All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>
To: tomm.merciai@gmail.com, prabhakar.mahadev-lad.rj@bp.renesas.com
Cc: linux-renesas-soc@vger.kernel.org, biju.das.jz@bp.renesas.com,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	John Madieu <john.madieu.xa@bp.renesas.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] arm64: dts: renesas: r9a09g047e57-smarc: Drop AUDIO_CLKOUT clock-frequency
Date: Fri, 23 Oct 2026 08:44:15 +0200	[thread overview]
Message-ID: <atsCP4pHneYvN3KB@tom-desktop> (raw)
In-Reply-To: <e2473162dc19edba539d8566c28ada810f36e73c.1792493096.git.tommaso.merciai.xr@bp.renesas.com>

Hi,

On Tue, Oct 20, 2026 at 01:11:07PM +0200, Tommaso Merciai wrote:
> AUDIO_CLKOUT is neither pinmuxed nor consumed on this board,
> clock-frequency describe the frequency of an output that does not
> exist here. The DA7212 MCLK comes from the on-board versa3 clock
> generator.
> 
> Drop the clock-frequency entry from the snd_rzg3e node.
> 
> This fix also the following dtbs_check warning:
> 
> sound@13c00000 (renesas,r9a09g047-sound): Unevaluated properties are not allowed ('clock-frequency' was unexpected)
> 	from schema $id: http://devicetree.org/schemas/sound/renesas,r9a09g047-sound.yaml#
> 
> Fixes: 3e23d2548ddb ("arm64: dts: renesas: r9a09g047e57-smarc: Add DA7212 audio codec support")
> Signed-off-by: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>

8KHz arecord is failing with this change and currently investigating the issue.
Will update you the findings later.


Kind regards,
Tommaso

> ---
> v1->v2:
>  - New patch.
> 
>  arch/arm64/boot/dts/renesas/r9a09g047e57-smarc.dts | 3 ---
>  1 file changed, 3 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/renesas/r9a09g047e57-smarc.dts b/arch/arm64/boot/dts/renesas/r9a09g047e57-smarc.dts
> index d242f2976296..6c0053735904 100644
> --- a/arch/arm64/boot/dts/renesas/r9a09g047e57-smarc.dts
> +++ b/arch/arm64/boot/dts/renesas/r9a09g047e57-smarc.dts
> @@ -378,9 +378,6 @@ &snd_rzg3e {
>  
>  	status = "okay";
>  
> -	/* audio_clkout */
> -	clock-frequency = <11289600>;
> -
>  	/* Multi DAI */
>  	#sound-dai-cells = <1>;
>  
> -- 
> 2.54.0
> 

      reply	other threads:[~2026-10-23  6:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 11:11 [PATCH v2 0/2] Drop clock-frequency from RZ/G3E SMARC snd_rzg3e dts node Tommaso Merciai
2026-10-20 11:11 ` [PATCH v2 1/2] arm64: dts: renesas: r9a09g047: Move #clock-cells to the RZ/G3E SoC dtsi Tommaso Merciai
2026-10-20 11:11 ` [PATCH v2 2/2] arm64: dts: renesas: r9a09g047e57-smarc: Drop AUDIO_CLKOUT clock-frequency Tommaso Merciai
2026-10-23  6:44   ` Tommaso Merciai [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=atsCP4pHneYvN3KB@tom-desktop \
    --to=tommaso.merciai.xr@bp.renesas.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=john.madieu.xa@bp.renesas.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=robh@kernel.org \
    --cc=tomm.merciai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.