From: Steen Hegelund <steen.hegelund@microchip.com>
To: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, <UNGLinuxDriver@microchip.com>,
<netdev@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: Steen Hegelund <steen.hegelund@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: [PATCH net-next v2 0/2] Adding Frame DMA functionality to Sparx5
Date: Thu, 19 Aug 2021 09:39:38 +0200 [thread overview]
Message-ID: <20210819073940.1589383-1-steen.hegelund@microchip.com> (raw)
v2:
Removed an unused variable (proc_ctrl) from sparx5_fdma_start.
This add frame DMA functionality to the Sparx5 platform.
Until now the Sparx5 SwitchDev driver has been using register based
injection and extraction when sending frames to/from the host CPU.
With this series the Frame DMA functionality now added.
The Frame DMA is only used if the Frame DMA interrupt is configured in the
device tree; otherwise the existing register based injection and extraction
is used.
The Sparx5 has two ports that can be used for sending and receiving frames,
but there are 8 channels that can be configured: 6 for injection and 2 for
extraction.
The additional channels can be used for more advanced scenarios e.g. where
virtual cores are used, but currently the driver only uses port 0 and
channel 0 and 6 respectively.
DCB (data control block) structures are passed to the Frame DMA with
suitable information about frame start/end etc, as well as pointers to DB
(data blocks) buffers.
The Frame DMA engine can use interrupts to signal back when the frames have
been injected or extracted.
There is a limitation on the DB alignment also for injection: Block must
start on 16byte boundaries, and this is why the driver currently copies the
data to into separate buffers.
The Sparx5 switch core needs a IFH (Internal Frame Header) to pass
information from the port to the switch core, and this header is added
before injection and stripped after extraction.
Steen Hegelund (2):
net: sparx5: switchdev: adding frame DMA functionality
arm64: dts: sparx5: Add the Sparx5 switch frame DMA support
arch/arm64/boot/dts/microchip/sparx5.dtsi | 5 +-
.../net/ethernet/microchip/sparx5/Makefile | 2 +-
.../ethernet/microchip/sparx5/sparx5_fdma.c | 593 ++++++++++++++++++
.../ethernet/microchip/sparx5/sparx5_main.c | 23 +-
.../ethernet/microchip/sparx5/sparx5_main.h | 69 ++
.../ethernet/microchip/sparx5/sparx5_packet.c | 13 +-
.../ethernet/microchip/sparx5/sparx5_port.c | 2 +-
.../ethernet/microchip/sparx5/sparx5_port.h | 1 +
8 files changed, 696 insertions(+), 12 deletions(-)
create mode 100644 drivers/net/ethernet/microchip/sparx5/sparx5_fdma.c
--
2.32.0
next reply other threads:[~2021-08-19 7:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 7:39 Steen Hegelund [this message]
2021-08-19 7:39 ` [PATCH net-next v2 1/2] net: sparx5: switchdev: adding frame DMA functionality Steen Hegelund
2021-08-19 7:39 ` [PATCH net-next v2 2/2] arm64: dts: sparx5: Add the Sparx5 switch frame DMA support Steen Hegelund
2021-08-20 13:40 ` [PATCH net-next v2 0/2] Adding Frame DMA functionality to Sparx5 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=20210819073940.1589383-1-steen.hegelund@microchip.com \
--to=steen.hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).