From: Michal Simek <michal.simek@xilinx.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 8/8] net: zynq: Fix MDC setting for zynq
Date: Wed, 4 Nov 2015 14:40:41 +0100 [thread overview]
Message-ID: <563A0AD9.6090004@xilinx.com> (raw)
In-Reply-To: <CANr=Z=YH-W21xEs6WRo5Xsmw3ytw_Xg0w022vPwZSnB13fQo2w@mail.gmail.com>
On 11/02/2015 10:39 PM, Joe Hershberger wrote:
> On Tue, Oct 27, 2015 at 10:17 AM, Michal Simek <michal.simek@xilinx.com> wrote:
>> Based on spec:
>> "MDC must not exceed 2.5 MHz (MDC is only active during MDIO read and
>> write operations)"
>> Zynq is running on 111MHz. Current setting is 32 which is 111/32=3.47
>
> Isn't it dependent on which board and what the clock setup is? Should
> this be specified by the board?
I am not aware about it. It is related to internal chip clock. I expect
that 111MHz is software default value is is used by most of the chip.
The clock range based on mainline Linux driver is 80MHz - 120MHz that's
why I expect all non standard configuration will fit to it.
For lower values as we used till now none reported any functional issue
too.
>
>> which is above of 2.5MHz.
>> Using 48 divider will give us correct setting according spec
>> (111/48=2.31).
>>
>> Signed-off-by: Michal Simek <michal.simek@xilinx.com>
>
> Acked-by: Joe Hershberger <joe.hershberger@ni.com>
>
Thanks,
Michal
next prev parent reply other threads:[~2015-11-04 13:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 15:17 [U-Boot] [PATCH 1/8] net: zynq: Allocate BD_SPACE in connection to RX_BUF Michal Simek
2015-10-27 15:17 ` [U-Boot] [PATCH 2/8] net: zynq: Setup BD when structures are filled Michal Simek
2015-11-02 21:39 ` Joe Hershberger
2015-10-27 15:17 ` [U-Boot] [PATCH 3/8] net: zynq: Do not report TX underrun Michal Simek
2015-11-02 21:40 ` Joe Hershberger
2015-10-27 15:17 ` [U-Boot] [PATCH 4/8] net: zynq: Add dummy packet to fix packet duplication issue Michal Simek
2015-11-02 21:40 ` Joe Hershberger
2015-10-27 15:17 ` [U-Boot] [PATCH 5/8] net: zynq: Wait till packet is sent Michal Simek
2015-11-02 21:40 ` Joe Hershberger
2015-11-04 13:46 ` Michal Simek
2015-10-27 15:17 ` [U-Boot] [PATCH 6/8] net: zynq: Fix mdc clock division setting for 100Mbit/s Michal Simek
2015-11-02 21:40 ` Joe Hershberger
2015-10-27 15:17 ` [U-Boot] [PATCH 7/8] net: zynq: Remove unused MDCCLKDIV2 macro Michal Simek
2015-11-02 21:40 ` Joe Hershberger
2015-10-27 15:17 ` [U-Boot] [PATCH 8/8] net: zynq: Fix MDC setting for zynq Michal Simek
2015-11-02 21:39 ` Joe Hershberger
2015-11-04 13:40 ` Michal Simek [this message]
2015-11-04 18:19 ` Joe Hershberger
2015-11-02 21:39 ` [U-Boot] [PATCH 1/8] net: zynq: Allocate BD_SPACE in connection to RX_BUF Joe Hershberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=563A0AD9.6090004@xilinx.com \
--to=michal.simek@xilinx.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox