From: Brian Norris <briannorris@chromium.org> To: heiko@sntech.de Cc: Archit Taneja <architt@codeaurora.org>, Andrzej Hajda <a.hajda@samsung.com>, Laurent Pinchart <Laurent.pinchart@ideasonboard.com>, David Airlie <airlied@linux.ie>, Yannick Fertre <yannick.fertre@st.com>, Philippe Cornu <philippe.cornu@st.com>, Benjamin Gaignard <benjamin.gaignard@linaro.org>, Vincent Abriou <vincent.abriou@st.com>, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Sean Paul <seanpaul@chromium.org>, Nickey Yang <nickey.yang@rock-chips.com>, hl@rock-chips.com, <linux-rockchip@lists.infradead.org>, mka@chromium.org, Doug Anderson <dianders@chromium.org>, robh+dt@kernel.org, mark.rutland@arm.com, hoegsberg@gmail.com, zyw@rock-chips.com, xbl@rock-chips.com, Brian Norris <briannorris@chromium.org> Subject: [PATCH v4] arm64: dts: rockchip: update mipi cells for RK3399 Date: Wed, 29 Nov 2017 10:47:55 -0800 [thread overview] Message-ID: <20171129184755.77187-1-briannorris@chromium.org> (raw) From: Nickey Yang <nickey.yang@rock-chips.com> We might include additional ports in derivative device trees, so the 'port' node should have an address, and the parent 'ports' node needs /#{addres,size}-cells. v4: * keep #{address,size}-cells in both 'ports' and 'port@0' nodes * separate from the rest of the series, since this is mostly independent of the driver refactoring Signed-off-by: Nickey Yang <nickey.yang@rock-chips.com> Signed-off-by: Brian Norris <briannorris@chromium.org> --- arch/arm64/boot/dts/rockchip/rk3399.dtsi | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi index d340b58ab184..c6dae25a3f23 100644 --- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi +++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi @@ -1652,7 +1652,11 @@ status = "disabled"; ports { - mipi_in: port { + #address-cells = <1>; + #size-cells = <0>; + + mipi_in: port@0 { + reg = <0>; #address-cells = <1>; #size-cells = <0>; -- 2.15.0.531.g2ccb3012c9-goog
WARNING: multiple messages have this Message-ID (diff)
From: Brian Norris <briannorris@chromium.org> To: heiko@sntech.de Cc: mark.rutland@arm.com, David Airlie <airlied@linux.ie>, dri-devel@lists.freedesktop.org, Philippe Cornu <philippe.cornu@st.com>, Laurent Pinchart <Laurent.pinchart@ideasonboard.com>, zyw@rock-chips.com, Brian Norris <briannorris@chromium.org>, linux-rockchip@lists.infradead.org, Nickey Yang <nickey.yang@rock-chips.com>, mka@chromium.org, xbl@rock-chips.com, hoegsberg@gmail.com, robh+dt@kernel.org, Vincent Abriou <vincent.abriou@st.com>, hl@rock-chips.com, Doug Anderson <dianders@chromium.org>, linux-kernel@vger.kernel.org, Yannick Fertre <yannick.fertre@st.com> Subject: [PATCH v4] arm64: dts: rockchip: update mipi cells for RK3399 Date: Wed, 29 Nov 2017 10:47:55 -0800 [thread overview] Message-ID: <20171129184755.77187-1-briannorris@chromium.org> (raw) From: Nickey Yang <nickey.yang@rock-chips.com> We might include additional ports in derivative device trees, so the 'port' node should have an address, and the parent 'ports' node needs /#{addres,size}-cells. v4: * keep #{address,size}-cells in both 'ports' and 'port@0' nodes * separate from the rest of the series, since this is mostly independent of the driver refactoring Signed-off-by: Nickey Yang <nickey.yang@rock-chips.com> Signed-off-by: Brian Norris <briannorris@chromium.org> --- arch/arm64/boot/dts/rockchip/rk3399.dtsi | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi b/arch/arm64/boot/dts/rockchip/rk3399.dtsi index d340b58ab184..c6dae25a3f23 100644 --- a/arch/arm64/boot/dts/rockchip/rk3399.dtsi +++ b/arch/arm64/boot/dts/rockchip/rk3399.dtsi @@ -1652,7 +1652,11 @@ status = "disabled"; ports { - mipi_in: port { + #address-cells = <1>; + #size-cells = <0>; + + mipi_in: port@0 { + reg = <0>; #address-cells = <1>; #size-cells = <0>; -- 2.15.0.531.g2ccb3012c9-goog _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-11-29 18:48 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-11-29 18:47 Brian Norris [this message] 2017-11-29 18:47 ` [PATCH v4] arm64: dts: rockchip: update mipi cells for RK3399 Brian Norris 2017-11-29 20:52 ` Doug Anderson 2017-11-29 20:52 ` Doug Anderson 2017-12-04 10:05 ` Heiko Stuebner 2017-12-04 13:22 ` Laurent Pinchart 2017-12-04 13:22 ` Laurent Pinchart 2017-12-04 13:46 ` Heiko Stuebner 2017-12-04 13:46 ` Heiko Stuebner 2017-12-04 16:36 ` Laurent Pinchart 2017-12-04 16:36 ` Laurent Pinchart
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=20171129184755.77187-1-briannorris@chromium.org \ --to=briannorris@chromium.org \ --cc=Laurent.pinchart@ideasonboard.com \ --cc=a.hajda@samsung.com \ --cc=airlied@linux.ie \ --cc=architt@codeaurora.org \ --cc=benjamin.gaignard@linaro.org \ --cc=dianders@chromium.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=heiko@sntech.de \ --cc=hl@rock-chips.com \ --cc=hoegsberg@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-rockchip@lists.infradead.org \ --cc=mark.rutland@arm.com \ --cc=mka@chromium.org \ --cc=nickey.yang@rock-chips.com \ --cc=philippe.cornu@st.com \ --cc=robh+dt@kernel.org \ --cc=seanpaul@chromium.org \ --cc=vincent.abriou@st.com \ --cc=xbl@rock-chips.com \ --cc=yannick.fertre@st.com \ --cc=zyw@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.