devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Simon Horman <horms@verge.net.au>, Magnus Damm <magnus.damm@gmail.com>
Cc: linux-renesas-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [PATCH v4 6/9] ARM: dts: marzen: Enable SCIF_CLK frequency and pins
Date: Fri, 29 Jan 2016 11:17:23 +0100	[thread overview]
Message-ID: <1454062646-4826-7-git-send-email-geert+renesas@glider.be> (raw)
In-Reply-To: <1454062646-4826-1-git-send-email-geert+renesas@glider.be>

Add and enable the external crystal for the SCIF_CLK and its pinctrl, to
be used by the Baud Rate Generator for External Clock (BRG) on (H)SCIF.

This increases the range and accuracy of supported baud rates.

Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
Based on schematics, tested with remote access.

v4:
  - Change one-line summary prefix to match current arm-soc practices,

v3:
  - New.
---
 arch/arm/boot/dts/r8a7779-marzen.dts | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/arch/arm/boot/dts/r8a7779-marzen.dts b/arch/arm/boot/dts/r8a7779-marzen.dts
index fe396c8d58db7986..e111d35d02aebe19 100644
--- a/arch/arm/boot/dts/r8a7779-marzen.dts
+++ b/arch/arm/boot/dts/r8a7779-marzen.dts
@@ -165,6 +165,9 @@
 };
 
 &pfc {
+	pinctrl-0 = <&scif_clk_pins>;
+	pinctrl-names = "default";
+
 	du_pins: du {
 		du0 {
 			renesas,groups = "du0_rgb888", "du0_sync_1", "du0_clk_out_0";
@@ -176,6 +179,11 @@
 		};
 	};
 
+	scif_clk_pins: scif_clk {
+		renesas,groups = "scif_clk_b";
+		renesas,function = "scif_clk";
+	};
+
 	ethernet_pins: ethernet {
 		intc {
 			renesas,groups = "intc_irq1_b";
@@ -222,6 +230,11 @@
 	status = "okay";
 };
 
+&scif_clk {
+	clock-frequency = <14745600>;
+	status = "okay";
+};
+
 &sdhi0 {
 	pinctrl-0 = <&sdhi0_pins>;
 	pinctrl-names = "default";
-- 
1.9.1

  parent reply	other threads:[~2016-01-29 10:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29 10:17 [PATCH v4 0/9] ARM/arm64: dts: rcar: Enable SCIF_CLK frequency and pins Geert Uytterhoeven
2016-01-29 10:17 ` [PATCH v4 1/9] ARM: dts: alt: " Geert Uytterhoeven
2016-01-29 10:17 ` [PATCH v4 2/9] ARM: dts: bockw: " Geert Uytterhoeven
2016-01-29 10:17 ` [PATCH v4 3/9] ARM: dts: gose: " Geert Uytterhoeven
2016-01-29 10:17 ` [PATCH v4 4/9] ARM: dts: koelsch: " Geert Uytterhoeven
     [not found] ` <1454062646-4826-1-git-send-email-geert+renesas-gXvu3+zWzMSzQB+pC5nmwQ@public.gmane.org>
2016-01-29 10:17   ` [PATCH v4 5/9] ARM: dts: lager: " Geert Uytterhoeven
2016-01-29 10:17   ` [PATCH v4 9/9] arm64: dts: salvator-x: " Geert Uytterhoeven
2016-01-29 10:17 ` Geert Uytterhoeven [this message]
2016-01-29 10:17 ` [PATCH v4 7/9] ARM: dts: porter: " Geert Uytterhoeven
2016-01-29 10:17 ` [PATCH v4 8/9] ARM: dts: silk: " Geert Uytterhoeven
2016-02-02 10:21 ` [PATCH v4 0/9] ARM/arm64: dts: rcar: " Simon Horman
2016-02-02 13:16   ` 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=1454062646-4826-7-git-send-email-geert+renesas@glider.be \
    --to=geert+renesas@glider.be \
    --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=magnus.damm@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 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).