linux-kernel - Re: [PATCH] dmaengine: stm32-dmamux: avoid reset of dmamux if used by coprocessor

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 19 May 2022 23:19:37 +0530
From:   Vinod Koul <vkoul@...nel.org>
To:     Amelie Delaunay <amelie.delaunay@...s.st.com>
Cc:     Maxime Coquelin <mcoquelin.stm32@...il.com>,
        Alexandre Torgue <alexandre.torgue@...s.st.com>,
        dmaengine@...r.kernel.org,
        linux-stm32@...md-mailman.stormreply.com,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dmaengine: stm32-dmamux: avoid reset of dmamux if used
 by coprocessor

On 04-05-22, 18:17, Amelie Delaunay wrote:
> One of the two DMA controllers managed by the DMAMUX can be used by the
> coprocessor. It is defined in the device tree with dma-masters.
> When the two DMA controllers are used by the main CPU,
> dma-masters = <&dma1, &dma2>; is specified in the device tree.
> When one of the controllers is used by coprocessor (so not managed by
> Linux), dma-masters = <&dma1>; is specified in the device tree.
> In this case, Linux driver must not reset the DMAMUX, because it could have
> been configured by the coprocessor to use the second DMA controller.
> count is the number of DMA controllers defined in dma-masters property.
> Reset only if resets property is found and valid in device tree, and if
> the two DMA controllers are under Linux control.

Applied, thanks

-- 
~Vinod