From: Vinod Koul <vkoul@kernel.org>
To: Amelie Delaunay <amelie.delaunay@foss.st.com>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
dmaengine@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: stm32-dmamux: avoid reset of dmamux if used by coprocessor
Date: Thu, 19 May 2022 23:19:37 +0530 [thread overview]
Message-ID: <YoaDMTRk07ot2p7B@matsya> (raw)
In-Reply-To: <20220504161724.123180-1-amelie.delaunay@foss.st.com>
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-05-19 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 16:17 [PATCH] dmaengine: stm32-dmamux: avoid reset of dmamux if used by coprocessor Amelie Delaunay
2022-05-19 17:49 ` Vinod Koul [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YoaDMTRk07ot2p7B@matsya \
--to=vkoul@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=amelie.delaunay@foss.st.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).