On Mon, 18 Oct 2021 12:24:20 +0200, Stephan Gerhold wrote: > 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 <stephan@xxxxxxxxxxx> > --- > Changes in v3: None, split from BAM-DMUX patch set > Changes since RFC: > - Rename qcom,remote-power-collapse -> qcom,powered-remotely > for consistency with "qcom,controlled-remotely" > > Also note that there is an ongoing effort to convert these bindings > to DT schema but sadly there were not any updates for a while. :/ > https://lore.kernel.org/linux-arm-msm/20210519143700.27392-2-bhupesh.sharma@xxxxxxxxxx/ > --- > Documentation/devicetree/bindings/dma/qcom_bam_dma.txt | 2 ++ > 1 file changed, 2 insertions(+) > Acked-by: Rob Herring <robh@xxxxxxxxxx>
