From: Doug Anderson <dianders@chromium.org> To: Yakir Yang <ykk@rock-chips.com> Cc: Heiko Stuebner <heiko@sntech.de>, Kumar Gala <galak@codeaurora.org>, Rob Herring <robh+dt@kernel.org>, Olof Johansson <olof@lixom.net>, Ian Campbell <ijc+devicetree@hellion.org.uk>, "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "open list:ARM/Rockchip SoC..." <linux-rockchip@lists.infradead.org>, "linux-arm-kernel@lists.infradead.org" <linux-arm-kernel@lists.infradead.org>, Mark Yao <mark.yao@rock-chips.com>, Caesar Wang <wxt@rock-chips.com> Subject: Re: [PATCH v3 1/4] arm64: dts: rockchip: add VOP and VOP iommu node for rk3399 Date: Thu, 30 Jun 2016 10:45:21 -0700 [thread overview] Message-ID: <CAD=FV=URVQTvEKQbUVOXyMnO1a-kGs9inX_AZY3vo_YxXD5-5w@mail.gmail.com> (raw) In-Reply-To: <1466564069-18220-1-git-send-email-ykk@rock-chips.com> Hi On Tue, Jun 21, 2016 at 7:54 PM, Yakir Yang <ykk@rock-chips.com> wrote: > From: Mark Yao <mark.yao@rock-chips.com> > > Add the core display-subsystem node and the two display controllers > available on the rk3399. > > Signed-off-by: Mark Yao <mark.yao@rock-chips.com> > Signed-off-by: Yakir Yang <ykk@rock-chips.com> > --- > Changes in v3: None > Changes in v2: > - provide some minimal patch description (Heiko) > > arch/arm64/boot/dts/rockchip/rk3399.dtsi | 58 ++++++++++++++++++++++++++++++++ > 1 file changed, 58 insertions(+) > > diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi > index 46f325a..54e5c25 100644 > --- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi > +++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi > @@ -543,6 +543,64 @@ > status = "disabled"; > }; > > + vopl: vop@ff8f0000 { > + compatible = "rockchip,rk3399-vop-lit"; > + reg = <0x0 0xff8f0000 0x0 0x3efc>; > + interrupts = <GIC_SPI 119 IRQ_TYPE_LEVEL_HIGH>; > + clocks = <&cru ACLK_VOP1>, <&cru DCLK_VOP1>, <&cru HCLK_VOP1>; > + clock-names = "aclk_vop", "dclk_vop", "hclk_vop"; Note that if this lands after Elaine / Caesar's patch ("arm64: dts: rockchip: add the power domain node for rk3399") <https://patchwork.kernel.org/patch/9206415/> then you need to respin adding powerdomain references here for correctness. If this lands before Elaine / Caesar's patch then the other patch needs to be re-spun. ;) > + resets = <&cru SRST_A_VOP1>, <&cru SRST_H_VOP1>, <&cru SRST_D_VOP1>; > + reset-names = "axi", "ahb", "dclk"; > + iommus = <&vopl_mmu>; > + status = "disabled"; > + > + vopl_out: port { > + #address-cells = <1>; > + #size-cells = <0>; > + }; > + }; > + > + vopl_mmu: iommu@ff8f3f00 { > + compatible = "rockchip,iommu"; > + reg = <0x0 0xff8f3f00 0x0 0x100>; > + interrupts = <GIC_SPI 119 IRQ_TYPE_LEVEL_HIGH>; > + interrupt-names = "vopl_mmu"; > + #iommu-cells = <0>; > + status = "disabled"; > + }; > + > + vopb: vop@ff900000 { > + compatible = "rockchip,rk3399-vop-big"; > + reg = <0x0 0xff900000 0x0 0x3efc>; > + interrupts = <GIC_SPI 118 IRQ_TYPE_LEVEL_HIGH>; > + clocks = <&cru ACLK_VOP0>, <&cru DCLK_VOP0>, <&cru HCLK_VOP0>; > + clock-names = "aclk_vop", "dclk_vop", "hclk_vop"; Here too, obviously. See <http://crosreview.com/356623> for reference. -Doug
WARNING: multiple messages have this Message-ID (diff)
From: dianders@chromium.org (Doug Anderson) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v3 1/4] arm64: dts: rockchip: add VOP and VOP iommu node for rk3399 Date: Thu, 30 Jun 2016 10:45:21 -0700 [thread overview] Message-ID: <CAD=FV=URVQTvEKQbUVOXyMnO1a-kGs9inX_AZY3vo_YxXD5-5w@mail.gmail.com> (raw) In-Reply-To: <1466564069-18220-1-git-send-email-ykk@rock-chips.com> Hi On Tue, Jun 21, 2016 at 7:54 PM, Yakir Yang <ykk@rock-chips.com> wrote: > From: Mark Yao <mark.yao@rock-chips.com> > > Add the core display-subsystem node and the two display controllers > available on the rk3399. > > Signed-off-by: Mark Yao <mark.yao@rock-chips.com> > Signed-off-by: Yakir Yang <ykk@rock-chips.com> > --- > Changes in v3: None > Changes in v2: > - provide some minimal patch description (Heiko) > > arch/arm64/boot/dts/rockchip/rk3399.dtsi | 58 ++++++++++++++++++++++++++++++++ > 1 file changed, 58 insertions(+) > > diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi > index 46f325a..54e5c25 100644 > --- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi > +++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi > @@ -543,6 +543,64 @@ > status = "disabled"; > }; > > + vopl: vop at ff8f0000 { > + compatible = "rockchip,rk3399-vop-lit"; > + reg = <0x0 0xff8f0000 0x0 0x3efc>; > + interrupts = <GIC_SPI 119 IRQ_TYPE_LEVEL_HIGH>; > + clocks = <&cru ACLK_VOP1>, <&cru DCLK_VOP1>, <&cru HCLK_VOP1>; > + clock-names = "aclk_vop", "dclk_vop", "hclk_vop"; Note that if this lands after Elaine / Caesar's patch ("arm64: dts: rockchip: add the power domain node for rk3399") <https://patchwork.kernel.org/patch/9206415/> then you need to respin adding powerdomain references here for correctness. If this lands before Elaine / Caesar's patch then the other patch needs to be re-spun. ;) > + resets = <&cru SRST_A_VOP1>, <&cru SRST_H_VOP1>, <&cru SRST_D_VOP1>; > + reset-names = "axi", "ahb", "dclk"; > + iommus = <&vopl_mmu>; > + status = "disabled"; > + > + vopl_out: port { > + #address-cells = <1>; > + #size-cells = <0>; > + }; > + }; > + > + vopl_mmu: iommu at ff8f3f00 { > + compatible = "rockchip,iommu"; > + reg = <0x0 0xff8f3f00 0x0 0x100>; > + interrupts = <GIC_SPI 119 IRQ_TYPE_LEVEL_HIGH>; > + interrupt-names = "vopl_mmu"; > + #iommu-cells = <0>; > + status = "disabled"; > + }; > + > + vopb: vop at ff900000 { > + compatible = "rockchip,rk3399-vop-big"; > + reg = <0x0 0xff900000 0x0 0x3efc>; > + interrupts = <GIC_SPI 118 IRQ_TYPE_LEVEL_HIGH>; > + clocks = <&cru ACLK_VOP0>, <&cru DCLK_VOP0>, <&cru HCLK_VOP0>; > + clock-names = "aclk_vop", "dclk_vop", "hclk_vop"; Here too, obviously. See <http://crosreview.com/356623> for reference. -Doug
next prev parent reply other threads:[~2016-06-30 17:45 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-06-22 2:53 [PATCH v3 0/4] Add the eDP/VOP device node for rk3399 Yakir Yang 2016-06-22 2:53 ` Yakir Yang 2016-06-22 2:53 ` Yakir Yang 2016-06-22 2:54 ` [PATCH v3 1/4] arm64: dts: rockchip: add VOP and VOP iommu " Yakir Yang 2016-06-22 2:54 ` Yakir Yang 2016-06-22 2:54 ` Yakir Yang 2016-06-30 17:45 ` Doug Anderson [this message] 2016-06-30 17:45 ` Doug Anderson 2016-06-30 17:45 ` Doug Anderson 2016-06-30 17:52 ` Heiko Stuebner 2016-06-30 17:52 ` Heiko Stuebner 2016-06-30 17:52 ` Heiko Stuebner 2016-06-22 2:54 ` [PATCH v3 2/4] arm64: dts: rockchip: add eDP device " Yakir Yang 2016-06-22 2:54 ` Yakir Yang 2016-06-22 2:54 ` Yakir Yang 2016-06-22 2:54 ` [PATCH v3 3/4] arm64: dts: rockchip: add backlight support for rk3399 evb board Yakir Yang 2016-06-22 2:54 ` Yakir Yang 2016-06-22 2:54 ` Yakir Yang 2016-06-22 2:54 ` [PATCH v3 4/4] arm64: dtsi: rockchip: introduce pclk_vio_grf in eDP device node Yakir Yang 2016-06-22 2:54 ` Yakir Yang 2016-06-22 2:54 ` Yakir Yang 2016-06-22 3:01 ` [PATCH v3.1 4/4] arm64: dts: " Yakir Yang 2016-06-22 3:01 ` Yakir Yang 2016-06-22 3:01 ` Yakir Yang
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='CAD=FV=URVQTvEKQbUVOXyMnO1a-kGs9inX_AZY3vo_YxXD5-5w@mail.gmail.com' \ --to=dianders@chromium.org \ --cc=devicetree@vger.kernel.org \ --cc=galak@codeaurora.org \ --cc=heiko@sntech.de \ --cc=ijc+devicetree@hellion.org.uk \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-rockchip@lists.infradead.org \ --cc=mark.yao@rock-chips.com \ --cc=olof@lixom.net \ --cc=robh+dt@kernel.org \ --cc=wxt@rock-chips.com \ --cc=ykk@rock-chips.com \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.