[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52160EA9.4060801@overkiz.com>
Date: Thu, 22 Aug 2013 15:14:17 +0200
From: boris brezillon <b.brezillon@...rkiz.com>
To: Boris BREZILLON <b.brezillon@...rkiz.com>
CC: "David S. Miller" <davem@...emloft.net>,
Mark Brown <broonie@...nel.org>,
Nick Bowler <nbowler@...iptictech.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Grant Likely <grant.likely@...retlab.ca>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [RFC PATCH] phylib: mdio: handle register/unregister/register
sequence
On 22/08/2013 14:33, Boris BREZILLON wrote:
> Hello,
>
> This patch is a proposal to support the register/unregister/register
> sequence on a given mdio bus.
I forgot to ask, if this limitation was made on purpose ?
In other terms: no one should ever try to register, unregister and
register again
a given mii_bus structure.
>
> I use the register/unregister/register sequence to add a fallback when the
> of_mdiobus_register (this function calls mdiobus_register with phy_mask
> set to ~0) does not register any phy device (because the device tree does
> not define any phy).
> In this case I call mdiobus_unregister and then call mdiobus_register with
> a phy_mask set to 0 to trigger a full mdio bus scan.
>
> I'm not sure this is the right way to do it (this is why I added RFC in the
> subject).
>
> Could someone help me figuring out what I should use to implement my fallback ?
>
> 1) use the register/unregister/register sequence
> 2) reimplement the "for (i = 0; i < PHY_MAX_ADDR; i++)" mdiobus_scan loop
>
> Thanks.
>
> Best Regards,
> Boris
>
> Boris BREZILLON (1):
> phylib: mdio: handle register/unregister/register sequence
>
> drivers/net/phy/mdio_bus.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
--
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/
Powered by blists - more mailing lists