mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Jihed Chaibi <jihed.chaibi.dev@gmail.com>,
	<mcoquelin.stm32@gmail.com>, <robh@kernel.org>
Cc: <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<shuah@kernel.org>
Subject: Re: [PATCH] ARM: dts: stm32: stm32mp151c-plyaqm: Use correct dai-format property
Date: Wed, 3 Sep 2025 09:38:19 +0200	[thread overview]
Message-ID: <667a4a36-5b5a-4a45-9300-d0abd10d4b53@foss.st.com> (raw)
In-Reply-To: <20250830225115.303663-1-jihed.chaibi.dev@gmail.com>

Hi Jihed

On 8/31/25 00:51, Jihed Chaibi wrote:
> The stm32-i2s binding inherits from the standard audio-graph-port
> schema for its 'port' subnode, audio-graph-port requires the use
> of the 'dai-format' property. The stm32mp151c-plyaqm dts file was
> using the non-standard name 'format'.
> 
> Correct the property name to 'dai-format' to fix the dtbs_check
> validation error.
> 
> Fixes: 9365fa46be358 ("ARM: dts: stm32: Add Plymovent AQM devicetree")
> Signed-off-by: Jihed Chaibi <jihed.chaibi.dev@gmail.com>
> ---
>   arch/arm/boot/dts/st/stm32mp151c-plyaqm.dts | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arm/boot/dts/st/stm32mp151c-plyaqm.dts b/arch/arm/boot/dts/st/stm32mp151c-plyaqm.dts
> index 39a3211c613..55fe916740d 100644
> --- a/arch/arm/boot/dts/st/stm32mp151c-plyaqm.dts
> +++ b/arch/arm/boot/dts/st/stm32mp151c-plyaqm.dts
> @@ -239,7 +239,7 @@ &i2s1 {
>   
>   	i2s1_port: port {
>   		i2s1_endpoint: endpoint {
> -			format = "i2s";
> +			dai-format = "i2s";
>   			mclk-fs = <256>;
>   			remote-endpoint = <&codec_endpoint>;
>   		};

Applied on stm32-next.

Thanks
Alex

      reply	other threads:[~2025-09-03  7:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-30 22:51 Jihed Chaibi
2025-09-03  7:38 ` 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=667a4a36-5b5a-4a45-9300-d0abd10d4b53@foss.st.com \
    --to=alexandre.torgue@foss.st.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jihed.chaibi.dev@gmail.com \
    --cc=krzk+dt@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@kernel.org \
    --cc=shuah@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

all inboxes | Powered by JetHome®