From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Nikita Yushchenko <nikita.yoush@cogentembedded.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
dri-devel@lists.freedesktop.org,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: renesas: r8a77961: Add lvds0 device node
Date: Wed, 29 Dec 2021 21:33:20 +0200 [thread overview]
Message-ID: <Ycy4AMAT53Uzf+K7@pendragon.ideasonboard.com> (raw)
In-Reply-To: <39f70781-831e-c86a-ec5f-68f2b4bd3d62@cogentembedded.com>
Hi Nikita,
On Wed, Dec 29, 2021 at 08:19:10PM +0300, Nikita Yushchenko wrote:
> >> If this approach is not appropriate, then perhaps need to fix it in
> >> files for all SoCs, to make it possible for extension board dtsi to be
> >> compatible with all of them.
> >
> > I'm writing a patch to drop those right now :-) I'll CC you.
And of course I hit the send button too fast, sorry :-S
https://lore.kernel.org/linux-renesas-soc/20211229191838.27922-1-laurent.pinchart+renesas@ideasonboard.com/T/#t
> Ok.
>
> But, are you sure that empty nodes like these are that bad?
>
> I was going to suggest a movement in opposite direction - adding more such nodes, so they could form a
> sort of API for dts plugins describing e.g. displays connectable to boards based on different SoCs.
Endpoints are meant to model a link between two ports, so an endpoint
shouldn't exist in isolation. The issue with creating named endpoints in
SoC files is that you can't tell there what remote devices may exist, so
the endpoint may or may not match the actual hardware design of a board.
I think it's better to create endpoints on both sides together in
overlays.
https://lore.kernel.org/linux-renesas-soc/20211229193135.28767-2-laurent.pinchart+renesas@ideasonboard.com/T/#t
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2021-12-29 19:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-24 5:23 [PATCH 0/3] add R-Car M3-W+ (r8a99761) LVDS encoder support Nikita Yushchenko
2021-12-24 5:23 ` [PATCH 1/3] drm: rcar-du: lvds: Add r8a77961 support Nikita Yushchenko
2021-12-29 16:53 ` Laurent Pinchart
2021-12-24 5:23 ` [PATCH 2/3] arm64: dts: renesas: r8a77961: Add lvds0 device node Nikita Yushchenko
2021-12-29 16:56 ` Laurent Pinchart
2021-12-29 17:04 ` Nikita Yushchenko
2021-12-29 17:13 ` Laurent Pinchart
2021-12-29 17:19 ` Nikita Yushchenko
2021-12-29 19:33 ` Laurent Pinchart [this message]
2021-12-29 21:12 ` Nikita Yushchenko
2021-12-29 22:19 ` Laurent Pinchart
2021-12-30 5:30 ` Nikita Yushchenko
2021-12-30 17:11 ` Laurent Pinchart
2022-01-12 21:10 ` Nikita Yushchenko
2022-01-13 9:01 ` Geert Uytterhoeven
2022-01-10 8:43 ` Geert Uytterhoeven
2022-01-10 8:51 ` Laurent Pinchart
2022-01-10 8:52 ` Geert Uytterhoeven
2022-01-10 9:51 ` Nikita Yushchenko
2022-01-10 9:55 ` Geert Uytterhoeven
2021-12-24 5:23 ` [PATCH 3/3] dt-bindings: display: bridge: renesas,lvds: Document r8a77961 bindings Nikita Yushchenko
2021-12-29 16:46 ` Laurent Pinchart
2022-03-02 17:00 ` Geert Uytterhoeven
2022-03-03 9:14 ` Laurent Pinchart
2022-03-04 12:20 ` Laurent Pinchart
2022-01-04 20:19 ` Rob Herring
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=Ycy4AMAT53Uzf+K7@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert+renesas@glider.be \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=nikita.yoush@cogentembedded.com \
--cc=robh+dt@kernel.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