From: Jagan Teki <jagan@amarulasolutions.com>
To: Maxime Ripard <maxime@cerno.tech>
Cc: Dave Stevenson <dave.stevenson@raspberrypi.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
Sam Ravnborg <sam@ravnborg.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, devicetree@vger.kernel.org,
dri-devel@lists.freedesktop.org, Marek Vasut <marex@denx.de>,
linux-amarula <linux-amarula@amarulasolutions.com>
Subject: Re: [PATCH v7 09/12] arm64: dts: rockchip: a64: Add endpoint@0 to dsi_in_tcon0
Date: Wed, 29 Mar 2023 21:00:22 +0530 [thread overview]
Message-ID: <CAMty3ZDXWw2ajF5DsYCMy0XCa348y8XKKUzAfrU=2iUG23yVow@mail.gmail.com> (raw)
In-Reply-To: <20230329150202.3rbjrq6iqum5ybjh@penduick>
On Wed, Mar 29, 2023 at 8:32 PM Maxime Ripard <maxime@cerno.tech> wrote:
>
> The commit title is wrong, it's not a rockchip device.
Thanks for the note, I will fix it in the next version.
>
> On Wed, Mar 29, 2023 at 06:46:15PM +0530, Jagan Teki wrote:
> > The DSI downstream devices are likely to be Panel, Bridge and
> > I2C-Configured Bridge.
> >
> > It is possible to connect all three devices using upstream OF-graph port
> > or ports node however only Panel and Bridge are possible to connect via
> > child node but not possible to connect I2C-Configured Bridge via child
> > node since I2C-Configure bridges are child of I2C not upstream DSI hosts
> > and it must represent them via port or ports with endpoint linking.
> >
> > Allwinner A64 DSI node already has a port so add endpoint 0 for input
> > tcon so that the downstream DSI devices can use endpoint 1 to connect
> > Panel or Bridge or I2C-Configured Bridge.
> >
> > An example of the I2C-Configured downstream bridge representation is,
> >
> > i2c1 {
> > bridge@1b {
> > compatible = "ti,dlpc3433";
> >
> > ports {
> > port@0 {
> > reg = <0>;
> >
> > bridge_in_dsi: endpoint {
> > remote-endpoint = <&dsi_out_bridge>;
> > data-lanes = <1 2 3 4>;
> > };
> > };
> >
> > port@2 {
> > reg = <2>;
> >
> > bridge_out_dmd: endpoint {
> > remote-endpoint = <&dmd_out_bridge>;
> > };
> > };
> > };
> > };
> > };
> >
> > dsi {
> > compatible = "allwinner,sun50i-a64-mipi-dsi";
> >
> > port {
> > dsi_in_tcon0: endpoint@0 {
> > reg = <0>;
> > remote-endpoint = <tcon0_out_dsi>;
> > };
> >
> > dsi_out_bridge: endpoint@1 {
> > reg = <1>;
> > remote-endpoint = <&bridge_in_dsi>;
> > };
> > };
> > };
> >
> > Note that existing device bindings are untouched and still represent
> > the downstream devices via child nodes since the sun6i-mipi-dsi host
> > will migrate to a standardized single helper to lookup for a
> > downstream device via child or OF-graph port or port node.
> >
> > Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
> > ---
> > Changes for v7:
> > - new patch
> >
> > arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi b/arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi
> > index 77b5349f6087..3ed566dc2172 100644
> > --- a/arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi
> > +++ b/arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi
> > @@ -1189,7 +1189,11 @@ dsi: dsi@1ca0000 {
> > #size-cells = <0>;
> >
> > port {
> > - dsi_in_tcon0: endpoint {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + dsi_in_tcon0: endpoint@0 {
> > + reg = <0>;
> > remote-endpoint = <&tcon0_out_dsi>;
> > };
>
> That doesn't match the DT binding anymore, and why can't we add endpoint@1 there too?
Do you mean add endpoint@1 without any remote-endpoint like this?
dsi_out_bridge: endpoint@1 {
reg = <1>;
};
I was supposed to add this, since dtbs_check doesn't give any error. I
have skipped this, as I thought it wouldn't be needed.
Thanks,
agan.
prev parent reply other threads:[~2023-03-29 15:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 13:16 [PATCH v7 00/12] drm: sun4i: Convert Allwinner DSI to bridge Jagan Teki
2023-03-29 13:16 ` [PATCH v7 01/12] drm: of: Lookup if child node has DSI panel or bridge Jagan Teki
2023-03-29 13:16 ` [PATCH v7 02/12] drm: bridge: panel: Implement drmm_of_dsi_get_bridge helper Jagan Teki
2023-03-29 15:03 ` Maxime Ripard
2023-03-29 15:26 ` Jagan Teki
2023-03-29 16:08 ` Maxime Ripard
2023-03-29 13:16 ` [PATCH v7 03/12] drm: panel: feiyang-fy07024di26a30d: Enable prepare_prev_first flag Jagan Teki
2023-03-29 13:16 ` [PATCH v7 04/12] drm: panel: sitronix-st7701: Enable prepare_prev_first for ts8550b Jagan Teki
2023-03-29 13:16 ` [PATCH v7 05/12] drm: panel: sitronix-st7703: Enable prepare_prev_first for xbd599 Jagan Teki
2023-03-29 13:16 ` [PATCH v7 06/12] drm: panel: feixin-k101-im2ba02: Enable prepare_prev_first flag Jagan Teki
2023-03-29 13:16 ` [PATCH v7 07/12] drm: panel: ilitek-ili9881c: Enable prepare_prev_first for k101_im2byl02 Jagan Teki
2023-03-29 13:16 ` [PATCH v7 08/12] ARM: dts: sun8i: a33: Add endpoint@0 to dsi_in_tcon0 Jagan Teki
2023-03-29 13:16 ` [PATCH v7 09/12] arm64: dts: rockchip: a64: " Jagan Teki
2023-03-29 15:02 ` Maxime Ripard
2023-03-29 15:30 ` Jagan Teki [this message]
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='CAMty3ZDXWw2ajF5DsYCMy0XCa348y8XKKUzAfrU=2iUG23yVow@mail.gmail.com' \
--to=jagan@amarulasolutions.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=daniel@ffwll.ch \
--cc=dave.stevenson@raspberrypi.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marex@denx.de \
--cc=maxime@cerno.tech \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=samuel@sholland.org \
--cc=tzimmermann@suse.de \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).