From: Alexandre Torgue <alexandre.torgue@st.com>
To: Amelie Delaunay <amelie.delaunay@st.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh+dt@kernel.org>
Cc: <linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] ARM: dts: stm32: fix mdma1 clients channel priority level on stm32mp151
Date: Tue, 17 Nov 2020 10:46:11 +0100 [thread overview]
Message-ID: <3be2f6c9-609a-3ecc-ebae-31ae24859493@st.com> (raw)
In-Reply-To: <20201110143641.13879-1-amelie.delaunay@st.com>
Hi,
On 11/10/20 3:36 PM, Amelie Delaunay wrote:
> Update mdma1 clients channel priority level following stm32-mdma bindings.
>
> Signed-off-by: Amelie Delaunay <amelie.delaunay@st.com>
> ---
> arch/arm/boot/dts/stm32mp151.dtsi | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/boot/dts/stm32mp151.dtsi b/arch/arm/boot/dts/stm32mp151.dtsi
> index 719a4276a348..b95c46c82223 100644
> --- a/arch/arm/boot/dts/stm32mp151.dtsi
> +++ b/arch/arm/boot/dts/stm32mp151.dtsi
> @@ -1294,7 +1294,7 @@
> interrupts = <GIC_SPI 80 IRQ_TYPE_LEVEL_HIGH>;
> clocks = <&rcc HASH1>;
> resets = <&rcc HASH1_R>;
> - dmas = <&mdma1 31 0x10 0x1000A02 0x0 0x0>;
> + dmas = <&mdma1 31 0x2 0x1000A02 0x0 0x0>;
> dma-names = "in";
> dma-maxburst = <2>;
> status = "disabled";
> @@ -1358,8 +1358,8 @@
> reg = <0x58003000 0x1000>, <0x70000000 0x10000000>;
> reg-names = "qspi", "qspi_mm";
> interrupts = <GIC_SPI 92 IRQ_TYPE_LEVEL_HIGH>;
> - dmas = <&mdma1 22 0x10 0x100002 0x0 0x0>,
> - <&mdma1 22 0x10 0x100008 0x0 0x0>;
> + dmas = <&mdma1 22 0x2 0x100002 0x0 0x0>,
> + <&mdma1 22 0x2 0x100008 0x0 0x0>;
> dma-names = "tx", "rx";
> clocks = <&rcc QSPI_K>;
> resets = <&rcc QSPI_R>;
>
Applied on stm32-next.
Thanks.
Alex
prev parent reply other threads:[~2020-11-17 9:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 14:36 [PATCH 1/1] ARM: dts: stm32: fix mdma1 clients channel priority level on stm32mp151 Amelie Delaunay
2020-11-17 9:46 ` Alexandre Torgue [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=3be2f6c9-609a-3ecc-ebae-31ae24859493@st.com \
--to=alexandre.torgue@st.com \
--cc=amelie.delaunay@st.com \
--cc=devicetree@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 \
--cc=robh+dt@kernel.org \
/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).