From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: netdev@vger.kernel.org, f.fainelli@gmail.com,
Daniel Mack <zonque@gmail.com>
Subject: Re: [PATCH] at803x: fix reset handling
Date: Wed, 23 Mar 2016 07:45:04 +0100 [thread overview]
Message-ID: <20160323064504.GI6191@pengutronix.de> (raw)
In-Reply-To: <1525241.UQIRf9ZOB3@wasted.cogentembedded.com>
Hello,
I added the author of 13a56b449325 to Cc.
On Wed, Mar 23, 2016 at 12:44:40AM +0300, Sergei Shtylyov wrote:
> The driver of course "knows" that the chip's reset signal is active low,
> so it drives the GPIO to 0 to reset the PHY and to 1 otherwise; however
> all this will only work iff the GPIO is specified as active-high in the
> device tree! I think both the driver and the device trees (if there are
> any -- I was unable to find them) need to be fixed in this case...
>
> Fixes: 13a56b449325 ("net: phy: at803x: Add support for hardware reset")
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>
> ---
> The patch is against DaveM's 'net.git' repo.
Don't you need to work against net-next for non-urgent stuff? Or do you
consider this urgent?
> drivers/net/phy/at803x.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> Index: net/drivers/net/phy/at803x.c
> ===================================================================
> --- net.orig/drivers/net/phy/at803x.c
> +++ net/drivers/net/phy/at803x.c
> @@ -277,7 +277,7 @@ static int at803x_probe(struct phy_devic
> if (!priv)
> return -ENOMEM;
>
> - gpiod_reset = devm_gpiod_get_optional(dev, "reset", GPIOD_OUT_HIGH);
> + gpiod_reset = devm_gpiod_get_optional(dev, "reset", GPIOD_OUT_LOW);
> if (IS_ERR(gpiod_reset))
> return PTR_ERR(gpiod_reset);
>
> @@ -362,10 +362,10 @@ static void at803x_link_change_notify(st
>
> at803x_context_save(phydev, &context);
>
> - gpiod_set_value(priv->gpiod_reset, 0);
> - msleep(1);
> gpiod_set_value(priv->gpiod_reset, 1);
> msleep(1);
> + gpiod_set_value(priv->gpiod_reset, 0);
> + msleep(1);
The new variant is better than the old one. The change however breaks
existing device trees which is not so nice. Given there are no mainline
users this is probably ok though. So:
Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2016-03-23 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 21:44 [PATCH] at803x: fix reset handling Sergei Shtylyov
2016-03-23 6:45 ` Uwe Kleine-König [this message]
2016-03-23 11:56 ` Daniel Mack
2016-03-23 13:30 ` Sergei Shtylyov
2016-03-23 13:23 ` Sergei Shtylyov
2016-03-23 17:40 ` David Miller
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=20160323064504.GI6191@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=zonque@gmail.com \
/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).