From: Vladimir Oltean <olteanv@gmail.com>
To: Robert Marko <robert.marko@sartura.hr>
Cc: Andrew Lunn <andrew@lunn.ch>,
vivien.didelot@gmail.com, Florian Fainelli <f.fainelli@gmail.com>,
David Miller <davem@davemloft.net>,
kuba@kernel.org, netdev@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Gabor Juhos <j4g8y7@gmail.com>, John Crispin <john@phrozen.org>
Subject: Re: [net-next] net: dsa: qca8k: only change the MIB_EN bit in MODULE_EN register
Date: Tue, 9 Nov 2021 01:38:16 +0200 [thread overview]
Message-ID: <20211108233816.tnov6gufaagdrhlv@skbuf> (raw)
In-Reply-To: <CA+HBbNH=31j1Nv8T67DKhLXaQub2Oz11Dw2RuMEWQ3iXrF2fxg@mail.gmail.com>
On Mon, Nov 08, 2021 at 11:13:30PM +0100, Robert Marko wrote:
> > The driver keeps state. If the switch just resets by itself, what do you
> > think will continue to work fine afterwards? The code path needs testing.
> > I am not convinced that a desynchronized software state is any better
> > than a lockup.
>
> It's really unpredictable, as QCA doesn't specify what does the software reset
> actually does, as I doubt that they are completely resetting the
> switch to HW defaults.
> But since I was not able to trigger the QM error and the resulting
> reset, it's hard to tell.
> Phylink would probably see the ports going down and trigger the MAC
> configuration again,
> this should at least allow using the ports and forwarding to CPU again.
> However, it may also reset the forwarding config to basically flooding
> all ports which is the default
> which is not great.
>
> But I do agree that it may not be a lot better than a lockup.
I'm not sure what you expect going forward. You haven't proven an issue
with the actual code structure, or an improvement brought by your change.
Allowing the hardware to autonomously reconfigure itself, even if
partially, is out of the question (of course, that's if and only if I
understand correctly the info that you've presented).
next prev parent reply other threads:[~2021-11-08 23:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 12:49 [net-next] net: dsa: qca8k: only change the MIB_EN bit in MODULE_EN register Robert Marko
2021-11-04 12:52 ` Vladimir Oltean
2021-11-08 20:20 ` Vladimir Oltean
2021-11-08 21:10 ` Robert Marko
2021-11-08 21:18 ` Vladimir Oltean
2021-11-08 21:39 ` Robert Marko
2021-11-08 21:46 ` Vladimir Oltean
2021-11-08 21:56 ` Robert Marko
2021-11-08 21:59 ` Vladimir Oltean
2021-11-08 22:13 ` Robert Marko
2021-11-08 23:38 ` Vladimir Oltean [this message]
2021-11-08 23:52 ` Robert Marko
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=20211108233816.tnov6gufaagdrhlv@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=j4g8y7@gmail.com \
--cc=john@phrozen.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robert.marko@sartura.hr \
--cc=vivien.didelot@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