mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: MD Danish Anwar <danishanwar@ti.com>
Cc: Rob Herring <robh@kernel.org>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Vladimir Oltean <vladimir.oltean@nxp.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Grygorii Strashko <grygorii.strashko@ti.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Roger Quadros <rogerq@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	"David S. Miller" <davem@davemloft.net>,
	linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, srk@ti.com, r-gunasekaran@ti.com
Subject: Re: [RFC PATCH v2 2/3] net: ti: icssg-switch: Add switchdev based driver for ethernet switch support
Date: Fri, 19 Jan 2024 15:12:04 +0100	[thread overview]
Message-ID: <3ea8934e-c41f-4366-a0c4-1894ed4e3d7e@lunn.ch> (raw)
In-Reply-To: <20240118071005.1514498-3-danishanwar@ti.com>

> +static int prueth_switchdev_stp_state_set(struct prueth_emac *emac,
> +					  u8 state)
> +{
> +	enum icssg_port_state_cmd emac_state;
> +	int ret = 0;
> +
> +	switch (state) {
> +	case BR_STATE_FORWARDING:
> +		emac_state = ICSSG_EMAC_PORT_FORWARD;
> +		break;
> +	case BR_STATE_DISABLED:
> +		emac_state = ICSSG_EMAC_PORT_DISABLE;
> +		break;
> +	case BR_STATE_LEARNING:
> +	case BR_STATE_LISTENING:
> +	case BR_STATE_BLOCKING:
> +		emac_state = ICSSG_EMAC_PORT_BLOCK;
> +		break;

That is unusual. Does it still learn while in BLOCK? It might be you
need to flush the FDB for this port when it changes from BLOCKING to
LISTENING or LEARNING?

> +static void prueth_switchdev_event_work(struct work_struct *work)
> +{
> +	struct prueth_switchdev_event_work *switchdev_work =
> +		container_of(work, struct prueth_switchdev_event_work, work);
> +	struct prueth_emac *emac = switchdev_work->emac;
> +	struct switchdev_notifier_fdb_info *fdb;
> +	int port_id = emac->port_id;
> +	int ret;
> +
> +	rtnl_lock();
> +	switch (switchdev_work->event) {
> +	case SWITCHDEV_FDB_ADD_TO_DEVICE:
> +		fdb = &switchdev_work->fdb_info;
> +
> +		netdev_dbg(emac->ndev, "prueth_fdb_add: MACID = %pM vid = %u flags = %u %u -- port %d\n",
> +			   fdb->addr, fdb->vid, fdb->added_by_user,
> +			   fdb->offloaded, port_id);
> +
> +		if (!fdb->added_by_user)
> +			break;
> +		if (memcmp(emac->mac_addr, (u8 *)fdb->addr, ETH_ALEN) == 0)
> +			break;

ether_addr_equal(). Please review all the code and use these helpers
when possible.

So you don't add an FDB for the interfaces own MAC address? Does the
switch know the interfaces MAC address?

       Andrew

  reply	other threads:[~2024-01-19 14:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18  7:10 [RFC PATCH v2 0/3] Introduce switch mode support for ICSSG driver MD Danish Anwar
2024-01-18  7:10 ` [RFC PATCH v2 1/3] net: ti: icssg-prueth: Add helper functions to configure FDB MD Danish Anwar
2024-01-19 13:55   ` Andrew Lunn
2024-01-22 10:48     ` MD Danish Anwar
2024-01-18  7:10 ` [RFC PATCH v2 2/3] net: ti: icssg-switch: Add switchdev based driver for ethernet switch support MD Danish Anwar
2024-01-19 14:12   ` Andrew Lunn [this message]
2024-01-22 11:08     ` MD Danish Anwar
2024-03-19  9:49       ` MD Danish Anwar
2024-01-19 20:40   ` Simon Horman
2024-01-22  7:54     ` MD Danish Anwar
2024-01-18  7:10 ` [RFC PATCH v2 3/3] net: ti: icssg-prueth: Add support for ICSSG switch firmware MD Danish Anwar
2024-01-19 14:29   ` Andrew Lunn
2024-01-22 10:35     ` MD Danish Anwar
2024-01-19 20:41   ` Simon Horman
2024-01-22  7:52     ` MD Danish Anwar
2024-01-18 14:01 ` [RFC PATCH v2 0/3] Introduce switch mode support for ICSSG driver Andrew Lunn
2024-01-22 10:45   ` MD Danish Anwar

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=3ea8934e-c41f-4366-a0c4-1894ed4e3d7e@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=dan.carpenter@linaro.org \
    --cc=danishanwar@ti.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=grygorii.strashko@ti.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=r-gunasekaran@ti.com \
    --cc=robh@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=srk@ti.com \
    --cc=vigneshr@ti.com \
    --cc=vladimir.oltean@nxp.com \
    --cc=wsa+renesas@sang-engineering.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®