From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: barebox@lists.infradead.org, kernel@pengutronix.de
Subject: Re: [PATCH] [RFC] fec: fix calculation of mii bus speed on mxs
Date: Mon, 10 Sep 2012 09:32:36 +0200 [thread overview]
Message-ID: <20120910073236.GU18243@pengutronix.de> (raw)
In-Reply-To: <1346939401-25611-1-git-send-email-u.kleine-koenig@pengutronix.de>
Hi Uwe,
On Thu, Sep 06, 2012 at 03:50:01PM +0200, Uwe Kleine-König wrote:
> According to a comment in Linux' fec driver, i.MX28 uses the same
> formula for determination of the frequency divider as i.MX6, that is
> (different from the i.MX28 manual):
>
> parent clock / ((MII_SPEED + 1) * 2)
>
> instead of
>
> parent clock / (MII_SPEED * 2)
>
> on the older i.MX SoCs. Fix the calculation accordingly.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> --
> But note that this doesn't fix accessing the phy on my machine. The
> calculated value is 9 (with and without this patch btw) but accessing
> the phy only gets reliable with a value of >=20 or alternatively don't
> set the SPEED value before reading and writing a mii register but only
> on probe.
>
> The Freescale kernel 2.6.35_10.12.01 does the following instead (in
> fec_switch.c):
>
> fep->phy_speed = DIV_ROUND_UP(clk_get_rate(fep->clk), 5000000) << 1;
> #ifdef CONFIG_ARCH_MXS
> /* Can't get phy(8720) ID when set to 2.5M on MX28, lower it */
> fep->phy_speed <<= 2;
> #endif
>
> which would result in 40 (and is unaware of the changed formula).
>
> I didn't have an opportunity to check the signals with an oszilloscope, but
> intend to fetch that later.
> ---
> drivers/net/fec_imx.c | 48 ++++++++++++++++++++++++++++++++++++++----------
> 1 file changed, 38 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/net/fec_imx.c b/drivers/net/fec_imx.c
> index 599a9b4..969c903 100644
> --- a/drivers/net/fec_imx.c
> +++ b/drivers/net/fec_imx.c
> @@ -47,6 +47,41 @@ struct fec_frame {
> uint8_t head[16]; /* MAC header(6 + 6 + 2) + 2(aligned) */
> };
>
> +static void fec_miidev_setspeed(struct fec_priv *fec)
> +{
> + u32 mii_speed;
> +
> + mii_speed = DIV_ROUND_UP(imx_get_fecclk(), 5000000);
> +
> +#ifdef CONFIG_ARCH_MXS
> + /*
> + * Compared to the other imx socs imx28 and imx6 have an additional "+1"
> + * in the formula for MII_SPEED. In MCIMX28RM Rev.1, 2010 this is not
> + * documented though.
> + */
> + mii_speed -= 1;
> +#endif
Please use a if (cpu_is_mx28()) instead. While we are at it we should
also do this for i.MX6 and add a cpu_is_mx6() aswell.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-09-10 7:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 13:50 Uwe Kleine-König
2012-09-10 7:32 ` Sascha Hauer [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=20120910073236.GU18243@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=kernel@pengutronix.de \
--cc=u.kleine-koenig@pengutronix.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