From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH][v2] driver/net/fm/memac_phy: Initialize mdio_clock for SoCs wih FMANv3
Date: Wed, 23 Apr 2014 15:02:29 -0700 [thread overview]
Message-ID: <53583875.6000603@freescale.com> (raw)
In-Reply-To: <1396934749-2282-1-git-send-email-Priyanka.Jain@freescale.com>
On 04/07/2014 10:25 PM, Priyanka Jain wrote:
> MDIO clock needs to be initialized in u-boot code for SoCs
> having FMAN-v3(v3H or v3L) controller due to below reasons
>
> -On SoCs that have FMAN-v3H like B4860, default value of
> MDIO_CLK_DIV bits in mdio_stat(mdio_cfg) register generates
> mdio clock too high (much higher than 2.5MHz), violating the
> IEEE specs.
> -On SOCs that have FMAN-v3L like T1040, default value of
> MDIO_CLK_DIV bits is zero, so MDIO clock is disabled.
>
> So, for proper functioninig of MDIO, MDIO_CLK_DIV bits needs to
> be properly initialized.
> Also this type of initialization is generally done in
> PBI(pre-bootloader) phase using rcw.But for chips like T1040
> which support deep-sleep, such type of initialization cannot be
> done in PBI phase due to the limitation that during deep-sleep
> resume, FMAN (MDIO) registers are not accessible in PBI phase.
> So, mdio clock initailization must be done as part of u-boot.
>
> This initialization code is implemented in memac_phy.c which
> gets compiled only for SoCs having FMANv3, so no extra compilation
> flag is required.
>
> Signed-off-by: Priyanka Jain <Priyanka.Jain@freescale.com>
> ---
> Changes for v2: Corrected Signed-off footer
>
Applied to u-boot-mpc85xx/master, thanks.
York
prev parent reply other threads:[~2014-04-23 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 5:25 [U-Boot] [PATCH][v2] driver/net/fm/memac_phy: Initialize mdio_clock for SoCs wih FMANv3 Priyanka Jain
2014-04-23 22:02 ` York Sun [this message]
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=53583875.6000603@freescale.com \
--to=yorksun@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.