From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: [PATCH 1/3] net: dsa: ksz9477: always toggle reset gpio if available
Date: Thu, 2 May 2024 17:19:10 +0200 [thread overview]
Message-ID: <36534163-87c9-4afd-bb50-9ec13aa58cd1@pengutronix.de> (raw)
In-Reply-To: <20240502151757.3964461-1-a.fatoum@pengutronix.de>
On 02.05.24 17:17, Ahmad Fatoum wrote:
> The barebox driver currently only ensures that the switch is out of
> reset, but doesn't actually trigger a reset pulse.
>
> The Linux driver, on the other hand, holds reset active for 10ms and
> then waits a whopping 100ms after reset deassertion.
>
> This seems excessive by a thousandfold for at least KSZ9893R[1], whose
> datasheet states:
>
> After the de-assertion of reset, it is recommended to wait a minimum of
> 100µs before starting to program the device through any interface.
>
> Therefore, let's pulse the reset like Linux does and give the switch 100
> microseconds before continuing with the driver probe.
>
> [1]: DS00002420E-page 176
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
I forgot to include the patch prefix, but IMO all three patches are
master material.
Cheers,
Ahmad
> ---
> drivers/net/ksz9477.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ksz9477.c b/drivers/net/ksz9477.c
> index 1abea9d04017..5c5f4ec8d995 100644
> --- a/drivers/net/ksz9477.c
> +++ b/drivers/net/ksz9477.c
> @@ -433,8 +433,10 @@ static int microchip_switch_probe(struct device *dev)
> if (IS_ERR(gpio)) {
> dev_warn(dev, "Failed to get 'reset' GPIO (ignored)\n");
> } else if (gpio) {
> - mdelay(1);
> + gpiod_set_value(gpio, true);
> + mdelay(10);
> gpiod_set_value(gpio, false);
> + udelay(100);
> }
>
> ksz_reset_switch(dev->priv);
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-05-02 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 15:17 Ahmad Fatoum
2024-05-02 15:17 ` [PATCH 2/3] net: dsa: ksz9477: report 0 as value when returning error Ahmad Fatoum
2024-05-02 15:17 ` [PATCH 3/3] net: dsa: ksz9477: return negative error codes on PHY access failures Ahmad Fatoum
2024-05-02 15:19 ` Ahmad Fatoum [this message]
2024-05-03 6:50 ` [PATCH 1/3] net: dsa: ksz9477: always toggle reset gpio if available Sascha Hauer
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=36534163-87c9-4afd-bb50-9ec13aa58cd1@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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