linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Olivier Moysan <olivier.moysan@foss.st.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Olivier Moysan <olivier.moysan@st.com>,
	"Rob Herring" <robh+dt@kernel.org>
Cc: <devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH] ARM: dts: stm32: fix SAI sub nodes register range
Date: Fri, 15 Oct 2021 15:01:57 +0200	[thread overview]
Message-ID: <f2c206ad-503b-3652-8741-d4c660b8dedf@foss.st.com> (raw)
In-Reply-To: <20210924160221.13287-1-olivier.moysan@foss.st.com>

On 9/24/21 6:02 PM, Olivier Moysan wrote:
> The STM32 SAI subblocks registers offsets are in the range
> 0x0004 (SAIx_CR1) to 0x0020 (SAIx_DR).
> The corresponding range length is 0x20 instead of 0x1c.
> Change reg property accordingly.
> 
> Fixes: 5afd65c3a060 ("ARM: dts: stm32: add sai support on stm32mp157c")
> 
> Signed-off-by: Olivier Moysan <olivier.moysan@foss.st.com>
> ---
>   arch/arm/boot/dts/stm32mp151.dtsi | 16 ++++++++--------
>   1 file changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/arch/arm/boot/dts/stm32mp151.dtsi b/arch/arm/boot/dts/stm32mp151.dtsi
> index bd289bf5d269..6992a4b0ba79 100644
> --- a/arch/arm/boot/dts/stm32mp151.dtsi
> +++ b/arch/arm/boot/dts/stm32mp151.dtsi
> @@ -824,7 +824,7 @@
>   				#sound-dai-cells = <0>;
>   
>   				compatible = "st,stm32-sai-sub-a";
> -				reg = <0x4 0x1c>;
> +				reg = <0x4 0x20>;
>   				clocks = <&rcc SAI1_K>;
>   				clock-names = "sai_ck";
>   				dmas = <&dmamux1 87 0x400 0x01>;
> @@ -834,7 +834,7 @@
>   			sai1b: audio-controller@4400a024 {
>   				#sound-dai-cells = <0>;
>   				compatible = "st,stm32-sai-sub-b";
> -				reg = <0x24 0x1c>;
> +				reg = <0x24 0x20>;
>   				clocks = <&rcc SAI1_K>;
>   				clock-names = "sai_ck";
>   				dmas = <&dmamux1 88 0x400 0x01>;
> @@ -855,7 +855,7 @@
>   			sai2a: audio-controller@4400b004 {
>   				#sound-dai-cells = <0>;
>   				compatible = "st,stm32-sai-sub-a";
> -				reg = <0x4 0x1c>;
> +				reg = <0x4 0x20>;
>   				clocks = <&rcc SAI2_K>;
>   				clock-names = "sai_ck";
>   				dmas = <&dmamux1 89 0x400 0x01>;
> @@ -865,7 +865,7 @@
>   			sai2b: audio-controller@4400b024 {
>   				#sound-dai-cells = <0>;
>   				compatible = "st,stm32-sai-sub-b";
> -				reg = <0x24 0x1c>;
> +				reg = <0x24 0x20>;
>   				clocks = <&rcc SAI2_K>;
>   				clock-names = "sai_ck";
>   				dmas = <&dmamux1 90 0x400 0x01>;
> @@ -886,7 +886,7 @@
>   			sai3a: audio-controller@4400c004 {
>   				#sound-dai-cells = <0>;
>   				compatible = "st,stm32-sai-sub-a";
> -				reg = <0x04 0x1c>;
> +				reg = <0x04 0x20>;
>   				clocks = <&rcc SAI3_K>;
>   				clock-names = "sai_ck";
>   				dmas = <&dmamux1 113 0x400 0x01>;
> @@ -896,7 +896,7 @@
>   			sai3b: audio-controller@4400c024 {
>   				#sound-dai-cells = <0>;
>   				compatible = "st,stm32-sai-sub-b";
> -				reg = <0x24 0x1c>;
> +				reg = <0x24 0x20>;
>   				clocks = <&rcc SAI3_K>;
>   				clock-names = "sai_ck";
>   				dmas = <&dmamux1 114 0x400 0x01>;
> @@ -1271,7 +1271,7 @@
>   			sai4a: audio-controller@50027004 {
>   				#sound-dai-cells = <0>;
>   				compatible = "st,stm32-sai-sub-a";
> -				reg = <0x04 0x1c>;
> +				reg = <0x04 0x20>;
>   				clocks = <&rcc SAI4_K>;
>   				clock-names = "sai_ck";
>   				dmas = <&dmamux1 99 0x400 0x01>;
> @@ -1281,7 +1281,7 @@
>   			sai4b: audio-controller@50027024 {
>   				#sound-dai-cells = <0>;
>   				compatible = "st,stm32-sai-sub-b";
> -				reg = <0x24 0x1c>;
> +				reg = <0x24 0x20>;
>   				clocks = <&rcc SAI4_K>;
>   				clock-names = "sai_ck";
>   				dmas = <&dmamux1 100 0x400 0x01>;
> 

Applied on stm32-next.

Thanks
Alex


      reply	other threads:[~2021-10-15 13:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-24 16:02 [PATCH] ARM: dts: stm32: fix SAI sub nodes register range Olivier Moysan
2021-10-15 13:01 ` 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=f2c206ad-503b-3652-8741-d4c660b8dedf@foss.st.com \
    --to=alexandre.torgue@foss.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=olivier.moysan@foss.st.com \
    --cc=olivier.moysan@st.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).