From: Linus Walleij <linus.walleij@linaro.org>
To: Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org,
"Linus Walleij" <linus.walleij@linaro.org>,
"Alvin Šipraga" <alsi@bang-olufsen.dk>,
"Mauri Sandberg" <sandberg@mailfence.com>,
"DENG Qingfang" <dqfext@gmail.com>
Subject: [PATCH net-next 2/4 v4] net: dsa: rtl8366rb: Support flood control
Date: Wed, 29 Sep 2021 23:03:47 +0200 [thread overview]
Message-ID: <20210929210349.130099-3-linus.walleij@linaro.org> (raw)
In-Reply-To: <20210929210349.130099-1-linus.walleij@linaro.org>
Now that we have implemented bridge flag handling we can easily
support flood control as well so let's do it.
Cc: Vladimir Oltean <olteanv@gmail.com>
Cc: Alvin Šipraga <alsi@bang-olufsen.dk>
Cc: Mauri Sandberg <sandberg@mailfence.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>
Cc: DENG Qingfang <dqfext@gmail.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
ChangeLog v3->v4:
- No changes, rebased on the other patches.
ChangeLog v2->v3:
- Move the UNMC under the multicast setting as it is related to
multicast to unknown address.
- Add some more registers from the API, unfortunately we don't
know how to make use of them.
- Use tabs for indentation in copypaste bug.
- Since we don't know how to make the elaborate storm control
work just mention flood control in the message.
ChangeLog v1->v2:
- New patch
---
drivers/net/dsa/rtl8366rb.c | 55 +++++++++++++++++++++++++++++++++++--
1 file changed, 53 insertions(+), 2 deletions(-)
diff --git a/drivers/net/dsa/rtl8366rb.c b/drivers/net/dsa/rtl8366rb.c
index b3056064b937..52e750ea790e 100644
--- a/drivers/net/dsa/rtl8366rb.c
+++ b/drivers/net/dsa/rtl8366rb.c
@@ -164,6 +164,26 @@
*/
#define RTL8366RB_VLAN_INGRESS_CTRL2_REG 0x037f
+/* Storm registers are for flood control
+ *
+ * 02e2 and 02e3 are defined in the header for the RTL8366RB API
+ * but there are no usage examples. The implementation only activates
+ * the filter per port in the CTRL registers.
+ */
+#define RTL8366RB_STORM_FILTERING_1_REG 0x02e2
+#define RTL8366RB_STORM_FILTERING_PERIOD_BIT BIT(0)
+#define RTL8366RB_STORM_FILTERING_PERIOD_MSK GENMASK(1, 0)
+#define RTL8366RB_STORM_FILTERING_COUNT_BIT BIT(1)
+#define RTL8366RB_STORM_FILTERING_COUNT_MSK GENMASK(3, 2)
+#define RTL8366RB_STORM_FILTERING_BC_BIT BIT(5)
+#define RTL8366RB_STORM_FILTERING_2_REG 0x02e3
+#define RTL8366RB_STORM_FILTERING_MC_BIT BIT(0)
+#define RTL8366RB_STORM_FILTERING_UNDA_BIT BIT(5)
+#define RTL8366RB_STORM_BC_CTRL 0x03e0
+#define RTL8366RB_STORM_MC_CTRL 0x03e1
+#define RTL8366RB_STORM_UNDA_CTRL 0x03e2
+#define RTL8366RB_STORM_UNMC_CTRL 0x03e3
+
/* LED control registers */
#define RTL8366RB_LED_BLINKRATE_REG 0x0430
#define RTL8366RB_LED_BLINKRATE_MASK 0x0007
@@ -1282,8 +1302,8 @@ rtl8366rb_port_pre_bridge_flags(struct dsa_switch *ds, int port,
struct switchdev_brport_flags flags,
struct netlink_ext_ack *extack)
{
- /* We support enabling/disabling learning */
- if (flags.mask & ~(BR_LEARNING))
+ if (flags.mask & ~(BR_LEARNING | BR_BCAST_FLOOD |
+ BR_MCAST_FLOOD | BR_FLOOD))
return -EINVAL;
return 0;
@@ -1305,6 +1325,37 @@ rtl8366rb_port_bridge_flags(struct dsa_switch *ds, int port,
return ret;
}
+ if (flags.mask & BR_BCAST_FLOOD) {
+ ret = regmap_update_bits(smi->map, RTL8366RB_STORM_BC_CTRL,
+ BIT(port),
+ (flags.val & BR_BCAST_FLOOD) ? BIT(port) : 0);
+ if (ret)
+ return ret;
+ }
+
+ if (flags.mask & BR_MCAST_FLOOD) {
+ ret = regmap_update_bits(smi->map, RTL8366RB_STORM_MC_CTRL,
+ BIT(port),
+ (flags.val & BR_MCAST_FLOOD) ? BIT(port) : 0);
+ if (ret)
+ return ret;
+ /* UNMC = Unknown multicast address */
+ ret = regmap_update_bits(smi->map, RTL8366RB_STORM_UNMC_CTRL,
+ BIT(port),
+ (flags.val & BR_FLOOD) ? BIT(port) : 0);
+ if (ret)
+ return ret;
+ }
+
+ if (flags.mask & BR_FLOOD) {
+ /* UNDA = Unknown destination address */
+ ret = regmap_update_bits(smi->map, RTL8366RB_STORM_UNDA_CTRL,
+ BIT(port),
+ (flags.val & BR_FLOOD) ? BIT(port) : 0);
+ if (ret)
+ return ret;
+ }
+
return 0;
}
--
2.31.1
next prev parent reply other threads:[~2021-09-29 21:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 21:03 [PATCH net-next 0/4 v4] RTL8366RB enhancements Linus Walleij
2021-09-29 21:03 ` [PATCH net-next 1/4 v4] net: dsa: rtl8366rb: Support disabling learning Linus Walleij
2021-09-29 21:58 ` Vladimir Oltean
2021-09-30 10:45 ` Alvin Šipraga
2021-10-04 20:57 ` Linus Walleij
2021-10-05 7:59 ` Alvin Šipraga
2021-10-05 14:07 ` Linus Walleij
2021-10-05 14:45 ` Alvin Šipraga
2021-09-29 21:03 ` Linus Walleij [this message]
2021-09-29 21:57 ` [PATCH net-next 2/4 v4] net: dsa: rtl8366rb: Support flood control Vladimir Oltean
2021-09-30 9:09 ` Alvin Šipraga
2021-10-04 22:22 ` Linus Walleij
2021-09-29 21:03 ` [PATCH net-next 3/4 v4] net: dsa: rtl8366rb: Support fast aging Linus Walleij
2021-09-29 21:45 ` Vladimir Oltean
2021-10-04 22:41 ` Linus Walleij
2021-09-29 21:03 ` [PATCH net-next 4/4 v4] net: dsa: rtl8366rb: Support setting STP state Linus Walleij
2021-09-29 21:54 ` Vladimir Oltean
2021-10-04 21:07 ` Linus Walleij
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=20210929210349.130099-3-linus.walleij@linaro.org \
--to=linus.walleij@linaro.org \
--cc=alsi@bang-olufsen.dk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=sandberg@mailfence.com \
--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: 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