From: Eric Anholt <eric@anholt.net>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-rpi-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>,
linux-clk@vger.kernel.org, Stephen Boyd <sboyd@codeaurora.org>,
Mike Turquette <mturquette@linaro.org>,
Eric Anholt <eric@anholt.net>
Subject: [PATCH v3 6/7] ARM: bcm2835: Use the RPi firmware clocks for uart.
Date: Mon, 8 Jun 2015 16:58:59 -0700 [thread overview]
Message-ID: <1433807940-15328-6-git-send-email-eric@anholt.net> (raw)
In-Reply-To: <1433807940-15328-1-git-send-email-eric@anholt.net>
This gets us a correct apb_pclk, which previously was accidentally
using the "20201000.uart" clock from clk-bcm2835.c, due to the
fallback clk_get_sys() path.
Signed-off-by: Eric Anholt <eric@anholt.net>
---
arch/arm/boot/dts/bcm2835-rpi.dtsi | 7 +++++++
arch/arm/boot/dts/bcm2835.dtsi | 2 +-
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/bcm2835-rpi.dtsi b/arch/arm/boot/dts/bcm2835-rpi.dtsi
index 7cc47fb..9549eb8 100644
--- a/arch/arm/boot/dts/bcm2835-rpi.dtsi
+++ b/arch/arm/boot/dts/bcm2835-rpi.dtsi
@@ -1,3 +1,4 @@
+#include <dt-bindings/clk/raspberrypi.h>
#include "bcm2835.dtsi"
/ {
@@ -62,3 +63,9 @@
status = "okay";
bus-width = <4>;
};
+
+&uart0 {
+ clocks = <&firmware_clocks RPI_CLOCK_UART0>,
+ <&firmware_clocks RPI_CLOCK_CORE>;
+ clock-names = "uartclk", "apb_pclk";
+};
diff --git a/arch/arm/boot/dts/bcm2835.dtsi b/arch/arm/boot/dts/bcm2835.dtsi
index 32f5830..5be2862 100644
--- a/arch/arm/boot/dts/bcm2835.dtsi
+++ b/arch/arm/boot/dts/bcm2835.dtsi
@@ -92,7 +92,7 @@
#interrupt-cells = <2>;
};
- uart@7e201000 {
+ uart0: uart@7e201000 {
compatible = "brcm,bcm2835-pl011", "arm,pl011", "arm,primecell";
reg = <0x7e201000 0x1000>;
interrupts = <2 25>;
--
2.1.4
next prev parent reply other threads:[~2015-06-08 23:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 23:58 [PATCH v3 1/7] dt/bindings: Add binding for the Raspberry Pi clock provider Eric Anholt
2015-06-08 23:58 ` [PATCH v3 2/7] ARM: bcm2835: Add a Raspberry Pi-specific clock driver Eric Anholt
2015-06-09 1:56 ` Stephen Warren
2015-06-09 9:56 ` Lee Jones
2015-06-08 23:58 ` [PATCH v3 3/7] ARM: bcm2835: Add DT for the firmware clocks driver Eric Anholt
2015-06-08 23:58 ` [PATCH v3 4/7] ARM: bcm2835: Drop never-used clock-frequency property of uart0 Eric Anholt
2015-06-08 23:58 ` [PATCH v3 5/7] ARM: bcm2835: Drop the fixed sys_pclk Eric Anholt
2015-06-08 23:58 ` Eric Anholt [this message]
2015-06-08 23:59 ` [PATCH v3 7/7] ARM: bcm2835: Tie SPI clock to the core clock rate Eric Anholt
2015-06-09 0:03 ` [PATCH v3 1/7] dt/bindings: Add binding for the Raspberry Pi clock provider Eric Anholt
2015-06-09 10:03 ` Lee Jones
2015-07-07 20:13 ` Eric Anholt
2015-07-24 15:30 ` Lee Jones
2015-07-28 2:53 ` Stephen Warren
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=1433807940-15328-6-git-send-email-eric@anholt.net \
--to=eric@anholt.net \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mturquette@linaro.org \
--cc=sboyd@codeaurora.org \
--cc=swarren@wwwdotorg.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).