From: Siddharth Vadapalli <s-vadapalli@ti.com>
To: <peter.ujfalusi@gmail.com>, <vkoul@kernel.org>
Cc: <dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <srk@ti.com>,
<vigneshr@ti.com>, <s-vadapalli@ti.com>
Subject: [PATCH 0/4] Add APIs to request TX/RX DMA channels by ID
Date: Tue, 14 Nov 2023 14:09:02 +0530 [thread overview]
Message-ID: <20231114083906.3143548-1-s-vadapalli@ti.com> (raw)
The existing APIs for requesting TX and RX DMA channels rely on parsing
a device-tree node to obtain the Channel/Thread IDs from their names.
However, it is possible to know the thread IDs by alternative means such
as being informed by Firmware on a remote core regarding the allocated
TX/RX DMA channel IDs. Thus, add APIs to support such use cases.
Additionally, since the name of the device for the remote RX channel is
being set purely on the basis of the RX channel ID itself, it can result
in duplicate names when multiple flows are used on the same channel.
Avoid name duplication by including the flow in the name.
Series is based on linux-next tagged next-20231114.
RFC Series:
https://lore.kernel.org/r/20231111121555.2656760-1-s-vadapalli@ti.com/
Changes since RFC Series:
- Rebased patches 1, 2 and 3 on linux-next tagged next-20231114.
- Added patch 4 to the series.
Regards,
Siddharth.
Siddharth Vadapalli (4):
dmaengine: ti: k3-udma-glue: Add function to parse channel by ID
dmaengine: ti: k3-udma-glue: Add function to request TX channel by ID
dmaengine: ti: k3-udma-glue: Add function to request RX channel by ID
dmaengine: ti: k3-udma-glue: Update name for remote RX channel device
drivers/dma/ti/k3-udma-glue.c | 306 ++++++++++++++++++++++---------
include/linux/dma/k3-udma-glue.h | 8 +
2 files changed, 228 insertions(+), 86 deletions(-)
--
2.34.1
next reply other threads:[~2023-11-14 8:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 8:39 Siddharth Vadapalli [this message]
2023-11-14 8:39 ` [PATCH 1/4] dmaengine: ti: k3-udma-glue: Add function to parse channel by ID Siddharth Vadapalli
2023-11-14 8:39 ` [PATCH 2/4] dmaengine: ti: k3-udma-glue: Add function to request TX " Siddharth Vadapalli
2023-11-14 8:39 ` [PATCH 3/4] dmaengine: ti: k3-udma-glue: Add function to request RX " Siddharth Vadapalli
2023-11-14 8:39 ` [PATCH 4/4] dmaengine: ti: k3-udma-glue: Update name for remote RX channel device Siddharth Vadapalli
2023-11-15 19:59 ` [PATCH 0/4] Add APIs to request TX/RX DMA channels by ID Péter Ujfalusi
2023-11-17 5:55 ` Siddharth Vadapalli
2023-11-22 15:22 ` Péter Ujfalusi
2023-12-04 8:21 ` Siddharth Vadapalli
2023-12-11 9:00 ` Siddharth Vadapalli
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=20231114083906.3143548-1-s-vadapalli@ti.com \
--to=s-vadapalli@ti.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=srk@ti.com \
--cc=vigneshr@ti.com \
--cc=vkoul@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