diff options
author | Stephan Gerhold <[email protected]> | 2021-10-18 12:24:20 +0200 |
---|---|---|
committer | Vinod Koul <[email protected]> | 2021-10-28 22:42:30 +0530 |
commit | 37aef53f5ccf789a87006e0dcbce187ce3427f63 (patch) | |
tree | 73bc6fe07a046dec87fd7b12f810f8688f22fdd7 /tools/perf/scripts/python/syscall-counts.py | |
parent | 07c609cc987710a2874d41cf54802777b44b523b (diff) |
dt-bindings: dmaengine: bam_dma: Add "powered remotely" mode
In some configurations, the BAM DMA controller is set up by a remote
processor and the local processor can simply start making use of it
without setting up the BAM. This is already supported using the
"qcom,controlled-remotely" property.
However, for some reason another possible configuration is that the
remote processor is responsible for powering up the BAM, but we are
still responsible for initializing it (e.g. resetting it etc). Add
a "qcom,powered-remotely" property to describe that configuration.
Signed-off-by: Stephan Gerhold <[email protected]>
Acked-by: Rob Herring <[email protected]>
Reviewed-by: Bhupesh Sharma <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Vinod Koul <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions