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 5/6] net: dsa: qca: ar9331: add bridge support Date: Mon, 2 Aug 2021 17:55:29 +0300 [thread overview] Message-ID: <20210802145529.5k57qhsp7i43wmff@skbuf> (raw) In-Reply-To: <20210802131037.32326-6-o.rempel@pengutronix.de> On Mon, Aug 02, 2021 at 03:10:36PM +0200, Oleksij Rempel wrote: > This switch is providing forwarding matrix, with it we can configure > individual bridges. Potentially we can configure more than one not VLAN > based bridge on this HW. > > Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de> > Reviewed-by: Florian Fainelli <f.fainelli@gmail.com> > --- > drivers/net/dsa/qca/ar9331.c | 53 ++++++++++++++++++++++++++++++++++++ > 1 file changed, 53 insertions(+) > > diff --git a/drivers/net/dsa/qca/ar9331.c b/drivers/net/dsa/qca/ar9331.c > index d726d2f223ea..a0324fed2136 100644 > --- a/drivers/net/dsa/qca/ar9331.c > +++ b/drivers/net/dsa/qca/ar9331.c > @@ -40,6 +40,7 @@ > */ > > #include <linux/bitfield.h> > +#include <linux/if_bridge.h> > #include <linux/module.h> > #include <linux/of_irq.h> > #include <linux/of_mdio.h> > @@ -1093,6 +1094,56 @@ static int ar9331_sw_set_ageing_time(struct dsa_switch *ds, > val); > } > > +static int ar9331_sw_port_bridge_mod(struct dsa_switch *ds, int port, > + struct net_device *br, bool join) > +{ > + struct ar9331_sw_priv *priv = (struct ar9331_sw_priv *)ds->priv; > + struct regmap *regmap = priv->regmap; Reverse Christmas tree notation.. > + int port_mask = BIT(dsa_to_port(ds, port)->cpu_dp->index); Could you use dsa_upstream_port(ds, port) instead of raw access to cpu_dp? Or alternatively, you can add another condition in your "for" loop, for dsa_is_cpu_port(ds, port) => port_mask |= BIT(i); > + int i, ret; > + u32 val; > + > + for (i = 0; i < ds->num_ports; i++) { > + if (dsa_to_port(ds, i)->bridge_dev != br) > + continue; > + > + if (!dsa_is_user_port(ds, port)) > + continue; Only user ports can have a ->bridge_dev pointer populated in the first place. Also, did you mean dsa_is_user_port(ds, i)? The "port" variable is an invariant as far as this loop is concerned. > + > + val = FIELD_PREP(AR9331_SW_PORT_VLAN_PORT_VID_MEMBER, BIT(port)); > + ret = regmap_set_bits(regmap, AR9331_SW_REG_PORT_VLAN(i), val); > + if (ret) > + goto error; > + > + if (join && i != port) > + port_mask |= BIT(i); > + } > + > + val = FIELD_PREP(AR9331_SW_PORT_VLAN_PORT_VID_MEMBER, port_mask); > + ret = regmap_update_bits(regmap, AR9331_SW_REG_PORT_VLAN(port), > + AR9331_SW_PORT_VLAN_PORT_VID_MEMBER, val); > + if (ret) > + goto error; > + > + return 0; > +error: > + dev_err(priv->dev, "%s: error: %i\n", __func__, ret); > + > + return ret; > +} > + > +static int ar9331_sw_port_bridge_join(struct dsa_switch *ds, int port, > + struct net_device *br) > +{ > + return ar9331_sw_port_bridge_mod(ds, port, br, true); > +} > + > +static void ar9331_sw_port_bridge_leave(struct dsa_switch *ds, int port, > + struct net_device *br) > +{ > + ar9331_sw_port_bridge_mod(ds, port, br, false); > +} > + > static const struct dsa_switch_ops ar9331_sw_ops = { > .get_tag_protocol = ar9331_sw_get_tag_protocol, > .setup = ar9331_sw_setup, > @@ -1109,6 +1160,8 @@ static const struct dsa_switch_ops ar9331_sw_ops = { > .port_mdb_add = ar9331_sw_port_mdb_add, > .port_mdb_del = ar9331_sw_port_mdb_del, > .set_ageing_time = ar9331_sw_set_ageing_time, > + .port_bridge_join = ar9331_sw_port_bridge_join, > + .port_bridge_leave = ar9331_sw_port_bridge_leave, > }; > > static irqreturn_t ar9331_sw_irq(int irq, void *data) > -- > 2.30.2 >
next prev parent reply other threads:[~2021-08-02 14:55 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 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 [this message] 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=20210802145529.5k57qhsp7i43wmff@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).