From: Andrew Lunn <andrew@lunn.ch>
To: Fabio Estevam <festevam@gmail.com>
Cc: Bruno Thomsen <bruno.thomsen@gmail.com>,
netdev <netdev@vger.kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Heiner Kallweit <hkallweit1@gmail.com>,
Lars Alex Pedersen <laa@kamstrup.com>,
Bruno Thomsen <bth@kamstrup.com>
Subject: Re: [PATCH 1/2] net: mdiobus: reset deassert delay
Date: Tue, 28 Jul 2020 20:47:32 +0200 [thread overview]
Message-ID: <20200728184732.GB1745134@lunn.ch> (raw)
In-Reply-To: <CAOMZO5D3Hiybr8dPv2LZFrqp23=N1UGiy9Qea74ZSThoZALMbQ@mail.gmail.com>
On Tue, Jul 28, 2020 at 09:32:03AM -0300, Fabio Estevam wrote:
> > Signed-off-by: Bruno Thomsen <bruno.thomsen@gmail.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
next prev parent reply other threads:[~2020-07-28 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 9:02 [PATCH 1/2] net: mdiobus: reset deassert delay Bruno Thomsen
2020-07-28 9:02 ` [PATCH 2/2] dt-bindings: net: mdio: update reset-delay-us description Bruno Thomsen
2020-07-28 12:32 ` [PATCH 1/2] net: mdiobus: reset deassert delay Fabio Estevam
2020-07-28 12:49 ` Bruno Thomsen
2020-07-28 18:47 ` Andrew Lunn [this message]
2020-07-28 18:41 ` Andrew Lunn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200728184732.GB1745134@lunn.ch \
--to=andrew@lunn.ch \
--cc=bruno.thomsen@gmail.com \
--cc=bth@kamstrup.com \
--cc=f.fainelli@gmail.com \
--cc=festevam@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=laa@kamstrup.com \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).