public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: Damon Ding <damon.ding@rock-chips•com>
To: hjc@rock-chips•com, heiko@sntech•de, andy.yan@rock-chips•com,
	maarten.lankhorst@linux•intel.com, mripard@kernel•org,
	tzimmermann@suse•de, airlied@gmail•com, simona@ffwll•ch,
	robh@kernel•org, krzk+dt@kernel•org, conor+dt@kernel•org,
	andrzej.hajda@intel•com, neil.armstrong@linaro•org,
	rfoss@kernel•org
Cc: Laurent.pinchart@ideasonboard•com, jonas@kwiboo•se,
	jernej.skrabec@gmail•com, nicolas.frattaroli@collabora•com,
	cristian.ciocaltea@collabora•com,
	sebastian.reichel@collabora•com,
	dmitry.baryshkov@oss•qualcomm.com, luca.ceresoli@bootlin•com,
	dianders@chromium•org, m.szyprowski@samsung•com,
	dri-devel@lists•freedesktop.org, devicetree@vger•kernel.org,
	linux-arm-kernel@lists•infradead.org,
	linux-rockchip@lists•infradead.org, linux-kernel@vger•kernel.org,
	Damon Ding <damon.ding@rock-chips•com>
Subject: [PATCH v4 1/3] dt-bindings: display: bridge: analogix-dp: Add data-lanes support for endpoint
Date: Fri, 29 May 2026 12:05:28 +0800	[thread overview]
Message-ID: <20260529040530.741336-2-damon.ding@rock-chips.com> (raw)
In-Reply-To: <20260529040530.741336-1-damon.ding@rock-chips.com>

Add data-lanes property support to the port@1 endpoint for physical
lane mapping configuration.

Lane mapping is mainly used for below scenarios:
1. Correct PCB lane swap and differential line routing crossover
   without hardware changes;
2. Adapt mismatched lane pin definitions between SoC and eDP panel;
3. Support multiple panel hardware variants on the same board
   by configuring data-lanes in device tree only.

Additionally, add data-lanes setting in Rockchip eDP DT node example
to show actual lane mapping usage.

Signed-off-by: Damon Ding <damon.ding@rock-chips•com>

---

Changes in v2:
- Add lane mapping application scenarios in commit message.
- Remove redundant deprecated property 'data-lanes' for eDP node.
- Update port@1 $ref to /schemas/graph.yaml#/$defs/port-base.

Changes in v3:
- Squash data-lanes adjustment of Rockchip eDP DT example into this
  commit.
- Add unevaluatedProperties: false to both the port@1 and endpoint
  nodes.
---
 .../bindings/display/bridge/analogix,dp.yaml  | 19 ++++++++++++++-----
 .../rockchip/rockchip,analogix-dp.yaml        |  1 +
 2 files changed, 15 insertions(+), 5 deletions(-)

diff --git a/Documentation/devicetree/bindings/display/bridge/analogix,dp.yaml b/Documentation/devicetree/bindings/display/bridge/analogix,dp.yaml
index 62f0521b0924..ecf206871cdd 100644
--- a/Documentation/devicetree/bindings/display/bridge/analogix,dp.yaml
+++ b/Documentation/devicetree/bindings/display/bridge/analogix,dp.yaml
@@ -42,13 +42,22 @@ properties:
     properties:
       port@0:
         $ref: /schemas/graph.yaml#/properties/port
-        description:
-          Input node to receive pixel data.
+        description: Input node to receive pixel data.
 
       port@1:
-        $ref: /schemas/graph.yaml#/properties/port
-        description:
-          Port node with one endpoint connected to a dp-connector node.
+        $ref: /schemas/graph.yaml#/$defs/port-base
+        unevaluatedProperties: false
+        description: Port node with one endpoint connected to sink device node.
+        properties:
+          endpoint:
+            $ref: /schemas/media/video-interfaces.yaml#
+            unevaluatedProperties: false
+            properties:
+              data-lanes:
+                minItems: 1
+                maxItems: 4
+                items:
+                  enum: [ 0, 1, 2, 3 ]
 
     required:
       - port@0
diff --git a/Documentation/devicetree/bindings/display/rockchip/rockchip,analogix-dp.yaml b/Documentation/devicetree/bindings/display/rockchip/rockchip,analogix-dp.yaml
index d99b23b88cc5..f690ee393fdb 100644
--- a/Documentation/devicetree/bindings/display/rockchip/rockchip,analogix-dp.yaml
+++ b/Documentation/devicetree/bindings/display/rockchip/rockchip,analogix-dp.yaml
@@ -117,6 +117,7 @@ examples:
           reg = <1>;
 
           edp_out_panel: endpoint {
+            data-lanes = <0 1>;
             remote-endpoint = <&panel_in_edp>;
           };
         };
-- 
2.34.1



  reply	other threads:[~2026-05-29  4:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29  4:05 [PATCH v4 0/3] Add eDP lane mapping support Damon Ding
2026-05-29  4:05 ` Damon Ding [this message]
2026-05-29 16:43   ` [PATCH v4 1/3] dt-bindings: display: bridge: analogix-dp: Add data-lanes support for endpoint Conor Dooley
2026-06-01 11:55   ` Sebastian Reichel
2026-05-29  4:05 ` [PATCH v4 2/3] drm/bridge: analogix_dp: Add validation for samsung,lane-count property Damon Ding
2026-05-30 13:33   ` Luca Ceresoli
2026-05-30 13:38     ` Luca Ceresoli
2026-06-01  2:59       ` Damon Ding
2026-06-01 12:02         ` Luca Ceresoli
2026-06-01 12:24           ` Damon Ding
2026-05-29  4:05 ` [PATCH v4 3/3] drm/bridge: analogix_dp: Add support for optional data-lanes mapping Damon Ding
2026-06-01 11:59   ` Sebastian Reichel

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=20260529040530.741336-2-damon.ding@rock-chips.com \
    --to=damon.ding@rock-chips$(echo .)com \
    --cc=Laurent.pinchart@ideasonboard$(echo .)com \
    --cc=airlied@gmail$(echo .)com \
    --cc=andrzej.hajda@intel$(echo .)com \
    --cc=andy.yan@rock-chips$(echo .)com \
    --cc=conor+dt@kernel$(echo .)org \
    --cc=cristian.ciocaltea@collabora$(echo .)com \
    --cc=devicetree@vger$(echo .)kernel.org \
    --cc=dianders@chromium$(echo .)org \
    --cc=dmitry.baryshkov@oss$(echo .)qualcomm.com \
    --cc=dri-devel@lists$(echo .)freedesktop.org \
    --cc=heiko@sntech$(echo .)de \
    --cc=hjc@rock-chips$(echo .)com \
    --cc=jernej.skrabec@gmail$(echo .)com \
    --cc=jonas@kwiboo$(echo .)se \
    --cc=krzk+dt@kernel$(echo .)org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-rockchip@lists$(echo .)infradead.org \
    --cc=luca.ceresoli@bootlin$(echo .)com \
    --cc=m.szyprowski@samsung$(echo .)com \
    --cc=maarten.lankhorst@linux$(echo .)intel.com \
    --cc=mripard@kernel$(echo .)org \
    --cc=neil.armstrong@linaro$(echo .)org \
    --cc=nicolas.frattaroli@collabora$(echo .)com \
    --cc=rfoss@kernel$(echo .)org \
    --cc=robh@kernel$(echo .)org \
    --cc=sebastian.reichel@collabora$(echo .)com \
    --cc=simona@ffwll$(echo .)ch \
    --cc=tzimmermann@suse$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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