public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Simon Horman <horms@kernel.org>
Cc: Joris Vaisvila <joey@tinyisr.com>,
	netdev@vger.kernel.org, nbd@nbd.name, sean.wang@mediatek.com,
	lorenzo@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
	edumazet@google.com, pabeni@redhat.com
Subject: Re: [PATCH v2] net: ethernet: mtk_eth_soc: avoid writing to ESW registers on MT7628
Date: Thu, 8 Jan 2026 08:35:30 -0800	[thread overview]
Message-ID: <20260108083530.6169b627@kernel.org> (raw)
In-Reply-To: <20260108150457.GI345651@kernel.org>

On Thu, 8 Jan 2026 15:04:57 +0000 Simon Horman wrote:
> On Tue, Jan 06, 2026 at 07:18:28AM +0200, Joris Vaisvila wrote:
> > The MT7628 does not expose MAC control registers. Writes to these
> > registers corrupt the ESW VLAN configuration. Existing drivers
> > never use the affected features, so this went unnoticed.
> > 
> > This patch skips MCR register reads and writes on MT7628, preventing
> > invalid register access.
> > 
> > Fixes: 296c9120752b ("net: ethernet: mediatek: Add MT7628/88 SoC support")
> > Signed-off-by: Joris Vaisvila <joey@tinyisr.com>
> 
> While I think a minimal patch along these lines is appropriate as a bug
> fix. I am wondering if, as a follow-up, consideration could be given to
> registering alternate phy ops for MT7628. This would push the conditional
> handling to probe rather than calback execution time. And I suspect it
> would lead to a cleaner implementation.

Plus the commit message says: "Existing drivers never use the affected
features, so this went unnoticed." which makes it sound like user will
not notice the bad writes today?

So perhaps we can go for the cleaner approach and stick to net-next
(without fixing the older kernels?). Sorry for not reading the commit
message closely enough on v1.

  reply	other threads:[~2026-01-08 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06  5:18 [PATCH v2] net: ethernet: mtk_eth_soc: avoid writing to ESW registers on MT7628 Joris Vaisvila
2026-01-08 15:04 ` Simon Horman
2026-01-08 16:35   ` Jakub Kicinski [this message]
2026-01-09 20:09     ` Joris Vaišvila

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=20260108083530.6169b627@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=joey@tinyisr.com \
    --cc=lorenzo@kernel.org \
    --cc=nbd@nbd.name \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sean.wang@mediatek.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