LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com> To: Oleksij Rempel <o.rempel@pengutronix.de> Cc: Andrew Lunn <andrew@lunn.ch>, Vivien Didelot <vivien.didelot@gmail.com>, Florian Fainelli <f.fainelli@gmail.com>, "David S. Miller" <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>, Russell King <linux@armlinux.org.uk>, Pengutronix Kernel Team <kernel@pengutronix.de>, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org Subject: Re: [PATCH net-next v3 2/6] net: dsa: qca: ar9331: make proper initial port defaults Date: Mon, 2 Aug 2021 17:03:45 +0300 [thread overview] Message-ID: <20210802140345.zreovwix6nuyjwjy@skbuf> (raw) In-Reply-To: <20210802131037.32326-3-o.rempel@pengutronix.de> On Mon, Aug 02, 2021 at 03:10:33PM +0200, Oleksij Rempel wrote: > Make sure that all external port are actually isolated from each other, > so no packets are leaked. > > Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de> > --- > drivers/net/dsa/qca/ar9331.c | 109 ++++++++++++++++++++++++++++++++++- > 1 file changed, 108 insertions(+), 1 deletion(-) > > diff --git a/drivers/net/dsa/qca/ar9331.c b/drivers/net/dsa/qca/ar9331.c > index 6686192e1883..2f5673ea3140 100644 > --- a/drivers/net/dsa/qca/ar9331.c > +++ b/drivers/net/dsa/qca/ar9331.c > @@ -60,10 +60,20 @@ > > #define AR9331_SW_REG_FLOOD_MASK 0x2c > #define AR9331_SW_FLOOD_MASK_BROAD_TO_CPU BIT(26) > +#define AR9331_SW_FLOOD_MASK_MULTI_FLOOD_DP GENMASK(20, 16) > +#define AR9331_SW_FLOOD_MASK_UNI_FLOOD_DP GENMASK(4, 0) > > #define AR9331_SW_REG_GLOBAL_CTRL 0x30 > #define AR9331_SW_GLOBAL_CTRL_MFS_M GENMASK(13, 0) > > +#define AR9331_SW_REG_ADDR_TABLE_CTRL 0x5c > +#define AR9331_SW_AT_ARP_EN BIT(20) > +#define AR9331_SW_AT_LEARN_CHANGE_EN BIT(18) > +#define AR9331_SW_AT_AGE_EN BIT(17) > +#define AR9331_SW_AT_AGE_TIME GENMASK(15, 0) > +/* AGE_TIME_COEF is not documented. This is "works for me" value */ > +#define AR9331_SW_AT_AGE_TIME_COEF 6900 Not documented, not used either, it seems. "Works for you" based on what? > + > #define AR9331_SW_REG_MDIO_CTRL 0x98 > #define AR9331_SW_MDIO_CTRL_BUSY BIT(31) > #define AR9331_SW_MDIO_CTRL_MASTER_EN BIT(30) > @@ -101,6 +111,46 @@ > AR9331_SW_PORT_STATUS_RX_FLOW_EN | AR9331_SW_PORT_STATUS_TX_FLOW_EN | \ > AR9331_SW_PORT_STATUS_SPEED_M) Is this patch material for "net"? If standalone ports is all that ar9331 supports, then it would better not do packet forwarding in lack of a bridge device.
next prev parent reply other threads:[~2021-08-02 14:21 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-02 13:10 [PATCH net-next v3 0/6] ar9331: mainline some parts of switch functionality Oleksij Rempel 2021-08-02 13:10 ` [PATCH net-next v3 1/6] net: dsa: qca: ar9331: reorder MDIO write sequence Oleksij Rempel 2021-08-02 14:00 ` Vladimir Oltean 2021-08-02 13:10 ` [PATCH net-next v3 2/6] net: dsa: qca: ar9331: make proper initial port defaults Oleksij Rempel 2021-08-02 14:03 ` Vladimir Oltean [this message] 2021-08-02 19:45 ` Andrew Lunn 2021-08-03 6:36 ` Oleksij Rempel 2021-08-02 19:42 ` Andrew Lunn 2021-08-02 13:10 ` [PATCH net-next v3 3/6] net: dsa: qca: ar9331: add forwarding database support Oleksij Rempel 2021-08-02 15:37 ` Vladimir Oltean 2021-08-02 13:10 ` [PATCH net-next v3 4/6] net: dsa: qca: ar9331: add ageing time support Oleksij Rempel 2021-08-02 13:10 ` [PATCH net-next v3 5/6] net: dsa: qca: ar9331: add bridge support Oleksij Rempel 2021-08-02 14:55 ` Vladimir Oltean 2021-08-07 23:08 ` Vladimir Oltean 2021-08-09 5:04 ` Oleksij Rempel 2021-08-02 13:10 ` [PATCH net-next v3 6/6] net: dsa: qca: ar9331: add vlan support Oleksij Rempel 2021-08-02 14:50 ` Vladimir Oltean
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=20210802140345.zreovwix6nuyjwjy@skbuf \ --to=olteanv@gmail.com \ --cc=andrew@lunn.ch \ --cc=davem@davemloft.net \ --cc=f.fainelli@gmail.com \ --cc=kernel@pengutronix.de \ --cc=kuba@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mips@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=netdev@vger.kernel.org \ --cc=o.rempel@pengutronix.de \ --cc=vivien.didelot@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: linkBe 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).