linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: netdev@vger.kernel.org, linuxppc-dev@ozlabs.org,
	paulus@samba.org, Domen Puncer <domen@coderock.org>
Subject: Re: [PATCH] [POWERPC] mpc5200: Allow for fixed speed MII configurations
Date: Thu, 01 May 2008 18:38:11 +0200	[thread overview]
Message-ID: <4819F1F3.2000406@grandegger.com> (raw)
In-Reply-To: <fa686aa40805010733o6bb5b522hd16669b732f1892@mail.gmail.com>

Hi Grant,

Grant Likely wrote:
> On Tue, Apr 29, 2008 at 5:06 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
>> From: Grant Likely <grant.likely@secretlab.ca>
>>
>>  Various improvements for configuring the MPC5200 MII link from the
>>  device tree:
>>  * Look for 'current-speed' property for fixed speed MII links
>>  * Look for 'fsl,7-wire-mode' property for boards using the 7 wire mode
>>  * move definition of private data structure out of the header file
>>
>>  Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
> 
> Any more comments on this patch?  I want to push it to Paulus, but I'd
> like to have someone ack it first.
> 
> Wolfgang, you used the previous version of this patch.  Does this one
> work for you?

Sorry for the late answer. The patch works fine (under Linux 2.6.24) on
my board with a 3-port Micrel ethernet switch. There is still a minor
issue, though:

[...deletions...]
>>  diff --git a/drivers/net/fec_mpc52xx.c b/drivers/net/fec_mpc52xx.c
>>  index d21b7ab..eeb4433 100644
>>  --- a/drivers/net/fec_mpc52xx.c
>>  +++ b/drivers/net/fec_mpc52xx.c
[...deletions...]
>>  @@ -950,24 +976,36 @@ mpc52xx_fec_probe(struct of_device *op, const struct of_device_id *match)
>>         priv->msg_enable = netif_msg_init(debug, MPC52xx_MESSAGES_DEFAULT);
>>         priv->duplex = DUPLEX_FULL;

More concerning this line below.

>>
>>  -       /* is the phy present in device tree? */
>>  -       ph = of_get_property(op->node, "phy-handle", NULL);
>>  -       if (ph) {
>>  -               const unsigned int *prop;
>>  -               struct device_node *phy_dn;
>>  -               priv->has_phy = 1;
>>  -
>>  -               phy_dn = of_find_node_by_phandle(*ph);
>>  -               prop = of_get_property(phy_dn, "reg", NULL);
>>  -               priv->phy_addr = *prop;
>>  +       /*
>>  +        * Link mode configuration
>>  +        */
>>
>>  -               of_node_put(phy_dn);
>>  +       /* Start with safe defaults for link connection */
>>  +       priv->phy_addr = FEC5200_PHYADDR_NONE;
>>  +       priv->speed = 100;
>>  +       priv->duplex = 0;

priv->duplex is re-defined here. And instead of "0" we should use
DUPLEX_HALF.

Wolfgang.

  reply	other threads:[~2008-05-01 16:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29 23:06 [PATCH] [POWERPC] mpc5200: Allow for fixed speed MII configurations Grant Likely
2008-04-30  7:36 ` Joakim Tjernlund
2008-04-30 13:07   ` Grant Likely
2008-04-30 13:10     ` Joakim Tjernlund
2008-04-30 13:26       ` Grant Likely
2008-04-30 14:16         ` Joakim Tjernlund
2008-04-30 14:28           ` Grant Likely
2008-04-30 15:04             ` Joakim Tjernlund
2008-05-01 14:33 ` Grant Likely
2008-05-01 16:38   ` Wolfgang Grandegger [this message]
2008-05-01 16:52     ` Grant Likely
2008-05-01 16:59       ` Wolfgang Grandegger

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=4819F1F3.2000406@grandegger.com \
    --to=wg@grandegger.com \
    --cc=domen@coderock.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=paulus@samba.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).