linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Biju Das <biju.das.jz@bp.renesas.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Biju Das <biju.das.jz@bp.renesas.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
	Chris Paterson <Chris.Paterson2@renesas.com>,
	Biju Das <biju.das@bp.renesas.com>,
	Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: [PATCH 4/9] arm64: dts: renesas: r9a07g044: Add external audio clock nodes
Date: Fri,  2 Jul 2021 14:50:05 +0100	[thread overview]
Message-ID: <20210702135010.5937-5-biju.das.jz@bp.renesas.com> (raw)
In-Reply-To: <20210702135010.5937-1-biju.das.jz@bp.renesas.com>

Add external audio clocks nodes to RZ/G2L (a.k.a R9A07G044) SoC DTSI.

The external audio clocks are configured as 0 Hz fixed frequency clocks by
default. Boards that provide audio clocks should override them.

Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
Reviewed-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
---
 arch/arm64/boot/dts/renesas/r9a07g044.dtsi | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/arch/arm64/boot/dts/renesas/r9a07g044.dtsi b/arch/arm64/boot/dts/renesas/r9a07g044.dtsi
index 9f3e5ebd03f5..932eaed81f5d 100644
--- a/arch/arm64/boot/dts/renesas/r9a07g044.dtsi
+++ b/arch/arm64/boot/dts/renesas/r9a07g044.dtsi
@@ -13,6 +13,20 @@
 	#address-cells = <2>;
 	#size-cells = <2>;
 
+	audio_clk1: audio_clk1 {
+		compatible = "fixed-clock";
+		#clock-cells = <0>;
+		/* This value must be overridden by the board */
+		clock-frequency = <0>;
+	};
+
+	audio_clk2: audio_clk2 {
+		compatible = "fixed-clock";
+		#clock-cells = <0>;
+		/* This value must be overridden by the board */
+		clock-frequency = <0>;
+	};
+
 	/* clock can be either from exclk or crystal oscillator (XIN/XOUT) */
 	extal_clk: extal {
 		compatible = "fixed-clock";
-- 
2.17.1


  parent reply	other threads:[~2021-07-02 13:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02 13:50 [PATCH 0/9] Add RZ/G2L Sound support Biju Das
2021-07-02 13:50 ` [PATCH 1/9] ASoC: dt-bindings: Document RZ/G2L bindings Biju Das
2021-07-02 21:23   ` Rob Herring
2021-07-19 13:43     ` Biju Das
2021-07-02 13:50 ` [PATCH 2/9] drivers: clk: renesas: r9a07g044-cpg: Add SSIF-2 clock and reset entries Biju Das
2021-07-02 14:03   ` Geert Uytterhoeven
2021-07-02 13:50 ` [PATCH 3/9] sound: soc: sh: Add RZ/G2L SSIF-2 driver Biju Das
2021-07-02 13:50 ` Biju Das [this message]
2021-07-02 13:50 ` [PATCH 5/9] arm64: dts: renesas: r9a07g044: Add SSI support Biju Das
2021-07-02 13:50 ` [PATCH 6/9] arm64: defconfig: Enable ASoC sound support for RZ/G2L SoC Biju Das
2021-07-02 13:50 ` [PATCH 7/9] ASoC: dt-bindings: sound: renesas,rz-ssi: Document DMA support Biju Das
2021-07-02 13:50 ` [PATCH 8/9] sound: sh: rz-ssi: Add SSI DMAC support Biju Das
2021-07-02 13:50 ` [PATCH 9/9] arm64: dts: renesas: r9a07g044: Add SSI DMA support Biju Das

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=20210702135010.5937-5-biju.das.jz@bp.renesas.com \
    --to=biju.das.jz@bp.renesas.com \
    --cc=Chris.Paterson2@renesas.com \
    --cc=biju.das@bp.renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.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).