of_phy_connect is useful for most systems, but some drivers will want
finer-grained control over their PHYs, and won't want to use the
PHY Lib state machine or interrupt handlers.
This mirrors phy_attach() in libphy, which is already exported.
Signed-off-by: Andy Fleming aflem...@freescale.com
On Mon, Oct 17, 2011 at 10:41 AM, David Daney david.da...@cavium.com wrote:
On 10/17/2011 07:48 AM, Kumar Gala wrote:
On Sep 29, 2011, at 7:32 PM, Grant Likely wrote:
On Thu, Sep 29, 2011 at 04:31:12PM -0400, David Miller wrote:
From: David Daneydavid.da...@cavium.com
Your tree or mine,
On Fri, Feb 17, 2012 at 1:20 PM, Tabi Timur-B04825 b04...@freescale.com wrote:
On Tue, Feb 14, 2012 at 2:37 AM, Prabhakar Kushwaha
prabha...@freescale.com wrote:
Applied on git://git.kernel.org/pub/scm/linux/kernel/git/galak/powerpc.git
branch next
This is actually a false statement.
On Friday, September 30, 2011, David Daney david.da...@cavium.com wrote:
Many 10 gigabit Ethernet PHY devices are interfaced to the MDIO bus
using a protocol called IEEE802.3-2005 Section 45. Where as PHYS for
1G, 100M and 10M usually use IEEE802.3-2005 Section 22. These two
protocols can be
david.da...@cavium.com
Cc: Grant Likely grant.lik...@secretlab.ca
Cc: David S. Miller da...@davemloft.net
Looks good to me.
Acked-by: Andy Fleming aflem...@freescale.com
___
devicetree-discuss mailing list
devicetree-discuss@lists.ozlabs.org
https
On Fri, Nov 19, 2010 at 4:13 PM, David Daney dda...@caviumnetworks.com wrote:
Some aspects of PHY initialization are board dependent, things like
indicator LED connections and some clocking modes cannot be determined
by probing. The dev_flags element of struct phy_device can be used to
