summaryrefslogtreecommitdiff
path: root/net/Makefile
diff options
context:
space:
mode:
authorSiddharth Vadapalli <s-vadapalli@ti.com>2024-01-24 15:43:19 +0300
committerVinod Koul <vkoul@kernel.org>2024-01-30 19:43:52 +0300
commite54df52312fed462a005706d5d7ed6250da91d1e (patch)
tree29a0d9d2a4dd86957c1b98e0d2f02ae65ad968e1 /net/Makefile
parent7cbf7f4bf71a054d687c8860380c655a36d0f369 (diff)
downloadlinux-e54df52312fed462a005706d5d7ed6250da91d1e.tar.xz
dmaengine: ti: k3-udma-glue: Add function to request RX chan for thread ID
The existing function k3_udma_glue_request_remote_rx_chn() supports requesting an RX DMA channel and flow by the name of the RX DMA channel. Add support to request RX DMA channel for a given thread ID in the form of a new function named k3_udma_glue_request_remote_rx_chn_for_thread_id(). Also, export it for use by drivers which are probed by alternate methods (non device-tree) but still wish to make use of the existing DMA APIs. Such drivers could be informed about the thread ID corresponding to the RX DMA channel by RPMsg for example. Since the new function k3_udma_glue_request_remote_rx_chn_for_thread_id() reuses most of the code in k3_udma_glue_request_remote_rx_chn(), create a new function named k3_udma_glue_request_remote_rx_chn_common() for the common code. Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com> Acked-by: Peter Ujfalusi <peter.ujfalusi@gmail.com> Link: https://lore.kernel.org/r/20240124124319.820002-5-s-vadapalli@ti.com Signed-off-by: Vinod Koul <vkoul@kernel.org>
Diffstat (limited to 'net/Makefile')
0 files changed, 0 insertions, 0 deletions