From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-m32113.qiye.163.com (mail-m32113.qiye.163.com [220.197.32.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 40DE629B8D3; Thu, 21 May 2026 11:50:30 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=220.197.32.113 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779364234; cv=none; b=utCpsp3pRiOpg8wGgvMQTSRAGuWKUy40QfkNTadCTKH/+txKvEef93JSsq2UJKZge47FQB1nURDSbCw3tqSUF4gW4/flMuyK+s67HKqtM4bBq4QLr1Mp8FGJ3RBXkApE9vxE+iVoPRaZLXYI3zqORXRqZGWPnAGkSPhr6GJoVbw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779364234; c=relaxed/simple; bh=hv/b2JEP0rFcDiORQeZUL3yvj5BqbgW/0ZCO4PxG73U=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=UrTzt9UpgKMPAv9w0cwcCKv33oDfTv4afwWMqEawLlwHRCSxm+l3bW9E9XTmAA0uPY59Sh67NCmasoNuk5RRB5FqRFB/1bWdgB1rgoHFQaAa/B76oIk7q2FYEQ0YxB0LDqvGJJ86svSxz1KxPzR8/yOWKOfZJLh+Tp9Xp2TdQC8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=rock-chips.com; spf=pass smtp.mailfrom=rock-chips.com; dkim=pass (1024-bit key) header.d=rock-chips.com header.i=@rock-chips.com header.b=ZE0YpwEZ; arc=none smtp.client-ip=220.197.32.113 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=rock-chips.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=rock-chips.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=rock-chips.com header.i=@rock-chips.com header.b="ZE0YpwEZ" Received: from zyb-HP-ProDesk-680-G2-MT.. (unknown [61.154.14.86]) by smtp.qiye.163.com (Hmail) with ESMTP id 3f500942d; Thu, 21 May 2026 19:45:12 +0800 (GMT+08:00) From: Damon Ding 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 Subject: [PATCH v2 0/3] Add eDP lane mapping support Date: Thu, 21 May 2026 19:44:56 +0800 Message-Id: <20260521114459.1394264-1-damon.ding@rock-chips.com> X-Mailer: git-send-email 2.34.1 Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-HM-Tid: 0a9e4a5a995303a3kunmad9184e677760 X-HM-MType: 1 X-HM-Spam-Status: e1kfGhgUHx5ZQUpXWQgPGg8OCBgUHx5ZQUlOS1dZFg8aDwILHllBWSg2Ly tZV1koWUFITzdXWRgWCB1ZQUpXWS1ZQUlXWQ8JGhUIEh9ZQVkaSEwYVkpJSBpOTB8aGkgfS1YVFA kWGhdVEwETFhoSFyQUDg9ZV1kYEgtZQVlNSlVKTk9VSk9VQ01ZV1kWGg8SFR0UWUFZT0tIVUpLSE pKQk1VSktLVUpCWQY+ DKIM-Signature: a=rsa-sha256; b=ZE0YpwEZWOUjGg4dZS+BlhrYaNqZu/1+D2j4l2FfCCD0Ctd5AWtMzB9HqcDLVGs+CojaQLRwgG/eeViA001Q1vlrfkk5v415ccWoqaz3bgIVSuzXNV5LeSxU+WrCPr+smsgD42L2PSfnFa2JgE96U+4Sp9RkIwiIUnXLlxahEYs=; c=relaxed/relaxed; s=default; d=rock-chips.com; v=1; bh=+c7EBOaha3ykXg57gl7+bgXFaoZyrHAigjyfIwL1hGc=; h=date:mime-version:subject:message-id:from; This series adds configurable eDP/DP physical lane mapping support via device tree data-lanes property. 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. The series includes driver implementation and device tree binding updates to support custom lane mapping configuration from endpoint node, and keeps default linear lane order if no configuration is given. Patch 1: Add endpoint data-lanes property to analogix-dp binding Patch 2: Add data-lanes property example in rockchip analogix-dp binding Patch 3: Implement lane mapping in analogix_dp driver Damon Ding (3): dt-bindings: display: bridge: analogix-dp: Add data-lanes support for endpoint dt-bindings: rockchip: analogix-dp: Add data-lanes example drm/bridge: analogix_dp: Add support for optional data-lanes mapping .../bindings/display/bridge/analogix,dp.yaml | 17 ++++-- .../rockchip/rockchip,analogix-dp.yaml | 1 + .../drm/bridge/analogix/analogix_dp_core.c | 56 +++++++++++++++++++ .../drm/bridge/analogix/analogix_dp_core.h | 4 +- .../gpu/drm/bridge/analogix/analogix_dp_reg.c | 15 +++-- .../gpu/drm/bridge/analogix/analogix_dp_reg.h | 4 ++ 6 files changed, 83 insertions(+), 14 deletions(-) --- 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. -- 2.34.1