From: Heiko Stuebner <heiko@sntech.de>
To: Jacob Chen <jacob-chen@iotwrt.com>
Cc: linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 4/5] arm64: dts: rockchip: add rk3399 mipi nodes
Date: Sun, 06 Aug 2017 15:55:50 +0200 [thread overview]
Message-ID: <1762581.zRg8RSfhNk@phil> (raw)
In-Reply-To: <1500301019-9960-5-git-send-email-jacob-chen@iotwrt.com>
Am Montag, 17. Juli 2017, 22:16:58 CEST schrieb Jacob Chen:
> Add an mipi node, and also add mipi endpoints to vopb and vopl
> output port nodes.
>
> Signed-off-by: Jacob Chen <jacob-chen@iotwrt.com>
> ---
> arch/arm64/boot/dts/rockchip/rk3399.dtsi | 44 ++++++++++++++++++++++++++++++++
> 1 file changed, 44 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> index c0371af..5c5c9d9 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi
> @@ -1475,6 +1475,11 @@
> #address-cells = <1>;
> #size-cells = <0>;
>
> + vopl_out_mipi: endpoint@0 {
> + reg = <0>;
> + remote-endpoint = <&mipi_in_vopl>;
> + };
> +
> vopl_out_edp: endpoint@1 {
> reg = <1>;
> remote-endpoint = <&edp_in_vopl>;
> @@ -1516,6 +1521,11 @@
> remote-endpoint = <&edp_in_vopb>;
> };
>
> + vopb_out_mipi: endpoint@1 {
> + reg = <1>;
> + remote-endpoint = <&mipi_in_vopb>;
> + };
> +
> };
> };
>
> @@ -1531,6 +1541,40 @@
> status = "disabled";
> };
>
> + mipi_dsi: mipi@ff960000 {
> + compatible = "rockchip,rk3399-mipi-dsi", "snps,dw-mipi-dsi";
> + reg = <0x0 0xff960000 0x0 0x8000>;
> + interrupts = <GIC_SPI 45 IRQ_TYPE_LEVEL_HIGH 0>;
> + clocks = <&cru SCLK_MIPIDPHY_REF>, <&cru PCLK_MIPI_DSI0>,
> + <&cru SCLK_DPHY_TX0_CFG>;
> + clock-names = "ref", "pclk", "phy_cfg";
> + power-domains = <&power RK3399_PD_VIO>;
> + rockchip,grf = <&grf>;
> + #address-cells = <1>;
> + #size-cells = <0>;
I've dropped these, as the ports node does not need a regs property.
Similar to edp and hdmi.
> + status = "disabled";
> +
> + ports {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = <1>;
dropped this reg as well - see above
and applied the rest for 4.14
Thanks
Heiko
next prev parent reply other threads:[~2017-08-06 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 14:16 [PATCH v2 0/5] arm64: dts: add rk3399 display-related nodes Jacob Chen
2017-07-17 14:16 ` [PATCH v2 1/5] arm64: dts: rockchip: Add rk3399 vop and display-subsystem Jacob Chen
2017-08-06 13:45 ` Heiko Stuebner
2017-07-17 14:16 ` [PATCH v2 2/5] arm64: dts: rockchip: add pd_edp node for rk3399 Jacob Chen
2017-08-06 13:45 ` Heiko Stuebner
2017-07-17 14:16 ` [PATCH v2 3/5] arm64: dts: rockchip: add rk3399 edp nodes Jacob Chen
2017-08-06 13:53 ` Heiko Stuebner
2017-07-17 14:16 ` [PATCH v2 4/5] arm64: dts: rockchip: add rk3399 mipi nodes Jacob Chen
2017-08-06 13:55 ` Heiko Stuebner [this message]
2017-07-17 14:16 ` [PATCH v2 5/5] arm64: dts: rockchip: add rk3399 hdmi nodes Jacob Chen
2017-08-06 14:04 ` 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=1762581.zRg8RSfhNk@phil \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=jacob-chen@iotwrt.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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