[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200728184732.GB1745134@lunn.ch>
Date: Tue, 28 Jul 2020 20:47:32 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Fabio Estevam <festevam@...il.com>
Cc: Bruno Thomsen <bruno.thomsen@...il.com>,
netdev <netdev@...r.kernel.org>,
Florian Fainelli <f.fainelli@...il.com>,
Russell King - ARM Linux <linux@...linux.org.uk>,
Heiner Kallweit <hkallweit1@...il.com>,
Lars Alex Pedersen <laa@...strup.com>,
Bruno Thomsen <bth@...strup.com>
Subject: Re: [PATCH 1/2] net: mdiobus: reset deassert delay
On Tue, Jul 28, 2020 at 09:32:03AM -0300, Fabio Estevam wrote:
> > Signed-off-by: Bruno Thomsen <bruno.thomsen@...il.com>
> > ---
> > drivers/net/phy/mdio_bus.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/phy/mdio_bus.c b/drivers/net/phy/mdio_bus.c
> > index 6ceee82b2839..84d5ab07fe16 100644
> > --- a/drivers/net/phy/mdio_bus.c
> > +++ b/drivers/net/phy/mdio_bus.c
> > @@ -627,8 +627,9 @@ int __mdiobus_register(struct mii_bus *bus, struct module *owner)
> > bus->reset_gpiod = gpiod;
> >
> > gpiod_set_value_cansleep(gpiod, 1);
> > - udelay(bus->reset_delay_us);
> > + fsleep(bus->reset_delay_us);
> > gpiod_set_value_cansleep(gpiod, 0);
> > + fsleep(bus->reset_delay_us);
>
> Shouldn't it use the value passed in the reset-deassert-us property
> instead?
Hi Fabio
As Bruno pointed out, that property is not relevant here. But i agree
with you in principle. Bruno, please add a new optional property for
the delay after releasing the reset.
Andrew
Powered by blists - more mailing lists