From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: stefan.wahren@i2se.com, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com
Cc: mbrugger@suse.de, viresh.kumar@linaro.org, rjw@rjwysocki.net,
sboyd@kernel.org, eric@anholt.net, ptesarik@suse.com,
linux-rpi-kernel@lists.infradead.org,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC 4/5] dts: bcm2837: add per-cpu clock devices
Date: Fri, 17 May 2019 17:35:06 +0200 [thread overview]
Message-ID: <20190517153508.18314-5-nsaenzjulienne@suse.de> (raw)
In-Reply-To: <20190517153508.18314-1-nsaenzjulienne@suse.de>
The four CPUs share a same clock source called pllb_arm. The clock can
be scaled through the raspberrypi firmware interface.
Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
---
arch/arm/boot/dts/bcm2837.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/bcm2837.dtsi b/arch/arm/boot/dts/bcm2837.dtsi
index beb6c502dadc..a8fea6696b42 100644
--- a/arch/arm/boot/dts/bcm2837.dtsi
+++ b/arch/arm/boot/dts/bcm2837.dtsi
@@ -44,6 +44,8 @@
reg = <0>;
enable-method = "spin-table";
cpu-release-addr = <0x0 0x000000d8>;
+ clocks = <&clocks BCM2835_PLLB_ARM>;
+ clock-names = "pllb_arm";
};
cpu1: cpu@1 {
@@ -52,6 +54,8 @@
reg = <1>;
enable-method = "spin-table";
cpu-release-addr = <0x0 0x000000e0>;
+ clocks = <&clocks BCM2835_PLLB_ARM>;
+ clock-names = "pllb_arm";
};
cpu2: cpu@2 {
@@ -60,6 +64,8 @@
reg = <2>;
enable-method = "spin-table";
cpu-release-addr = <0x0 0x000000e8>;
+ clocks = <&clocks BCM2835_PLLB_ARM>;
+ clock-names = "pllb_arm";
};
cpu3: cpu@3 {
@@ -68,6 +74,8 @@
reg = <3>;
enable-method = "spin-table";
cpu-release-addr = <0x0 0x000000f0>;
+ clocks = <&clocks BCM2835_PLLB_ARM>;
+ clock-names = "pllb_arm";
};
};
};
--
2.21.0
next prev parent reply other threads:[~2019-05-17 15:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 15:35 [RFC 0/5] cpufreq support for the Raspberry Pi Nicolas Saenz Julienne
2019-05-17 15:35 ` [RFC 1/5] clk: bcm2835: set CLK_GET_RATE_NOCACHE on CPU clocks Nicolas Saenz Julienne
2019-05-17 15:35 ` [RFC 2/5] clk: bcm2835: set pllb_arm divisor as readonly Nicolas Saenz Julienne
2019-05-17 15:35 ` [RFC 3/5] clk: bcm2835: use firmware interface to update pllb Nicolas Saenz Julienne
2019-05-17 15:35 ` Nicolas Saenz Julienne [this message]
2019-05-17 15:35 ` [RFC 5/5] cpufreq: add driver for Raspbery Pi Nicolas Saenz Julienne
2019-05-20 4:39 ` Viresh Kumar
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=20190517153508.18314-5-nsaenzjulienne@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mbrugger@suse.de \
--cc=ptesarik@suse.com \
--cc=rjui@broadcom.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.com \
--cc=viresh.kumar@linaro.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).