From: Furong Xu <0x1207@gmail.com>
To: Boon Khai Ng <boon.khai.ng@altera.com>
Cc: netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Russell King <linux@armlinux.org.uk>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Matthew Gerlach <matthew.gerlach@altera.com>,
Tien Sung Ang <tien.sung.ang@altera.com>,
Mun Yew Tham <mun.yew.tham@altera.com>,
G Thomas Rohan <rohan.g.thomas@altera.com>
Subject: Re: [PATCH net-next v3 1/2] net: stmmac: Refactor VLAN implementation
Date: Thu, 10 Apr 2025 16:19:12 +0800 [thread overview]
Message-ID: <20250410161912.0000168a@gmail.com> (raw)
In-Reply-To: <20250408081354.25881-2-boon.khai.ng@altera.com>
On Tue, 8 Apr 2025 16:13:53 +0800, Boon Khai Ng <boon.khai.ng@altera.com> wrote:
> Refactor VLAN implementation by moving common code for DWMAC4 and
> DWXGMAC IPs into a separate VLAN module. VLAN implementation for
> DWMAC4 and DWXGMAC differs only for CSR base address, the descriptor
> for the VLAN ID and VLAN VALID bit field.
>
> Signed-off-by: Boon Khai Ng <boon.khai.ng@altera.com>
> Reviewed-by: Matthew Gerlach <matthew.gerlach@altera.com>
> ---
> drivers/net/ethernet/stmicro/stmmac/Makefile | 2 +-
> drivers/net/ethernet/stmicro/stmmac/common.h | 1 +
> drivers/net/ethernet/stmicro/stmmac/dwmac4.h | 40 ---
> .../net/ethernet/stmicro/stmmac/dwmac4_core.c | 295 +-----------------
> .../net/ethernet/stmicro/stmmac/dwxgmac2.h | 13 -
> .../ethernet/stmicro/stmmac/dwxgmac2_core.c | 87 ------
> drivers/net/ethernet/stmicro/stmmac/hwif.c | 8 +
> drivers/net/ethernet/stmicro/stmmac/hwif.h | 61 ++--
> .../net/ethernet/stmicro/stmmac/stmmac_vlan.c | 294 +++++++++++++++++
> .../net/ethernet/stmicro/stmmac/stmmac_vlan.h | 63 ++++
> 10 files changed, 401 insertions(+), 463 deletions(-)
> create mode 100644 drivers/net/ethernet/stmicro/stmmac/stmmac_vlan.c
> create mode 100644 drivers/net/ethernet/stmicro/stmmac/stmmac_vlan.h
>
[...]
> +static void vlan_update_hash(struct mac_device_info *hw, u32 hash,
> + __le16 perfect_match, bool is_double)
> +{
> + void __iomem *ioaddr = hw->pcsr;
> + u32 value;
> +
> + writel(hash, ioaddr + VLAN_HASH_TABLE);
> +
> + value = readl(ioaddr + VLAN_TAG);
> +
> + if (hash) {
> + value |= VLAN_VTHM | VLAN_ETV;
> + if (is_double) {
> + value |= VLAN_EDVLP;
> + value |= VLAN_ESVL;
> + value |= VLAN_DOVLTC;
I can confirm that 802.1ad (QinQ) has been broken on stmmac for years,
and it will be so nice if this refactoring includes some fixes for QinQ
> + }
> +
> + writel(value, ioaddr + VLAN_TAG);
> + } else if (perfect_match) {
> + u32 value = VLAN_ETV;
> +
> + if (is_double) {
> + value |= VLAN_EDVLP;
> + value |= VLAN_ESVL;
> + value |= VLAN_DOVLTC;
> + }
> +
> + writel(value | perfect_match, ioaddr + VLAN_TAG);
> + } else {
> + value &= ~(VLAN_VTHM | VLAN_ETV);
> + value &= ~(VLAN_EDVLP | VLAN_ESVL);
> + value &= ~VLAN_DOVLTC;
> + value &= ~VLAN_VID;
> +
> + writel(value, ioaddr + VLAN_TAG);
> + }
> +}
> +
> +static void vlan_enable(struct mac_device_info *hw, u32 type)
> +{
> + void __iomem *ioaddr = hw->pcsr;
> + u32 value;
> +
> + value = readl(ioaddr + VLAN_INCL);
> + value |= VLAN_VLTI;
> + value |= VLAN_CSVL; /* Only use SVLAN */
> + value &= ~VLAN_VLC;
> + value |= (type << VLAN_VLC_SHIFT) & VLAN_VLC;
> + writel(value, ioaddr + VLAN_INCL);
> +}
> +
> +static void vlan_rx_hw(struct mac_device_info *hw,
> + struct dma_desc *rx_desc, struct sk_buff *skb)
> +{
> + if (hw->desc->get_rx_vlan_valid(rx_desc)) {
> + u16 vid = hw->desc->get_rx_vlan_tci(rx_desc);
> +
> + __vlan_hwaccel_put_tag(skb, htons(ETH_P_8021Q), vid);
So, as the comment above, ETH_P_8021AD or ETH_P_8021Q shall be set selectively
depend on the frame type.
> + }
> +}
next prev parent reply other threads:[~2025-04-10 8:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 8:13 [PATCH net-next v3 0/2] Refactoring designware VLAN code Boon Khai Ng
2025-04-08 8:13 ` [PATCH net-next v3 1/2] net: stmmac: Refactor VLAN implementation Boon Khai Ng
2025-04-10 6:38 ` Furong Xu
2025-04-21 16:40 ` Ng, Boon Khai
2025-04-10 8:19 ` Furong Xu [this message]
2025-04-11 16:27 ` Simon Horman
2025-04-21 16:52 ` Ng, Boon Khai
2025-04-11 16:36 ` Simon Horman
2025-04-21 16:47 ` Ng, Boon Khai
2025-04-08 8:13 ` [PATCH net-next v3 2/2] net: stmmac: dwxgmac2: Add support for HW-accelerated VLAN stripping Boon Khai Ng
2025-04-08 19:08 ` Andrew Lunn
2025-04-09 3:12 ` Ng, Boon Khai
2025-04-09 12:04 ` Andrew Lunn
2025-04-10 2:19 ` Ng, Boon Khai
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=20250410161912.0000168a@gmail.com \
--to=0x1207@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=boon.khai.ng@altera.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=matthew.gerlach@altera.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mun.yew.tham@altera.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rohan.g.thomas@altera.com \
--cc=tien.sung.ang@altera.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).