From: Florian Fainelli <f.fainelli@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>, David Miller <davem@davemloft.net>
Cc: netdev <netdev@vger.kernel.org>,
Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
Neil Armstrong <narmstrong@baylibre.com>
Subject: Re: [PATCH net-next 2/2] dsa: mv88e6xxx.c: Hardware reset the chip if available
Date: Wed, 18 Nov 2015 15:51:22 -0800 [thread overview]
Message-ID: <564D0EFA.7050806@gmail.com> (raw)
In-Reply-To: <1447889365-25256-3-git-send-email-andrew@lunn.ch>
On 18/11/15 15:29, Andrew Lunn wrote:
> The device tree binding now allows a gpio to be specified which is
> attached to the switch chips reset line. If it is defined, perform
> a hardware reset on the switch during setup.
>
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> ---
> drivers/net/dsa/mv88e6xxx.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/drivers/net/dsa/mv88e6xxx.c b/drivers/net/dsa/mv88e6xxx.c
> index b06dba05594a..c0bbbe7713c5 100644
> --- a/drivers/net/dsa/mv88e6xxx.c
> +++ b/drivers/net/dsa/mv88e6xxx.c
> @@ -19,6 +19,7 @@
> #include <linux/list.h>
> #include <linux/module.h>
> #include <linux/netdevice.h>
> +#include <linux/gpio/consumer.h>
> #include <linux/phy.h>
> #include <net/dsa.h>
> #include <net/switchdev.h>
> @@ -2323,7 +2324,10 @@ int mv88e6xxx_switch_reset(struct dsa_switch *ds, bool ppu_active)
> {
> struct mv88e6xxx_priv_state *ps = ds_to_priv(ds);
> u16 is_reset = (ppu_active ? 0x8800 : 0xc800);
> + int gpio = ds->pd->reset;
> + int flags = ds->pd->reset_flags;
> unsigned long timeout;
> + int on = 1;
> int ret;
> int i;
>
> @@ -2336,6 +2340,16 @@ int mv88e6xxx_switch_reset(struct dsa_switch *ds, bool ppu_active)
> /* Wait for transmit queues to drain. */
> usleep_range(2000, 4000);
>
> + /* If there is a gpio connected to the reset pin, toggle it */
> + if (gpio_is_valid(gpio)) {
> + if (flags && OF_GPIO_ACTIVE_LOW)
> + on = !on;
> + gpio_set_value_cansleep(gpio, on);
> + usleep_range(10000, 20000);
> + gpio_set_value_cansleep(gpio, !on);
> + usleep_range(10000, 20000);
> + }
We are embedding reset logic here about the delays and polarity, while
there is now a proper abstraction for this within the reset controller
subsystem under drivers/reset/core.c. Could we utilize that facility
instead which would make us more robust wrt. non-GPIO reset lines (for
instance some SF2 switches on DSL gateways could definitively benefit
from this).
There does not seem to be a reset controller GPIO binding and generic
driver, but this seems like an appropriate candidate?
--
Florian
next prev parent reply other threads:[~2015-11-18 23:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 23:29 [PATCH net-next 0/2] DSA: GPIO to reset switches Andrew Lunn
2015-11-18 23:29 ` [PATCH net-next 1/2] net: dsa: Add support for a switch reset gpio Andrew Lunn
2015-11-19 3:06 ` Andrew Lunn
2015-11-19 8:39 ` Neil Armstrong
2015-11-19 14:55 ` Andrew Lunn
2015-11-18 23:29 ` [PATCH net-next 2/2] dsa: mv88e6xxx.c: Hardware reset the chip if available Andrew Lunn
2015-11-18 23:51 ` Florian Fainelli [this message]
2015-11-19 1:13 ` Andrew Lunn
2015-11-19 2:08 ` Phil Reid
2015-11-19 2:25 ` Andrew Lunn
2015-11-19 6:32 ` Phil Reid
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=564D0EFA.7050806@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=narmstrong@baylibre.com \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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).