linux-kernel - Re: [PATCH v3 2/2] of_mdio: Allow the DT to specify the phy ID and avoid autoprobing

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20140320.171057.609753569047907079.davem@davemloft.net>
Date:	Thu, 20 Mar 2014 17:10:57 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	jgunthorpe@...idianresearch.com
Cc:	robh+dt@...nel.org, f.fainelli@...il.com,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH v3 2/2] of_mdio: Allow the DT to specify the phy ID and
 avoid autoprobing

From: Jason Gunthorpe <jgunthorpe@...idianresearch.com>
Date: Wed, 19 Mar 2014 16:15:24 -0600

> This makes the generic of_mdiobus_register parse the DT compatible string for
> the pattern ethernet-phy-idAAAA.BBBB. If present it should be a value that
> matches the phy-id register normally readable through MDIO.
> 
> When the ID is given the phy autoprobing is defeated and the phy is
> created directly.
> 
> This is necessary to support phy's that cannot be autoprobed when
> of_mdiobus_register is called. Specifically, my case has the phy in reset at
> of_mdiobus_register, the reset is only released once the ethernet driver
> starts, before it attaches to the phy.
> 
> Tested on ARM Kirkwood with phy id 0x01410e90 (Marvell 88E1318)
> 
> Signed-off-by: Jason Gunthorpe <jgunthorpe@...idianresearch.com>
> Acked-by: Florian Fainelli <f.fainelli@...il.com>

Also applied to net-next.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/