mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alvin Šipraga" <alvin.sipraga@analog.com>
To: Mieczyslaw Nalewaj <namiltd@yahoo.com>
Cc: linusw@kernel.org, andrew@lunn.ch, olteanv@gmail.com,
	kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com, linux@armlinux.org.uk, luizluca@gmail.com,
	maxime.chevallier@bootlin.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v7 05/10] net: dsa: realtek: rtl8365mb: set and get vlan 4k for family D
Date: Wed, 4 Nov 2026 13:45:14 +0100	[thread overview]
Message-ID: <ausoMS5PcpEFz02i@analog.com> (raw)
In-Reply-To: <1ccb6acc-0809-4abe-8443-576f6727a6d5@yahoo.com>

On Mon, Nov 02, 2026 at 03:40:53PM +0100, Mieczyslaw Nalewaj wrote:
> The hardware structure of 4K VLAN table entries has changed between
> silicon families. Family D's CVLAN entry is two 16-bit words rather
> than three: there is no third word extending member/untag past bit 7,
> and no priority/meter fields at all. The FID field is restricted to a
> narrower 2-bit width. The chip itself supports both IVL and SVL.
> IVL_EN (bit 3) follows vlan4k->ivl_en, as on family C; the only caller,
> rtl8365mb_vlan_4k_port_set(), always requests IVL. SVLAN_CHK_IVL_SVL
> (bit 2) is left at 0, as in the vendor RTL8367D CVLAN API, which sets
> it only from the SVLAN member API; this driver has no SVLAN support.
> vlan4k->ivl_en is read back from IVL_EN.
> 
> Reusing the three-word family C layout unconditionally means the third
> word is read from and written back to the register that holds it on
> family C, but does not exist as a distinct table word on family D's
> die; whatever data happens to be there gets folded into member/untag
> bits [10:8] on read, and re-written on every read-modify-write cycle
> in rtl8365mb_vlan_4k_port_set(). Give family D its own two-word
> pack/unpack instead.
> 
> The two-word layout matches the vendor switch API for this chip
> family, which writes only 0x0510/0x0511 for a CVLAN entry.
> 
> The family D paths are not reachable until the RTL8367S-VB chip table
> entry is added in the last patch of the series.
> 
> Signed-off-by: Mieczyslaw Nalewaj <namiltd@yahoo.com>
> Reviewed-by: Linus Walleij <linusw@kernel.org>
> ---
>  drivers/net/dsa/realtek/rtl8365mb_vlan.c | 161 ++++++++++++++++-------
>  1 file changed, 111 insertions(+), 50 deletions(-)
> 
> diff --git a/drivers/net/dsa/realtek/rtl8365mb_vlan.c b/drivers/net/dsa/realtek/rtl8365mb_vlan.c
> index 8d49ffa..36f0d2a 100644
> --- a/drivers/net/dsa/realtek/rtl8365mb_vlan.c
> +++ b/drivers/net/dsa/realtek/rtl8365mb_vlan.c
> @@ -48,12 +48,16 @@
>  
>  #include "rtl8365mb_vlan.h"
>  #include "rtl8365mb_table.h"
> +#include "rtl8365mb.h"
>  #include <linux/if_bridge.h>
>  #include <linux/lockdep.h>
>  #include <linux/regmap.h>
>  
> -/* CVLAN (i.e. VLAN4k) table entry layout, u16[3] */
> +/* CVLAN (i.e. VLAN4k) table entry layout: u16[3] on family C, u16[2] on
> + * family D
> + */
>  #define RTL8365MB_CVLAN_ENTRY_SIZE			3 /* 48-bits */
> +#define RTL8365MB_D_CVLAN_ENTRY_SIZE			2 /* 32-bits */
>  #define RTL8365MB_CVLAN_ENTRY_D0_MBR_MASK		GENMASK(7, 0)
>  #define   RTL8365MB_CVLAN_MBR_LO_MASK			GENMASK(7, 0)
>  #define RTL8365MB_CVLAN_ENTRY_D0_UNTAG_MASK		GENMASK(15, 8)
> @@ -65,6 +69,9 @@
>  #define RTL8365MB_CVLAN_ENTRY_D1_METERIDX_MASK		GENMASK(13, 9)
>  #define   RTL8365MB_CVLAN_METERIDX_LO_MASK		GENMASK(4, 0)
>  #define RTL8365MB_CVLAN_ENTRY_D1_IVL_SVL_MASK		GENMASK(14, 14)
> +/* Family D CVLAN entry, word 1 (family D has no word 2) */
> +#define RTL8365MB_D_CVLAN_ENTRY_D1_IVL_EN_MASK		GENMASK(3, 3)
> +#define RTL8365MB_D_CVLAN_ENTRY_D1_FID_MASK		GENMASK(1, 0)
>  /* extends RTL8365MB_CVLAN_ENTRY_D0_MBR_MASK */
>  #define RTL8365MB_CVLAN_ENTRY_D2_MBR_EXT_MASK		GENMASK(2, 0)
>  #define   RTL8365MB_CVLAN_MBR_HI_MASK			GENMASK(10, 8)
> @@ -185,13 +192,16 @@ struct rtl8365mb_vlanmc {
>  static int rtl8365mb_vlan_4k_read(struct realtek_priv *priv, u16 vid,
>  				  struct rtl8365mb_vlan4k *vlan4k)
>  {
> +	bool is_d = rtl8365mb_get_family(priv) == RTL8365MB_FAMILY_D;
> +	size_t entry_size = is_d ? RTL8365MB_D_CVLAN_ENTRY_SIZE :
> +				   RTL8365MB_CVLAN_ENTRY_SIZE;
>  	u16 data[RTL8365MB_CVLAN_ENTRY_SIZE];
>  	int val;
>  	int ret;
>  
>  	ret = rtl8365mb_table_query(priv, RTL8365MB_TABLE_CVLAN,
>  				    RTL8365MB_TABLE_OP_READ, &vid, 0, 0,
> -				    data, ARRAY_SIZE(data));
> +				    data, entry_size);
>  	if (ret)
>  		return ret;
>  
> @@ -199,33 +209,61 @@ static int rtl8365mb_vlan_4k_read(struct realtek_priv *priv, u16 vid,
>  	memset(vlan4k, 0, sizeof(*vlan4k));
>  	vlan4k->vid = vid;
>  
> +	/* member/untag: d0[7:0]/d0[15:8] on both families. Family C
> +	 * extends these into data[2] bits [2:0]/[5:3] for its 9th-11th
> +	 * ports; family D's die has only 8 ports and no third table
> +	 * word, so data[2] does not exist there and must not be read.
> +	 */
>  	val = FIELD_GET(RTL8365MB_CVLAN_ENTRY_D0_MBR_MASK, data[0]);
>  	vlan4k->member = FIELD_PREP(RTL8365MB_CVLAN_MBR_LO_MASK, val);
> -	val = FIELD_GET(RTL8365MB_CVLAN_ENTRY_D2_MBR_EXT_MASK, data[2]);
> -	vlan4k->member |= FIELD_PREP(RTL8365MB_CVLAN_MBR_HI_MASK, val);
> +	if (!is_d) {
> +		val = FIELD_GET(RTL8365MB_CVLAN_ENTRY_D2_MBR_EXT_MASK, data[2]);
> +		vlan4k->member |= FIELD_PREP(RTL8365MB_CVLAN_MBR_HI_MASK, val);
> +	}
>  
>  	val = FIELD_GET(RTL8365MB_CVLAN_ENTRY_D0_UNTAG_MASK, data[0]);
>  	vlan4k->untag = FIELD_PREP(RTL8365MB_CVLAN_UNTAG_LO_MASK, val);
> -	val = FIELD_GET(RTL8365MB_CVLAN_ENTRY_D2_UNTAG_EXT_MASK, data[2]);
> -	vlan4k->untag |= FIELD_PREP(RTL8365MB_CVLAN_UNTAG_HI_MASK, val);
> -
> -	vlan4k->fid = FIELD_GET(RTL8365MB_CVLAN_ENTRY_D1_FID_MASK, data[1]);
> -	vlan4k->priority_en =
> -		FIELD_GET(RTL8365MB_CVLAN_ENTRY_D1_VBPEN_MASK, data[1]);
> -	vlan4k->priority =
> -		FIELD_GET(RTL8365MB_CVLAN_ENTRY_D1_VBPRI_MASK, data[1]);
> -	vlan4k->policing_en =
> -		FIELD_GET(RTL8365MB_CVLAN_ENTRY_D1_ENVLANPOL_MASK, data[1]);
> -
> -	val = FIELD_GET(RTL8365MB_CVLAN_ENTRY_D1_METERIDX_MASK, data[1]);
> -	val = FIELD_PREP(RTL8365MB_CVLAN_METERIDX_LO_MASK, val);
> -	vlan4k->meteridx = val;
> -	val = FIELD_GET(RTL8365MB_CVLAN_ENTRY_D2_METERIDX_EXT_MASK, data[2]);
> -	val = FIELD_PREP(RTL8365MB_CVLAN_METERIDX_HI_MASK, val);
> -	vlan4k->meteridx |= val;
> -
> -	vlan4k->ivl_en =
> -		FIELD_GET(RTL8365MB_CVLAN_ENTRY_D1_IVL_SVL_MASK, data[1]);
> +	if (!is_d) {
> +		val = FIELD_GET(RTL8365MB_CVLAN_ENTRY_D2_UNTAG_EXT_MASK,
> +				data[2]);
> +		vlan4k->untag |= FIELD_PREP(RTL8365MB_CVLAN_UNTAG_HI_MASK, val);
> +	}
> +
> +	if (is_d) {
> +		vlan4k->fid = FIELD_GET(RTL8365MB_D_CVLAN_ENTRY_D1_FID_MASK,
> +					data[1]);
> +		/* Family D has no priority/meter fields in this entry -
> +		 * left zeroed by the memset() above.
> +		 */
> +		vlan4k->ivl_en =
> +			FIELD_GET(RTL8365MB_D_CVLAN_ENTRY_D1_IVL_EN_MASK,
> +				  data[1]);
> +	} else {
> +		vlan4k->fid = FIELD_GET(RTL8365MB_CVLAN_ENTRY_D1_FID_MASK,
> +					data[1]);
> +		vlan4k->priority_en =
> +			FIELD_GET(RTL8365MB_CVLAN_ENTRY_D1_VBPEN_MASK,
> +				  data[1]);
> +		vlan4k->priority =
> +			FIELD_GET(RTL8365MB_CVLAN_ENTRY_D1_VBPRI_MASK,
> +				  data[1]);
> +		vlan4k->policing_en =
> +			FIELD_GET(RTL8365MB_CVLAN_ENTRY_D1_ENVLANPOL_MASK,
> +				  data[1]);
> +
> +		val = FIELD_GET(RTL8365MB_CVLAN_ENTRY_D1_METERIDX_MASK,
> +				data[1]);
> +		val = FIELD_PREP(RTL8365MB_CVLAN_METERIDX_LO_MASK, val);
> +		vlan4k->meteridx = val;
> +		val = FIELD_GET(RTL8365MB_CVLAN_ENTRY_D2_METERIDX_EXT_MASK,
> +				data[2]);
> +		val = FIELD_PREP(RTL8365MB_CVLAN_METERIDX_HI_MASK, val);
> +		vlan4k->meteridx |= val;
> +
> +		vlan4k->ivl_en =
> +			FIELD_GET(RTL8365MB_CVLAN_ENTRY_D1_IVL_SVL_MASK,
> +				  data[1]);
> +	}

Don't you think it's better to just split out into family C/D variants
for these ops? If you do so, then I think relabelling the old macros for
the C family with RTL8365MB_C_ prefixes will also be appropriate.

[...]

Kind regards,
Alvin

  reply	other threads:[~2026-11-04 12:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3bf4dd70-9771-497b-8c27-e925e0ef81eb.ref@yahoo.com>
2026-11-02 14:34 ` [PATCH net-next v7 0/10] net: dsa: realtek: rtl8365mb: add support for RTL8367S-VB Mieczyslaw Nalewaj
2026-11-02 14:36   ` [PATCH net-next v7 01/10] dt-bindings: net: dsa: realtek: add RTL8367S-VB Mieczyslaw Nalewaj
2026-11-02 14:37   ` [PATCH net-next v7 02/10] net: dsa: realtek: rtl8365mb: add chip family infrastructure Mieczyslaw Nalewaj
2026-11-02 14:38   ` [PATCH net-next v7 03/10] net: dsa: realtek: rtl8365mb: set speed for family D Mieczyslaw Nalewaj
2026-11-04 12:20     ` Alvin Šipraga
2026-11-02 14:39   ` [PATCH net-next v7 04/10] net: dsa: realtek: rtl8365mb: set RGMII mode " Mieczyslaw Nalewaj
2026-11-04 12:39     ` Alvin Šipraga
2026-11-02 14:40   ` [PATCH net-next v7 05/10] net: dsa: realtek: rtl8365mb: set and get vlan 4k " Mieczyslaw Nalewaj
2026-11-04 12:45     ` Alvin Šipraga [this message]
2026-11-02 14:41   ` [PATCH net-next v7 06/10] net: dsa: realtek: rtl8365mb: use raw VID for PVID on " Mieczyslaw Nalewaj
2026-11-02 14:42   ` [PATCH net-next v7 07/10] net: dsa: realtek: rtl8365mb: add family D SDS13 PCS support Mieczyslaw Nalewaj
2026-11-02 14:43   ` [PATCH net-next v7 08/10] net: dsa: realtek: rtl8365mb: re-latch the family D SerDes Mieczyslaw Nalewaj
2026-11-04 12:57     ` Alvin Šipraga
2026-11-02 14:44   ` [PATCH net-next v7 09/10] net: dsa: realtek: rtl8365mb: make L2/LUT access work on family D Mieczyslaw Nalewaj
2026-11-03 15:36     ` Alvin Šipraga
2026-11-03 16:44       ` Mieczyslaw Nalewaj
2026-11-02 14:45   ` [PATCH net-next v7 10/10] net: dsa: realtek: rtl8365mb: add support for RTL8367S-VB Mieczyslaw Nalewaj
2026-11-03 22:52     ` Alvin Šipraga
2026-11-03 23:41       ` Mieczyslaw Nalewaj
2026-11-04  9:40         ` Mieczyslaw Nalewaj
2026-11-04 13:14           ` Alvin Šipraga
2026-11-04 16:37             ` Mieczyslaw Nalewaj

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=ausoMS5PcpEFz02i@analog.com \
    --to=alvin.sipraga@analog.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=luizluca@gmail.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=namiltd@yahoo.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.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®