From: Sascha Hauer <s.hauer@pengutronix.de>
To: Michael Grzeschik <m.grzeschik@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] net: cpsw: don't reset twice
Date: Mon, 18 Nov 2019 09:16:27 +0100 [thread overview]
Message-ID: <20191118081627.m3x5dfu3hmqznnu6@pengutronix.de> (raw)
In-Reply-To: <20191115161928.12313-1-m.grzeschik@pengutronix.de>
On Fri, Nov 15, 2019 at 05:19:28PM +0100, Michael Grzeschik wrote:
> The softreset was already called previously in open and other settings
> have been prepared afterwards, so don't reset it a second time.
>
> Signed-off-by: Michael Grzeschik <m.grzeschik@pengutronix.de>
> ---
> drivers/net/cpsw.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/net/cpsw.c b/drivers/net/cpsw.c
> index b9a6575009..4eb2205daa 100644
> --- a/drivers/net/cpsw.c
> +++ b/drivers/net/cpsw.c
> @@ -676,8 +676,6 @@ static void cpsw_slave_init(struct cpsw_slave *slave, struct cpsw_priv *priv)
>
> dev_dbg(&slave->dev, "* %s\n", __func__);
>
> - soft_reset(priv, &slave->sliver->soft_reset);
> -
What you remove here is the only place where soft_reset() is called with
&slave->sliver->soft_reset. If you have to remove that to fix something
then it's not because we reset something twice.
What looks really really fishy in this driver is that cpsw_open() is
called per slave, but nearly all things this function does affect the
whole cpsw and not the slave instance it is called with. This starts
with:
soft_reset(priv, &priv->regs->soft_reset);
It looks like this can't work when multiple slaves are enabled.
Sascha
--
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 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2019-11-18 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 16:19 Michael Grzeschik
2019-11-18 8:16 ` Sascha Hauer [this message]
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=20191118081627.m3x5dfu3hmqznnu6@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.grzeschik@pengutronix.de \
/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