2) Call your mdio bus initialization function from your USB probe
function.
If I have multiple devices, should I wind up having a separate MDIO
bus
for each? If so, this would make sense for handling the registration.
My theory is one bus per master (mostly). As I understand it, each
On Thu, 2005-08-25 at 15:51 -0500, Andy Fleming wrote:
> On Aug 25, 2005, at 15:04, David Hollis wrote:
>
>
> >
> > Question for you, I'm trying to setup my mdio_bus driver and I don't
> > know how I can get it registered at the appropriate time. I can't
> > read
> > the PHY IDs until after I'
On Aug 25, 2005, at 15:04, David Hollis wrote:
Question for you, I'm trying to setup my mdio_bus driver and I don't
know how I can get it registered at the appropriate time. I can't
read
the PHY IDs until after I've diddled some bits on the device which
happens in my USB probe function.
On Wed, 2005-08-24 at 18:46 -0500, Andy Fleming wrote:
> This patch adds back the code that was taken out, thus re-enabling:
>
> * The PHY Layer to initialize without crashing
> * Drivers to actually connect to PHYs
> * The entire PHY Control Layer
>
Andy,
Thanks for the updated patch. Now I am
This patch adds back the code that was taken out, thus re-enabling:
* The PHY Layer to initialize without crashing
* Drivers to actually connect to PHYs
* The entire PHY Control Layer
This patch is used by the gianfar driver, and other drivers which are in
development.
Signed-off-by: Andy Flemi
