From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: r8a7795: salvator-x: Move HDMI0 to common Salvator-X board support
Date: Mon, 15 May 2017 15:29:39 +0300 [thread overview]
Message-ID: <11510386.Oacl68du7i@avalon> (raw)
In-Reply-To: <1494850964-7246-3-git-send-email-geert+renesas@glider.be>
Hi Geert,
Thank you for the patch.
On Monday 15 May 2017 14:22:44 Geert Uytterhoeven wrote:
> The extensions to the first HDMI device and connector nodes apply to
> Salvator-X boards equipped with either an R-Car H3 or M3-W SoC.
> Hence move them from the R-Car H3 specific board file to the common
> Salvator-X board file.
>
> The second HDMI device and connector nodes are left as-is, as R-Car M3-W
> has only one HDMI output.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
I wonder whether this is really worth it, given that the number of HDMI ports
is different between the two boards. I actually had similar patches in my tree
and then decided to drop them, as I found that splitting the H3 Salvator-X
HDMI ports salvator-x.dtsi and r8a7795-salvator-x.dts was getting pretty
confusing.
> ---
> arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts | 17 -----------------
> arch/arm64/boot/dts/renesas/salvator-x.dtsi | 17 +++++++++++++++++
> 2 files changed, 17 insertions(+), 17 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts
> b/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts index
> fcd9ca73f2c76768..22e5324e7ada0eea 100644
> --- a/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts
> +++ b/arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dts
> @@ -58,23 +58,6 @@
> status = "okay";
> };
>
> -&hdmi0 {
> - status = "okay";
> -
> - ports {
> - port@1 {
> - reg = <1>;
> - rcar_dw_hdmi0_out: endpoint {
> - remote-endpoint = <&hdmi0_con>;
> - };
> - };
> - };
> -};
> -
> -&hdmi0_con {
> - remote-endpoint = <&rcar_dw_hdmi0_out>;
> -};
> -
> &hdmi1 {
> status = "okay";
>
> diff --git a/arch/arm64/boot/dts/renesas/salvator-x.dtsi
> b/arch/arm64/boot/dts/renesas/salvator-x.dtsi index
> 5f0d4bdcd3b44aae..1f6b9fbb13af1ebf 100644
> --- a/arch/arm64/boot/dts/renesas/salvator-x.dtsi
> +++ b/arch/arm64/boot/dts/renesas/salvator-x.dtsi
> @@ -294,6 +294,23 @@
> clock-frequency = <32768>;
> };
>
> +&hdmi0 {
> + status = "okay";
> +
> + ports {
> + port@1 {
> + reg = <1>;
> + rcar_dw_hdmi0_out: endpoint {
> + remote-endpoint = <&hdmi0_con>;
> + };
> + };
> + };
> +};
> +
> +&hdmi0_con {
> + remote-endpoint = <&rcar_dw_hdmi0_out>;
> +};
> +
> &hsusb {
> status = "okay";
> };
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-05-15 12:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 12:22 [PATCH 0/2] arm64: dts: salvator-x: Move HDMI0 to common Salvator-X board support Geert Uytterhoeven
2017-05-15 12:22 ` [PATCH 1/2] arm64: dts: r8a7796: Add placeholder for HDMI device Geert Uytterhoeven
2017-05-15 12:22 ` [PATCH 2/2] arm64: dts: r8a7795: salvator-x: Move HDMI0 to common Salvator-X board support Geert Uytterhoeven
2017-05-15 12:29 ` Laurent Pinchart [this message]
2017-05-15 12:47 ` Geert Uytterhoeven
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=11510386.Oacl68du7i@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=geert+renesas@glider.be \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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: link
Be 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.