From: Angelo Dureghello <angelo@kernel-space.org>
To: andrew@lunn.ch, vivien.didelot@gmail.com, olteanv@gmail.com
Cc: netdev@vger.kernel.org,
Angelo Dureghello <angelo.dureghello@timesys.com>
Subject: [PATCH v2] net: dsa: mv88e6xxx: add mv88e6321 rsvd2cpu
Date: Wed, 26 Apr 2023 22:28:15 +0200 [thread overview]
Message-ID: <20230426202815.2991822-1-angelo@kernel-space.org> (raw)
From: Angelo Dureghello <angelo.dureghello@timesys.com>
Add rsvd2cpu capability for mv88e6321 model, to allow proper bpdu
processing.
Signed-off-by: Angelo Dureghello <angelo.dureghello@timesys.com>
Fixes: 51c901a775621 ("net: dsa: mv88e6xxx: distinguish Global 2 Rsvd2CPU")
---
Changes for v2:
- use mv88e6352_g2_mgmt_rsvd2cpu instead of mv88e6185_g2_mgmt_rsvd2cpu
---
drivers/net/dsa/mv88e6xxx/chip.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/dsa/mv88e6xxx/chip.c b/drivers/net/dsa/mv88e6xxx/chip.c
index 7108f745fbf0..902f40721340 100644
--- a/drivers/net/dsa/mv88e6xxx/chip.c
+++ b/drivers/net/dsa/mv88e6xxx/chip.c
@@ -5182,6 +5182,7 @@ static const struct mv88e6xxx_ops mv88e6321_ops = {
.set_cpu_port = mv88e6095_g1_set_cpu_port,
.set_egress_port = mv88e6095_g1_set_egress_port,
.watchdog_ops = &mv88e6390_watchdog_ops,
+ .mgmt_rsvd2cpu = mv88e6352_g2_mgmt_rsvd2cpu,
.reset = mv88e6352_g1_reset,
.vtu_getnext = mv88e6185_g1_vtu_getnext,
.vtu_loadpurge = mv88e6185_g1_vtu_loadpurge,
--
2.40.0
next reply other threads:[~2023-04-26 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 20:28 Angelo Dureghello [this message]
2023-04-26 20:58 ` [PATCH v2] net: dsa: mv88e6xxx: add mv88e6321 rsvd2cpu Andrew Lunn
2023-04-28 9:00 ` patchwork-bot+netdevbpf
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=20230426202815.2991822-1-angelo@kernel-space.org \
--to=angelo@kernel-space.org \
--cc=andrew@lunn.ch \
--cc=angelo.dureghello@timesys.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.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;
as well as URLs for NNTP newsgroup(s).