From: Andrew Lunn <andrew@lunn.ch>
To: "Alvin Šipraga" <alvin.sipraga@analog.com>
Cc: Rustam Adilov <adilov@disroot.org>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Linus Walleij <linusw@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Taiga Ogawa <zectaiga@gmail.com>
Subject: Re: [PATCH net-next] net: dsa: tag_rtl8_4: add support for RTL9607C tag variant
Date: Fri, 20 Nov 2026 14:10:41 +0100 [thread overview]
Message-ID: <e9964125-48a8-4a0a-aedf-1c22aed891c4@lunn.ch> (raw)
In-Reply-To: <awA2z07l0ZvzcWtc@analog.com>
On Fri, Nov 20, 2026 at 01:09:42PM +0100, Alvin Šipraga wrote:
> On Thu, Nov 19, 2026 at 09:50:51PM +0500, Rustam Adilov wrote:
> > The RTL9607C family of SoCs have an embdedded switch that utilizes
> > the same Realtek CPU Tag protocol 4 with 8 bytes in size but have
> > a bit different of a layout. And that layout is also different for
> > TX versus RX sides and introduces new fields not seen by RTL8_4.
> >
> > Add basic necessities for this cpu tag variant to function.
> >
> > Tested-by: Taiga Ogawa <zectaiga@gmail.com>
> > Signed-off-by: Rustam Adilov <adilov@disroot.org>
> > ---
> > Tested on OpenWrt with 6.18 kernel version [1].
>
> Mainline doesn't have the requisite DSA driver to make use of this
> protocol. Andrew, is it normal to accept tag protocol drivers without
> the corresponding DSA driver?
At minimum, i would like to know the DSA driver is on the way. It
could be posted as an RFC. Best would be to make it a patch series,
the tag driver and a minimal DSA driver. That would be normal.
Andrew
next prev parent reply other threads:[~2026-11-20 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 16:50 Rustam Adilov
2026-11-20 12:09 ` Alvin Šipraga
2026-11-20 13:10 ` Andrew Lunn [this message]
2026-11-20 14:47 ` Rustam Adilov
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=e9964125-48a8-4a0a-aedf-1c22aed891c4@lunn.ch \
--to=andrew@lunn.ch \
--cc=adilov@disroot.org \
--cc=alvin.sipraga@analog.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=zectaiga@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
all inboxes | Powered by JetHome®