From: mark.yao@rock-chips•com (Mark yao)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] arm64: dts: rk3399: init vop clock rates
Date: Wed, 16 Aug 2017 11:15:11 +0800 [thread overview]
Message-ID: <5993B8BF.9020100@rock-chips.com> (raw)
In-Reply-To: <1502851869-1736-1-git-send-email-kever.yang@rock-chips.com>
On 2017?08?16? 10:51, Kever Yang wrote:
> We need to init vop aclk and hclk incase the U-Boot does not do
> the initialize.
>
> Signed-off-by: Kever Yang <kever.yang@rock-chips•com>
> ---
Looks good for me:
Reviewed-by: Mark Yao <mark.yao@rock-chips•com>
> arch/arm64/boot/dts/rockchip/rk3399.dtsi | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> index 0b3acc9..a592c24 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> @@ -1480,6 +1480,8 @@
> interrupts = <GIC_SPI 119 IRQ_TYPE_LEVEL_HIGH 0>;
> clocks = <&cru ACLK_VOP1>, <&cru DCLK_VOP1>, <&cru HCLK_VOP1>;
> clock-names = "aclk_vop", "dclk_vop", "hclk_vop";
> + assigned-clocks = <&cru ACLK_VOP1>, <&cru HCLK_VOP1>;
> + assigned-clock-rates = <400000000>, <100000000>;
> iommus = <&vopl_mmu>;
> power-domains = <&power RK3399_PD_VOPL>;
> resets = <&cru SRST_A_VOP1>, <&cru SRST_H_VOP1>, <&cru SRST_D_VOP1>;
> @@ -1525,6 +1527,8 @@
> interrupts = <GIC_SPI 118 IRQ_TYPE_LEVEL_HIGH 0>;
> clocks = <&cru ACLK_VOP0>, <&cru DCLK_VOP0>, <&cru HCLK_VOP0>;
> clock-names = "aclk_vop", "dclk_vop", "hclk_vop";
> + assigned-clocks = <&cru ACLK_VOP0>, <&cru HCLK_VOP0>;
> + assigned-clock-rates = <400000000>, <100000000>;
> iommus = <&vopb_mmu>;
> power-domains = <&power RK3399_PD_VOPB>;
> resets = <&cru SRST_A_VOP0>, <&cru SRST_H_VOP0>, <&cru SRST_D_VOP0>;
--
?ark Yao
next prev parent reply other threads:[~2017-08-16 3:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 2:51 [PATCH] arm64: dts: rk3399: init vop clock rates Kever Yang
2017-08-16 3:15 ` Mark yao [this message]
2017-08-18 23:13 ` Heiko Stuebner
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=5993B8BF.9020100@rock-chips.com \
--to=mark.yao@rock-chips$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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