All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
To: linux-renesas-soc@vger.kernel.org,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Geert Uytterhoeven <geert@glider.be>
Cc: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org (open list:OPEN FIRMWARE AND
	FLATTENED DEVICE TREE BINDINGS),
	linux-kernel@vger.kernel.org (open list)
Subject: [PATCH v4 4/4] arm64: dts: renesas: r8a779a0: Provide default DSI data-lanes
Date: Fri, 26 Nov 2021 09:54:45 +0000	[thread overview]
Message-ID: <20211126095445.932930-5-kieran.bingham+renesas@ideasonboard.com> (raw)
In-Reply-To: <20211126095445.932930-1-kieran.bingham+renesas@ideasonboard.com>

The data-lanes is a mandatory property for the endpoints.
Provide a default when not connected that represents the maximum
lanes supported by the device.

A connected device should override the data-lanes if it uses a lower
number of lanes.

Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
---

This patch is split from 2/4 to keep it's change for distinct review.
The data-lanes is marked as a mandatory property in the DSI bindings
(which are out of tree, most recent posting at [0])

[0] https://lore.kernel.org/all/YQGFP%2FcFoSksPyn+@pendragon.ideasonboard.com/

The data-lanes property is marked as mandatory, which means it needs to
be provided even when supplying the port templates which get overridden
later. Is this expected behaviour?

Does this have sufficient meaning? Or will it always have to be
specified by any node overriding anyway...?


 arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/arch/arm64/boot/dts/renesas/r8a779a0.dtsi b/arch/arm64/boot/dts/renesas/r8a779a0.dtsi
index fdad8bc4a069..7322c4628e2b 100644
--- a/arch/arm64/boot/dts/renesas/r8a779a0.dtsi
+++ b/arch/arm64/boot/dts/renesas/r8a779a0.dtsi
@@ -2661,6 +2661,7 @@ dsi0_in: endpoint {
 				port@1 {
 					reg = <1>;
 					dsi0_out: endpoint {
+						data-lanes = <1 2 3 4>;
 					};
 				};
 			};
@@ -2691,7 +2692,9 @@ dsi1_in: endpoint {
 
 				port@1 {
 					reg = <1>;
+
 					dsi1_out: endpoint {
+						data-lanes = <1 2 3 4>;
 					};
 				};
 			};
-- 
2.30.2


  parent reply	other threads:[~2021-11-26  9:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-26  9:54 [PATCH v4 0/4] arm64: dts: renesas: r8a779a0 DU support Kieran Bingham
2021-11-26  9:54 ` [PATCH v4 1/4] arm64: dts: renesas: r8a779a0: Add " Kieran Bingham
2021-11-26 12:51   ` Geert Uytterhoeven
2021-11-26  9:54 ` [PATCH v4 2/4] arm64: dts: renesas: r8a779a0: Add DSI encoders Kieran Bingham
2021-11-26  9:54 ` [PATCH v4 3/4] arm64: dts: renesas: r8a779a0: falcon-cpu: Add DSI display output Kieran Bingham
2021-11-26  9:54 ` Kieran Bingham [this message]
2021-11-26 13:08   ` [PATCH v4 4/4] arm64: dts: renesas: r8a779a0: Provide default DSI data-lanes 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=20211126095445.932930-5-kieran.bingham+renesas@ideasonboard.com \
    --to=kieran.bingham+renesas@ideasonboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@glider.be \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.