From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: davem@davemloft.net, kuba@kernel.org
Cc: ivecera@redhat.com, andrew@lunn.ch,
alexandre.belloni@bootlin.com, f.fainelli@gmail.com,
jiri@resnulli.us, rasmus.villemoes@prevas.dk,
vladimir.oltean@nxp.com, bridge@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, UNGLinuxDriver@microchip.com,
claudiu.manoil@nxp.com, netdev@vger.kernel.org,
nikolay@nvidia.com, roopa@nvidia.com,
Horatiu Vultur <horatiu.vultur@microchip.com>,
vivien.didelot@gmail.com
Subject: [Bridge] [PATCH net-next v4 3/8] bridge: mrp: Add 'enum br_mrp_hw_support'
Date: Tue, 16 Feb 2021 22:42:00 +0100 [thread overview]
Message-ID: <20210216214205.32385-4-horatiu.vultur@microchip.com> (raw)
In-Reply-To: <20210216214205.32385-1-horatiu.vultur@microchip.com>
Add the enum br_mrp_hw_support that is used by the br_mrp_switchdev
functions to allow the SW to detect the cases where HW can't implement
the functionality or when SW is used as a backup.
Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
---
net/bridge/br_private_mrp.h | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/net/bridge/br_private_mrp.h b/net/bridge/br_private_mrp.h
index 2514954c1431..966444304c38 100644
--- a/net/bridge/br_private_mrp.h
+++ b/net/bridge/br_private_mrp.h
@@ -46,6 +46,20 @@ struct br_mrp {
struct rcu_head rcu;
};
+/* This type is returned by br_mrp_switchdev functions that allow to have a SW
+ * backup in case the HW can't implement completely the protocol.
+ * BR_MRP_NONE - means the HW can't run at all the protocol, so the SW stops
+ * configuring the node anymore.
+ * BR_MRP_SW - the HW can help the SW to run the protocol, by redirecting MRP
+ * frames to CPU.
+ * BR_MRP_HW - the HW can implement completely the protocol.
+ */
+enum br_mrp_hw_support {
+ BR_MRP_NONE,
+ BR_MRP_SW,
+ BR_MRP_HW,
+};
+
/* br_mrp.c */
int br_mrp_add(struct net_bridge *br, struct br_mrp_instance *instance);
int br_mrp_del(struct net_bridge *br, struct br_mrp_instance *instance);
--
2.27.0
next prev parent reply other threads:[~2021-02-16 21:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 21:41 [Bridge] [PATCH net-next v4 0/8] bridge: mrp: Extend br_mrp_switchdev_* Horatiu Vultur
2021-02-16 21:41 ` [Bridge] [PATCH net-next v4 1/8] switchdev: mrp: Remove CONFIG_BRIDGE_MRP Horatiu Vultur
2021-02-17 10:26 ` Vladimir Oltean
2021-02-16 21:41 ` [Bridge] [PATCH net-next v4 2/8] switchdev: mrp: Extend ring_role_mrp and in_role_mrp Horatiu Vultur
2021-02-17 10:34 ` Vladimir Oltean
2021-02-17 15:58 ` Horatiu Vultur
2021-02-17 16:09 ` Vladimir Oltean
2021-02-16 21:42 ` Horatiu Vultur [this message]
2021-02-16 21:42 ` [Bridge] [PATCH net-next v4 4/8] bridge: mrp: Extend br_mrp_switchdev to detect better the errors Horatiu Vultur
2021-02-17 10:56 ` Vladimir Oltean
2021-02-17 16:02 ` Horatiu Vultur
2021-02-16 21:42 ` [Bridge] [PATCH net-next v4 5/8] bridge: mrp: Update br_mrp to use new return values of br_mrp_switchdev Horatiu Vultur
2021-02-17 10:59 ` Vladimir Oltean
2021-02-17 16:18 ` Horatiu Vultur
2021-02-16 21:42 ` [Bridge] [PATCH net-next v4 6/8] net: mscc: ocelot: Add support for MRP Horatiu Vultur
2021-02-17 11:14 ` Vladimir Oltean
2021-02-17 16:25 ` Horatiu Vultur
2021-02-17 11:51 ` Vladimir Oltean
2021-02-16 21:42 ` [Bridge] [PATCH net-next v4 7/8] net: dsa: add MRP support Horatiu Vultur
2021-02-17 11:23 ` Vladimir Oltean
2021-02-16 21:42 ` [Bridge] [PATCH net-next v4 8/8] net: dsa: felix: Add support for MRP Horatiu Vultur
2021-02-17 10:24 ` Vladimir Oltean
2021-02-16 23:00 ` [Bridge] [PATCH net-next v4 0/8] bridge: mrp: Extend br_mrp_switchdev_* 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=20210216214205.32385-4-horatiu.vultur@microchip.com \
--to=horatiu.vultur@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=bridge@lists.linux-foundation.org \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=rasmus.villemoes@prevas.dk \
--cc=roopa@nvidia.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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