From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Cc: Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [PATCH 2/2] arm64: dts: renesas: Remove empty rgb output endpoints
Date: Wed, 26 Jan 2022 12:10:12 +0100 [thread overview]
Message-ID: <CAMuHMdXzrmRNQdgm+67Y+hRxHxBvSMejF-69xon2QJG2fuD-Ug@mail.gmail.com> (raw)
In-Reply-To: <20211229191838.27922-2-laurent.pinchart+renesas@ideasonboard.com>
Hi Laurent,
On Wed, Dec 29, 2021 at 8:18 PM Laurent Pinchart
<laurent.pinchart+renesas@ideasonboard.com> wrote:
> Endpoints node must have a remote-endpoint property, as endpoints only
> exist to model a link between ports. Drop the empty rgb output endpoints
> from SoC dtsi files, and declare them in the board dts instead.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Thanks for your patch!
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
If we go this route, ulcb-kf.dtsi needs a similar change as
beacon-renesom-baseboard.dtsi.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2022-01-26 11:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 19:18 [PATCH 1/2] arm64: dts: renesas: Remove empty lvds endpoints Laurent Pinchart
2021-12-29 19:18 ` [PATCH 2/2] arm64: dts: renesas: Remove empty rgb output endpoints Laurent Pinchart
2022-01-26 11:10 ` Geert Uytterhoeven [this message]
2022-02-21 14:26 ` Kieran Bingham
2022-01-10 10:10 ` [PATCH 1/2] arm64: dts: renesas: Remove empty lvds endpoints Geert Uytterhoeven
2022-01-10 11:24 ` Laurent Pinchart
2022-01-10 12:07 ` Geert Uytterhoeven
2022-02-21 14:10 ` Laurent Pinchart
2022-02-21 14:17 ` Kieran Bingham
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=CAMuHMdXzrmRNQdgm+67Y+hRxHxBvSMejF-69xon2QJG2fuD-Ug@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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;
as well as URLs for NNTP newsgroup(s).