Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1400978 > unrolled thread
| Started by | Brian Norris <briannorris@chromium.org> |
|---|---|
| First post | 2016-05-13 23:00 +0200 |
| Last post | 2016-05-14 14:00 +0200 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.kernel
[PATCH] ARM64: dts: rockchip: assign default rates for core rk3399 clocks Brian Norris <briannorris@chromium.org> - 2016-05-13 23:00 +0200
Re: [PATCH] ARM64: dts: rockchip: assign default rates for core rk3399 clocks Doug Anderson <dianders@chromium.org> - 2016-05-13 23:30 +0200
Re: [PATCH] ARM64: dts: rockchip: assign default rates for core rk3399 clocks Heiko Stuebner <heiko@sntech.de> - 2016-05-14 14:00 +0200
| From | Brian Norris <briannorris@chromium.org> |
|---|---|
| Date | 2016-05-13 23:00 +0200 |
| Subject | [PATCH] ARM64: dts: rockchip: assign default rates for core rk3399 clocks |
| Message-ID | <ryslI-2vK-15@gated-at.bofh.it> |
From: Xing Zheng <zhengxing@rock-chips.com>
These clocks are all core clocks used by many blocks/peripherals, many
of whose drivers don't set their clock rates at all. Let's assign
reasonable default clock rates for these core clocks, so that these
peripherals get something reasonable by default, and also so that if
child devices want to select a clock rate themselves, their muxes have
some reasonable parent clock rates to branch off of (rather than just
the boot-time defaults).
This helps the eMMC PHY, for one, to get a reasonable ACLK rate.
Signed-off-by: Xing Zheng <zhengxing@rock-chips.com>
Signed-off-by: Brian Norris <briannorris@chromium.org>
---
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
index 46f325a143b0..6fa9cc332482 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
@@ -478,6 +478,22 @@
reg = <0x0 0xff760000 0x0 0x1000>;
#clock-cells = <1>;
#reset-cells = <1>;
+ assigned-clocks =
+ <&cru PLL_GPLL>, <&cru PLL_CPLL>,
+ <&cru PLL_NPLL>,
+ <&cru ACLK_PERIHP>, <&cru HCLK_PERIHP>,
+ <&cru PCLK_PERIHP>,
+ <&cru ACLK_PERILP0>, <&cru HCLK_PERILP0>,
+ <&cru PCLK_PERILP0>,
+ <&cru HCLK_PERILP1>, <&cru PCLK_PERILP1>;
+ assigned-clock-rates =
+ <594000000>, <800000000>,
+ <1000000000>,
+ <150000000>, <75000000>,
+ <37500000>,
+ <100000000>, <100000000>,
+ <50000000>,
+ <100000000>, <50000000>;
};
grf: syscon@ff770000 {
--
2.8.0.rc3.226.g39d4020
[toc] | [next] | [standalone]
| From | Doug Anderson <dianders@chromium.org> |
|---|---|
| Date | 2016-05-13 23:30 +0200 |
| Subject | Re: [PATCH] ARM64: dts: rockchip: assign default rates for core rk3399 clocks |
| Message-ID | <rysOL-35p-15@gated-at.bofh.it> |
| In reply to | #1400978 |
Hi, On Fri, May 13, 2016 at 1:50 PM, Brian Norris <briannorris@chromium.org> wrote: > From: Xing Zheng <zhengxing@rock-chips.com> > > These clocks are all core clocks used by many blocks/peripherals, many > of whose drivers don't set their clock rates at all. Let's assign > reasonable default clock rates for these core clocks, so that these > peripherals get something reasonable by default, and also so that if > child devices want to select a clock rate themselves, their muxes have > some reasonable parent clock rates to branch off of (rather than just > the boot-time defaults). > > This helps the eMMC PHY, for one, to get a reasonable ACLK rate. > > Signed-off-by: Xing Zheng <zhengxing@rock-chips.com> > Signed-off-by: Brian Norris <briannorris@chromium.org> > --- > arch/arm64/boot/dts/rockchip/rk3399.dtsi | 16 ++++++++++++++++ > 1 file changed, 16 insertions(+) > > diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi > index 46f325a143b0..6fa9cc332482 100644 > --- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi > +++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi > @@ -478,6 +478,22 @@ > reg = <0x0 0xff760000 0x0 0x1000>; > #clock-cells = <1>; > #reset-cells = <1>; > + assigned-clocks = > + <&cru PLL_GPLL>, <&cru PLL_CPLL>, > + <&cru PLL_NPLL>, > + <&cru ACLK_PERIHP>, <&cru HCLK_PERIHP>, > + <&cru PCLK_PERIHP>, > + <&cru ACLK_PERILP0>, <&cru HCLK_PERILP0>, > + <&cru PCLK_PERILP0>, > + <&cru HCLK_PERILP1>, <&cru PCLK_PERILP1>; > + assigned-clock-rates = > + <594000000>, <800000000>, > + <1000000000>, > + <150000000>, <75000000>, > + <37500000>, > + <100000000>, <100000000>, > + <50000000>, > + <100000000>, <50000000>; I agree that * this is sane information to have in this node (like in rk3288) * the rates look sane (similar to rk3288 but two are double) * these rates match what I see in Rockchip's kernel So: Reviewed-by: Douglas Anderson <dianders@chromium.org>
[toc] | [prev] | [next] | [standalone]
| From | Heiko Stuebner <heiko@sntech.de> |
|---|---|
| Date | 2016-05-14 14:00 +0200 |
| Message-ID | <ryGoG-8o7-7@gated-at.bofh.it> |
| In reply to | #1400978 |
Am Freitag, 13. Mai 2016, 13:50:18 schrieb Brian Norris: > From: Xing Zheng <zhengxing@rock-chips.com> > > These clocks are all core clocks used by many blocks/peripherals, many > of whose drivers don't set their clock rates at all. Let's assign > reasonable default clock rates for these core clocks, so that these > peripherals get something reasonable by default, and also so that if > child devices want to select a clock rate themselves, their muxes have > some reasonable parent clock rates to branch off of (rather than just > the boot-time defaults). > > This helps the eMMC PHY, for one, to get a reasonable ACLK rate. > > Signed-off-by: Xing Zheng <zhengxing@rock-chips.com> > Signed-off-by: Brian Norris <briannorris@chromium.org> applied for 4.8 with Doug's review-tag (after making the ARM64 lower-case)
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web