From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <davem@davemloft.net>, <kuba@kernel.org>,
<vladimir.oltean@nxp.com>, <claudiu.manoil@nxp.com>,
<alexandre.belloni@bootlin.com>, <andrew@lunn.ch>,
<vivien.didelot@gmail.com>, <f.fainelli@gmail.com>
Cc: <UNGLinuxDriver@microchip.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: [PATCH net-next v2 0/3] net: ocelot: Extend MRP
Date: Tue, 16 Mar 2021 21:10:16 +0100 [thread overview]
Message-ID: <20210316201019.3081237-1-horatiu.vultur@microchip.com> (raw)
This patch series extends the current support of MRP in Ocelot driver.
Currently the forwarding of the frames happened in SW because all frames
were trapped to CPU. With this patch the MRP frames will be forward in HW.
v1 -> v2:
- create a patch series instead of single patch
- rename ocelot_mrp_find_port to ocelot_mrp_find_partner_port
- rename PGID_MRP to PGID_BLACKHOLE
- use GFP_KERNEL instead of GFP_ATOMIC
- fix other whitespace issues
Horatiu Vultur (3):
net: ocelot: Add PGID_BLACKHOLE
net: ocelot: Extend MRP
net: ocelot: Remove ocelot_xfh_get_cpuq
drivers/net/ethernet/mscc/ocelot.c | 12 +-
drivers/net/ethernet/mscc/ocelot_mrp.c | 233 +++++++++++++++++--------
include/linux/dsa/ocelot.h | 5 -
include/soc/mscc/ocelot.h | 12 +-
net/dsa/tag_ocelot.c | 8 -
5 files changed, 167 insertions(+), 103 deletions(-)
--
2.30.1
next reply other threads:[~2021-03-16 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 20:10 Horatiu Vultur [this message]
2021-03-16 20:10 ` [PATCH net-next v2 1/3] net: ocelot: Add PGID_BLACKHOLE Horatiu Vultur
2021-03-16 23:13 ` Vladimir Oltean
2021-03-16 20:10 ` [PATCH net-next v2 2/3] net: ocelot: Extend MRP Horatiu Vultur
2021-03-16 23:22 ` Vladimir Oltean
2021-03-16 20:10 ` [PATCH net-next v2 3/3] net: ocelot: Remove ocelot_xfh_get_cpuq Horatiu Vultur
2021-03-16 23:24 ` Vladimir Oltean
2021-03-16 23:30 ` [PATCH net-next v2 0/3] net: ocelot: Extend MRP 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=20210316201019.3081237-1-horatiu.vultur@microchip.com \
--to=horatiu.vultur@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).