linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Anatolij Gustschin <agust@denx.de>
Subject: Re: [PATCH v2] powerpc: 85xx: Add PHY fixup to socrates board code
Date: Tue, 21 Apr 2009 17:04:19 -0500	[thread overview]
Message-ID: <625ED025-8D5B-437F-BEA8-1A599B677D43@kernel.crashing.org> (raw)
In-Reply-To: <1D3E7471-098E-483F-A80D-4D02BB8F076C@kernel.crashing.org>


On Apr 21, 2009, at 4:54 PM, Kumar Gala wrote:

>
> On Apr 21, 2009, at 12:19 PM, Anatolij Gustschin wrote:
>
>> If the firmware missed to initialize the PHY correctly,
>> Linux may hang up on socrates while eth0/eth1 interface
>> startup (caused by continuous unacknowledged PHY interrupt).
>>
>> This patch adds PHY fixup to socrates platform code to
>> ensure the PHY is pre-initialized correctly. It is needed
>> to be compatible with older firmware.
>>
>> Signed-off-by: Anatolij Gustschin <agust@denx.de>
>> ---
>> Changes since first version:
>> 	use macros instead of register numbers as
>> 	suggested by Anton
>>
>> Kumar, could you please consider this patch for
>> inclusion into 2.6.30? Thanks!
>
> Sorry.  I dont think this is board specific and should at a minimum  
> be done in m88e1011_config_init in drivers/net/phy/marvell.c.  Not  
> sure how 88E1011 differs from 88E1111, but I'm wondering if you  
> really want to set config_init for m88e1011 to m88e1111_config_init
>
> - k

I got confused by the #'s.. I think we should have a struct in  
marvell.c for m88e1121 which I'm guessing is the PHY you are using.

- k

  reply	other threads:[~2009-04-21 22:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07 14:19 [PATCH] powerpc: 85xx: Add PHY fixup to socrates board code Anatolij Gustschin
2009-04-07 14:30 ` Anton Vorontsov
2009-04-07 17:24   ` Anatolij Gustschin
2009-04-07 18:09     ` Anton Vorontsov
2009-04-07 18:40       ` Anton Vorontsov
2009-04-21 17:19 ` [PATCH v2] " Anatolij Gustschin
2009-04-21 21:54   ` Kumar Gala
2009-04-21 22:04     ` Kumar Gala [this message]
2009-04-21 23:24       ` Anatolij Gustschin
2009-06-16 13:46         ` Kumar Gala
2009-06-23 10:15           ` Anatolij Gustschin

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=625ED025-8D5B-437F-BEA8-1A599B677D43@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=agust@denx.de \
    --cc=linuxppc-dev@ozlabs.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).