From: Daniel Palmer <daniel@0x0f.com>
To: devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
soc@kernel.org, sboyd@kernel.org
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, w@1wt.eu,
Daniel Palmer <daniel@0x0f.com>
Subject: [PATCH 5/8] ARM: mstar: Link cpupll to second core
Date: Tue, 23 Feb 2021 15:18:27 +0900 [thread overview]
Message-ID: <20210223061830.1913700-6-daniel@0x0f.com> (raw)
In-Reply-To: <20210223061830.1913700-1-daniel@0x0f.com>
The second core also sources it's clock from the CPU PLL.
Signed-off-by: Daniel Palmer <daniel@0x0f.com>
---
arch/arm/boot/dts/mstar-infinity2m.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/mstar-infinity2m.dtsi b/arch/arm/boot/dts/mstar-infinity2m.dtsi
index 6d4d1d224e96..dc339cd29778 100644
--- a/arch/arm/boot/dts/mstar-infinity2m.dtsi
+++ b/arch/arm/boot/dts/mstar-infinity2m.dtsi
@@ -11,6 +11,8 @@ cpu1: cpu@1 {
device_type = "cpu";
compatible = "arm,cortex-a7";
reg = <0x1>;
+ clocks = <&cpupll>;
+ clock-names = "cpuclk";
};
};
--
2.30.0.rc2
next prev parent reply other threads:[~2021-02-23 6:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 6:18 [PATCH 0/8] ARM: mstar: cpupll Daniel Palmer
2021-02-23 6:18 ` [PATCH 1/8] dt-bindings: clk: mstar msc313 cpupll binding description Daniel Palmer
2021-02-23 19:34 ` Rob Herring
2021-02-26 11:31 ` Daniel Palmer
2021-04-01 11:03 ` Arnd Bergmann
2021-04-01 11:07 ` Daniel Palmer
2021-02-23 6:18 ` [PATCH 2/8] clk: mstar: msc313 cpupll clk driver Daniel Palmer
2021-02-23 6:18 ` [PATCH 3/8] ARM: mstar: Add cpupll to base dtsi Daniel Palmer
2021-02-23 6:18 ` [PATCH 4/8] ARM: mstar: Link cpupll to cpu Daniel Palmer
2021-02-23 6:18 ` Daniel Palmer [this message]
2021-02-23 6:18 ` [PATCH 6/8] ARM: mstar: Add OPP table for infinity Daniel Palmer
2021-02-23 6:18 ` [PATCH 7/8] ARM: mstar: Add OPP table for infinity3 Daniel Palmer
2021-02-23 6:18 ` [PATCH 8/8] ARM: mstar: Add OPP table for mercury5 Daniel Palmer
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=20210223061830.1913700-6-daniel@0x0f.com \
--to=daniel@0x0f.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=soc@kernel.org \
--cc=w@1wt.eu \
/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).