netdev - Re: phy address in the device tree, vs auto probing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100210192411.GH27173@sirena.org.uk>
Date:	Wed, 10 Feb 2010 19:24:11 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Grant Likely <grant.likely@...retlab.ca>
Cc:	"M. Warner Losh" <imp@...imp.com>, scottwood@...escale.com,
	netdev@...r.kernel.org, devicetree-discuss@...ts.ozlabs.org,
	afleming@...escale.com
Subject: Re: phy address in the device tree, vs auto probing

On Wed, Feb 10, 2010 at 12:12:14PM -0700, Grant Likely wrote:
> On Wed, Feb 10, 2010 at 11:37 AM, M. Warner Losh <imp@...imp.com> wrote:

> > There are times that you'd want a list of PHY addresses to use. ?This
> > suggests a bitmask, but I don't know if they are common enough to
> > warrant the extra burden on the usual case...

> Are you talking a single MAC attached to multiple PHYs?  If so, then
> the current device tree binding doesn't support this, but it would be
> easy to extend the current binding by making the phy-handle property a
> list of phy nodes phandes.

There's also the entertaining case I've dealt with (pre device tree but
actually on PowerPC) where the MAC has multiple PHYs attached but they
should only be exposed to userspace and the driver should rely on MII
configuration provided by userspace without touching them.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html