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
