On 02/03/18 14:55, srinivas.kandaga...@linaro.org wrote:
From: Srinivas Kandagatla <srinivas.kandaga...@linaro.org>

Many of the rpmsg clients like audio drivers need to allocate
dma memory. Make this bus DMA capable so that the child devices
can use dma apis.

AFAICS after 15 minutes in the docs and code, the rpmsg "bus" is a virtual one based around shared-memory mailbox communication, so I don't really see how DMA exists in that context - I think maybe that abstraction needs looking at.

However, from grepping through the DTs it seems at first glance like the non-trivial things under the "qcom,smd" bus mostly map to actual platform devices via the "qcom,smd-edge" property - if those platform devices are the physical DMA masters, they should be the ones used for DMA API operations.

Signed-off-by: Srinivas Kandagatla <srinivas.kandaga...@linaro.org>
  drivers/rpmsg/rpmsg_core.c | 1 +
  1 file changed, 1 insertion(+)

diff --git a/drivers/rpmsg/rpmsg_core.c b/drivers/rpmsg/rpmsg_core.c
index e84c71f8d6ab..540a3f3567b8 100644
--- a/drivers/rpmsg/rpmsg_core.c
+++ b/drivers/rpmsg/rpmsg_core.c
@@ -472,6 +472,7 @@ struct bus_type rpmsg_bus = {
        .uevent         = rpmsg_uevent,
        .probe          = rpmsg_dev_probe,
        .remove         = rpmsg_dev_remove,
+       .force_dma      = true,

Regardless of the above, would you really need to use this brute force hack instead of just fixing the DTs? I'm struggling to find which drivers might currently be relying on this :/


iommu mailing list

Reply via email to