From: Hongyang Zhao <hongyang.zhao@thundersoft.com>
To: Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Vinod Koul <vkoul@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Hongyang Zhao <hongyang.zhao@thundersoft.com>,
Roger Shimizu <rosh@debian.org>
Subject: [PATCH v2 1/3] dt-bindings: display: lt9611: Support single Port B input
Date: Wed, 28 Jan 2026 19:15:45 +0800 [thread overview]
Message-ID: <20260128-rubikpi-next-20260116-v2-1-ba51ce8d2bd2@thundersoft.com> (raw)
In-Reply-To: <20260128-rubikpi-next-20260116-v2-0-ba51ce8d2bd2@thundersoft.com>
The LT9611 has two DSI input ports (Port A and Port B). Update the
binding to clearly document the port mapping and allow using Port B
alone when DSI is physically connected to Port B only.
Changes:
- Clarify port@0 corresponds to DSI Port A input
- Clarify port@1 corresponds to DSI Port B input
- Change port requirement from mandatory port@0 to anyOf port@0/port@1,
allowing either port to be used independently
Signed-off-by: Hongyang Zhao <hongyang.zhao@thundersoft.com>
Reviewed-by: Roger Shimizu <rosh@debian.org>
---
.../bindings/display/bridge/lontium,lt9611.yaml | 15 +++++++++++----
1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/display/bridge/lontium,lt9611.yaml b/Documentation/devicetree/bindings/display/bridge/lontium,lt9611.yaml
index 655db8cfdc25..429a06057ae8 100644
--- a/Documentation/devicetree/bindings/display/bridge/lontium,lt9611.yaml
+++ b/Documentation/devicetree/bindings/display/bridge/lontium,lt9611.yaml
@@ -44,21 +44,28 @@ properties:
port@0:
$ref: /schemas/graph.yaml#/properties/port
description:
- Primary MIPI port-1 for MIPI input
+ DSI Port A input. directly drives the display, or works in
+ combination with Port B for higher resolution displays.
port@1:
$ref: /schemas/graph.yaml#/properties/port
description:
- Additional MIPI port-2 for MIPI input, used in combination
- with primary MIPI port-1 to drive higher resolution displays
+ DSI Port B input. Can be used alone if DSI is physically
+ connected to Port B, or in combination with Port A for higher
+ resolution displays.
port@2:
$ref: /schemas/graph.yaml#/properties/port
description:
HDMI port for HDMI output
+ anyOf:
+ - required:
+ - port@0
+ - required:
+ - port@1
+
required:
- - port@0
- port@2
required:
--
2.43.0
next prev parent reply other threads:[~2026-01-28 11:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 11:15 [PATCH v2 0/3] Add DSI Port B input support for LT9611 HDMI bridge Hongyang Zhao
2026-01-28 11:15 ` Hongyang Zhao [this message]
2026-01-29 8:35 ` [PATCH v2 1/3] dt-bindings: display: lt9611: Support single Port B input Neil Armstrong
2026-02-05 13:07 ` Krzysztof Kozlowski
2026-02-05 20:31 ` Roger Shimizu
2026-02-06 7:08 ` Krzysztof Kozlowski
2026-02-06 9:49 ` Roger Shimizu
2026-02-06 10:55 ` Krzysztof Kozlowski
2026-02-07 5:22 ` Roger Shimizu
2026-02-07 9:35 ` Krzysztof Kozlowski
2026-02-07 10:35 ` Roger Shimizu
2026-01-28 11:15 ` [PATCH v2 2/3] drm/bridge: lt9611: Add support for " Hongyang Zhao
2026-01-29 0:47 ` Dmitry Baryshkov
2026-01-28 11:15 ` [PATCH v2 3/3] arm64: dts: qcom: qcs6490-rubikpi3: Use lt9611 DSI Port B Hongyang Zhao
2026-01-28 11:26 ` Konrad Dybcio
2026-02-05 13:09 ` Krzysztof Kozlowski
2026-02-05 19:36 ` Roger Shimizu
2026-02-06 7:08 ` Krzysztof Kozlowski
2026-02-07 5:24 ` Roger Shimizu
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=20260128-rubikpi-next-20260116-v2-1-ba51ce8d2bd2@thundersoft.com \
--to=hongyang.zhao@thundersoft.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=andrzej.hajda@intel.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=rosh@debian.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=vkoul@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
all inboxes | Powered by JetHome®