netdev - Re: [PATCH v6 2/3] netdev/of/phy: Add MDIO bus multiplexer support.

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: <20120507.225853.1863347275703801019.davem@davemloft.net>
Date:	Mon, 07 May 2012 22:58:53 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	ddaney.cavm@...il.com
Cc:	ralf@...ux-mips.org, grant.likely@...retlab.ca,
	rob.herring@...xeda.com, devicetree-discuss@...ts.ozlabs.org,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-mips@...ux-mips.org, afleming@...il.com,
	galak@...nel.crashing.org, david.daney@...ium.com
Subject: Re: [PATCH v6 2/3] netdev/of/phy: Add MDIO bus multiplexer support.

From: David Daney <ddaney.cavm@...il.com>
Date: Wed,  2 May 2012 18:16:38 -0700

> From: David Daney <david.daney@...ium.com>
> 
> This patch adds a somewhat generic framework for MDIO bus
> multiplexers.  It is modeled on the I2C multiplexer.
> 
> The multiplexer is needed if there are multiple PHYs with the same
> address connected to the same MDIO bus adepter, or if there is
> insufficient electrical drive capability for all the connected PHY
> devices.
> 
> Conceptually it could look something like this:
 ...
> This framework configures the bus topology from device tree data.  The
> mechanics of switching the multiplexer is left to device specific
> drivers.
> 
> The follow-on patch contains a multiplexer driven by GPIO lines.
> 
> Signed-off-by: David Daney <david.daney@...ium.com>

Applied.
--
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