From: Felix Radensky <felix@embedded-sol.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: netdev <netdev@vger.kernel.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: RX problem in ibm_newemac driver
Date: Wed, 11 Mar 2009 10:56:31 +0200 [thread overview]
Message-ID: <49B77CBF.6070005@embedded-sol.com> (raw)
In-Reply-To: <1236730894.7086.29.camel@pasglop>
Benjamin Herrenschmidt wrote:
> On Wed, 2009-03-11 at 01:39 +0200, Felix Radensky wrote:
>
>> Benjamin Herrenschmidt wrote:
>>
>>> On Wed, 2009-03-11 at 00:14 +0200, Felix Radensky wrote:
>>>
>>>
>>>> Yes, seems logical. U-boot has code to enable and disable loopback clock
>>>> for 440SPE, 440EPX,440GRX,405EX, 460EX and 460GT.
>>>>
>>>> I can test patches on my board. Alternatively, I can try something myself
>>>> if you can provide some guidance. I guess you are referring to the code
>>>> using
>>>> EMAC_FTR_440GX_PHY_CLK_FIX and EMAC_FTR_440EP_PHY_CLK_FIX.
>>>>
>>>>
>>> It would be nice if you could try something as I don't have anything to
>>> test here.
>>>
>>> And yes, it's probably one of those 2 fixes that need to be extended.
>>>
>>> I'll have a look later today if I can find the 405EXr user manual and
>>> give you more precise guidance.
>>>
>
> >From the doc, it looks like it needs the 440 type workaround (and the
> 405EX as well). Can you try this patch:
>
> emac: Fix clock control for 405EX and 405EXr chips
>
> The EMAC variant in the 405EX and 405EXr chips needs the "440EP" type clock
> control workaround to avoid lockups of the Rx side during reset.
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> ---
>
> Index: linux-work/drivers/net/ibm_newemac/core.c
> ===================================================================
> --- linux-work.orig/drivers/net/ibm_newemac/core.c 2009-03-11 11:13:37.000000000 +1100
> +++ linux-work/drivers/net/ibm_newemac/core.c 2009-03-11 11:14:00.000000000 +1100
> @@ -2594,6 +2594,9 @@ static int __devinit emac_init_config(st
> if (of_device_is_compatible(np, "ibm,emac-460ex") ||
> of_device_is_compatible(np, "ibm,emac-460gt"))
> dev->features |= EMAC_FTR_460EX_PHY_CLK_FIX;
> + if (of_device_is_compatible(np, "ibm,emac-405ex") ||
> + of_device_is_compatible(np, "ibm,emac-405exr"))
> + dev->features |= EMAC_FTR_440EP_PHY_CLK_FIX;
> } else if (of_device_is_compatible(np, "ibm,emac4")) {
> dev->features |= EMAC_FTR_EMAC4;
> if (of_device_is_compatible(np, "ibm,emac-440gx"))
>
>
>
Hi, Ben
This patch fixes a problem for me. Thank you very much for a quick fix.
Felix.
next prev parent reply other threads:[~2009-03-11 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49B6C4A2.8060302@embedded-sol.com>
[not found] ` <1236718202.7086.10.camel@pasglop>
[not found] ` <49B6E658.4010900@embedded-sol.com>
[not found] ` <1236725832.7086.21.camel@pasglop>
[not found] ` <49B6FA3B.8030509@embedded-sol.com>
2009-03-11 0:21 ` RX problem in ibm_newemac driver Benjamin Herrenschmidt
2009-03-11 8:56 ` Felix Radensky [this message]
2009-03-13 20:49 ` David Miller
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=49B77CBF.6070005@embedded-sol.com \
--to=felix@embedded-sol.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).