[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210824173237.1691654-1-dqfext@gmail.com>
Date: Wed, 25 Aug 2021 01:32:37 +0800
From: DENG Qingfang <dqfext@...il.com>
To: Vladimir Oltean <olteanv@...il.com>
Cc: Sean Wang <sean.wang@...iatek.com>,
Landen Chao <Landen.Chao@...iatek.com>,
Andrew Lunn <andrew@...n.ch>,
Vivien Didelot <vivien.didelot@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Philipp Zabel <p.zabel@...gutronix.de>,
Russell King <linux@...linux.org.uk>,
"open list:MEDIATEK SWITCH DRIVER" <netdev@...r.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@...ts.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@...ts.infradead.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next] net: dsa: mt7530: manually set up VLAN ID 0
On Tue, Aug 24, 2021 at 07:57:42PM +0300, Vladimir Oltean wrote:
> I understand that this is how you noticed the issue, but please remember
> that one can always compile a kernel with CONFIG_VLAN_8021Q=n. So the
> issue predates my patch by much longer. You might reconsider the Fixes:
> tag in light of this, maybe the patch needs to be sent to stable.
Okay. So the Fixes tag should be 6087175b7991, which initially adds the
software fallback support for mt7530.
>
> > +static int
> > +mt7530_setup_vlan0(struct mt7530_priv *priv)
> > +{
> > + u32 val;
> > +
> > + /* Validate the entry with independent learning, keep the original
> > + * ingress tag attribute.
> > + */
> > + val = IVL_MAC | EG_CON | PORT_MEM(MT7530_ALL_MEMBERS) | FID(FID_BRIDGED) |
>
> FID_BRIDGED?
What's wrong with that?
>
> > + VLAN_VALID;
> > + mt7530_write(priv, MT7530_VAWD1, val);
> > +
> > + return mt7530_vlan_cmd(priv, MT7530_VTCR_WR_VID, 0);
> > +}
>
Powered by blists - more mailing lists