Linux Renesas SOC kernel development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: horms@verge.net.au, linux-renesas-soc@vger.kernel.org,
	robh+dt@kernel.org, mark.rutland@arm.com,
	devicetree@vger.kernel.org
Cc: magnus.damm@gmail.com, linux@arm.linux.org.uk,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/6] ARM: dts: r8a7794: add audio clocks
Date: Wed, 27 Jul 2016 23:59:18 +0300	[thread overview]
Message-ID: <4789280.VAzvua9Bym@wasted.cogentembedded.com> (raw)
In-Reply-To: <3910788.ckTpUWEs6B@wasted.cogentembedded.com>

Describe  the external audio clocks (signals AUDIO_CLK[ABC]) required by
the sound driver.  Boards that provide audio clocks need to  override the
clock frequencies.

This patch is based on the commit 0d3dbde84a45 ("ARM: shmobile: r8a7791:
add  audio clock on DTSI").

Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>

---
Changes in version 4:
- refreshed the patch.

Changes in version 3:
- removed now redundant "clock-output-names" properties;
- reformatted the changelog;
- refreshed the patch.

 arch/arm/boot/dts/r8a7794.dtsi |   21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

Index: renesas/arch/arm/boot/dts/r8a7794.dtsi
===================================================================
--- renesas.orig/arch/arm/boot/dts/r8a7794.dtsi
+++ renesas/arch/arm/boot/dts/r8a7794.dtsi
@@ -952,6 +952,27 @@
 			clock-frequency = <0>;
 		};
 
+		/*
+		 * The external audio clocks are configured  as 0 Hz fixed
+		 * frequency clocks by default.  Boards that provide audio
+		 * clocks should override them.
+		 */
+		audio_clka: audio_clka {
+			compatible = "fixed-clock";
+			#clock-cells = <0>;
+			clock-frequency = <0>;
+		};
+		audio_clkb: audio_clkb {
+			compatible = "fixed-clock";
+			#clock-cells = <0>;
+			clock-frequency = <0>;
+		};
+		audio_clkc: audio_clkc {
+			compatible = "fixed-clock";
+			#clock-cells = <0>;
+			clock-frequency = <0>;
+		};
+
 		/* Special CPG clocks */
 		cpg_clocks: cpg_clocks@e6150000 {
 			compatible = "renesas,r8a7794-cpg-clocks",

  reply	other threads:[~2016-07-27 20:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27 20:55 [PATCH v3 0/6] Add R8A7794/SILK sound DT support Sergei Shtylyov
2016-07-27 20:59 ` Sergei Shtylyov [this message]
2016-07-27 20:59 ` [PATCH v4 2/6] ARM: dts: r8a7794: add MSTP5 clocks Sergei Shtylyov
2016-08-08 13:03   ` Geert Uytterhoeven
2016-07-27 21:01 ` [PATCH v4 3/6] ARM: dts: r8a7794: add MSTP10 clocks Sergei Shtylyov
2016-08-08 13:10   ` Geert Uytterhoeven
2016-07-27 21:02 ` [PATCH v4 4/6] ARM: dts: r8a7794: add Audio-DMAC support Sergei Shtylyov
2016-08-08 13:14   ` Geert Uytterhoeven
2016-08-08 13:15     ` Geert Uytterhoeven
2016-07-27 21:03 ` [PATCH v4 5/6] ARM: dts: r8a7794: add sound support Sergei Shtylyov
2016-07-27 21:05 ` [PATCH v4 6/6] ARM: dts: silk: " Sergei Shtylyov
2016-07-28 23:47 ` [PATCH v3 0/6] Add R8A7794/SILK sound DT support Kuninori Morimoto
2016-08-08 10:59   ` Simon Horman
2016-08-08 18:54     ` Sergei Shtylyov
2016-08-09 12:38       ` Simon Horman

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=4789280.VAzvua9Bym@wasted.cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=devicetree@vger.kernel.org \
    --cc=horms@verge.net.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=magnus.damm@gmail.com \
    --cc=mark.rutland@arm.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