linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: joakim.tjernlund@transmode.se
Cc: scottwood@freescale.com, linuxppc-dev@ozlabs.org,
	Stefan Roese <sr@denx.de>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	linux-net@vger.kernel.org
Subject: Re: [PATCH 1/5] phylib: don't create a phydev for ID-less PHYs.
Date: Fri, 11 Apr 2008 07:54:03 -0600	[thread overview]
Message-ID: <fa686aa40804110654k13e823c4v1d87d6a7cfd7034f@mail.gmail.com> (raw)
In-Reply-To: <1207910826.9544.26.camel@gentoo-jocke.transmode.se>

On Fri, Apr 11, 2008 at 4:47 AM, Joakim Tjernlund
<joakim.tjernlund@transmode.se> wrote:
>
>  On Fri, 2008-04-11 at 10:06 +0200, Stefan Roese wrote:
>  > On Friday 11 April 2008, Joakim Tjernlund wrote:
>  > > PHY ID 0x0 isn't an invalid id, I got a Broadcom PHY that has
>  > > PHY ID=0. Maybe I am misunderstanding something?
>  >
>  > IIRC, address 0 is the PHY broadcast address, but can be used without problem
>  > with some PHY's. I remember some designs were we had the PHY at address 0.
>
>  Ouh, if that is so, I guess we need a CONFIG option or a new mdio bus
>  property to select if PHY ID 0 is valid id or not.

Or, don't probe for phys by default.  Rather, use the data in the
device tree to determine what PHY ids are valid.

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2008-04-11 13:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-10 17:51 [PATCH 0/5] dynamic detection of gianfar TPIPA Paul Gortmaker
2008-04-10 17:51 ` [PATCH 1/5] phylib: don't create a phydev for ID-less PHYs Paul Gortmaker
2008-04-10 17:51   ` [PATCH 2/5] gianfar: assign mii_bus value in dev->priv Paul Gortmaker
2008-04-10 17:52     ` [PATCH 3/5] gianfar: limit scope of gfar_local_mdio functions Paul Gortmaker
2008-04-10 17:52       ` [PATCH 4/5] gianfar: dont hog the mii_bus->priv with just the regs Paul Gortmaker
2008-04-10 17:52         ` [PATCH 5/5] gianfar: don't hard code the TBIPA MDIO address Paul Gortmaker
2008-04-11  7:06   ` [PATCH 1/5] phylib: don't create a phydev for ID-less PHYs Joakim Tjernlund
2008-04-11  8:06     ` Stefan Roese
2008-04-11 10:47       ` Joakim Tjernlund
2008-04-11 13:54         ` Grant Likely [this message]
2008-04-10 22:17 ` [PATCH 0/5] dynamic detection of gianfar TPIPA David Miller
2008-04-10 23:30 ` Andy Fleming
2008-04-11  3:34   ` Paul Gortmaker

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=fa686aa40804110654k13e823c4v1d87d6a7cfd7034f@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=joakim.tjernlund@transmode.se \
    --cc=linux-net@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=scottwood@freescale.com \
    --cc=sr@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 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).