From: Vinod Koul <vkoul@kernel.org>
To: peter.ujfalusi@gmail.com, Siddharth Vadapalli <s-vadapalli@ti.com>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, srk@ti.com,
vigneshr@ti.com
Subject: Re: [PATCH v4 0/4] Add APIs to request TX/RX DMA channels for thread ID
Date: Tue, 30 Jan 2024 22:21:03 +0530 [thread overview]
Message-ID: <170663346383.658154.6469293255184472126.b4-ty@kernel.org> (raw)
In-Reply-To: <20240124124319.820002-1-s-vadapalli@ti.com>
On Wed, 24 Jan 2024 18:13:15 +0530, Siddharth Vadapalli wrote:
> 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 via RPMsg regarding the
> allocated TX/RX DMA channel thread IDs. In such cases, the driver can be
> probed by non device-tree methods such as RPMsg-bus, due to which it is not
> necessary that the device using the DMA has a device-tree node
> corresponding to it. Thus, add APIs to enable the driver to make use of
> the existing DMA APIs even when there's no device-tree node.
>
> [...]
Applied, thanks!
[1/4] dmaengine: ti: k3-udma-glue: Add function to parse channel by ID
commit: 81a1f90f20af71728f900f245aa69e9425fdef84
[2/4] dmaengine: ti: k3-udma-glue: Update name for remote RX channel device
commit: 7edd7a2fd345b10e80ee854aaacc6452d6f46a7e
[3/4] dmaengine: ti: k3-udma-glue: Add function to request TX chan for thread ID
commit: 7cbf7f4bf71a054d687c8860380c655a36d0f369
[4/4] dmaengine: ti: k3-udma-glue: Add function to request RX chan for thread ID
commit: e54df52312fed462a005706d5d7ed6250da91d1e
Best regards,
--
~Vinod
prev parent reply other threads:[~2024-01-30 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 12:43 [PATCH v4 0/4] Add APIs to request TX/RX DMA channels for thread ID Siddharth Vadapalli
2024-01-24 12:43 ` [PATCH v4 1/4] dmaengine: ti: k3-udma-glue: Add function to parse channel by ID Siddharth Vadapalli
2024-01-24 12:43 ` [PATCH v4 2/4] dmaengine: ti: k3-udma-glue: Update name for remote RX channel device Siddharth Vadapalli
2024-01-24 12:43 ` [PATCH v4 3/4] dmaengine: ti: k3-udma-glue: Add function to request TX chan for thread ID Siddharth Vadapalli
2024-01-24 12:43 ` [PATCH v4 4/4] dmaengine: ti: k3-udma-glue: Add function to request RX " Siddharth Vadapalli
2024-01-30 16:51 ` Vinod Koul [this message]
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=170663346383.658154.6469293255184472126.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@gmail.com \
--cc=s-vadapalli@ti.com \
--cc=srk@ti.com \
--cc=vigneshr@ti.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 read-only IMAP folder(s) and NNTP newsgroup(s).