From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-m49226.qiye.163.com (mail-m49226.qiye.163.com [45.254.49.226]) (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 D2A9C3C81AA; Fri, 15 May 2026 02:58:57 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.254.49.226 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778813942; cv=none; b=P57zp0V9M4/8EiAg9Rp45jjsubiI5oaxJ3ccoefO/lM5r5LDn0HcRmMzzpZ+cMcJ5vy2KzRNJ4yo3XRgEyeP0YnK1Y+RCjZXoUy+cA7EIJlO3icZFLgxrejUawT8ockpFDYm5DKHxUVoc/gl8Jp9Oc9/kF5WgDaGFn/GRnS7YK0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778813942; c=relaxed/simple; bh=PvGdAfskjOnfJFGxIFXft0jY6m3RugZRW95j804rXso=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=N/2VSLbdrYXJwnFF8ZguRH4C16+2WCB1Ft7jM7zwCP1dFr1MUgpVxLRWKinqwzHqjUrTbEF9gRHivNuiSDjKx05aEyeJ/7zwWhno1q0qA588m0s+1HP1JMZsyxdN1Lkan2/JEbRV3wH632ExWAIpBO3RV2gId1uzAum6/SnfE5Y= 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=bNuiS2Dr; arc=none smtp.client-ip=45.254.49.226 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="bNuiS2Dr" Received: from [172.16.12.43] (unknown [58.22.7.114]) by smtp.qiye.163.com (Hmail) with ESMTP id 3e805fe57; Fri, 15 May 2026 10:53:37 +0800 (GMT+08:00) Message-ID: Date: Fri, 15 May 2026 10:53:37 +0800 Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v1 2/3] dt-bindings: display: bridge: analogix-dp: Add data-lanes support for endpoint To: Conor Dooley Cc: 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, 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 References: <20260514070133.2275069-1-damon.ding@rock-chips.com> <20260514070133.2275069-3-damon.ding@rock-chips.com> <20260514-jolly-confining-997882e502c7@spud> Content-Language: en-US From: Damon Ding In-Reply-To: <20260514-jolly-confining-997882e502c7@spud> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-HM-Tid: 0a9e298dc37203a3kunm6bd5d8e111d35b X-HM-MType: 1 X-HM-Spam-Status: e1kfGhgUHx5ZQUpXWQgPGg8OCBgUHx5ZQUlOS1dZFg8aDwILHllBWSg2Ly tZV1koWUFDSUNOT01LS0k3V1kYFggdWUFKV1ktWUFJV1kPCRoVCBIfWUFZGhofSVZPShpPHUtKTB pLTEtWFRQJFhoXVRMBExYaEhckFA4PWVdZGBILWUFZTkNVSUlVTFVKSk9ZV1kWGg8SFR0UWUFZT0 tIVUpLSEpKQk1VSktLVUpCWQY+ DKIM-Signature: a=rsa-sha256; b=bNuiS2Dre4Q5BTbn3B1+0fBx2UlyKHcHIU2sndZ4rhJCriwHPmLgl2XgQ0+5OezFxNij6gzxyCaFuJ9XbQD19js2/mtL18ORxirq3opoRFCafpHIl1GwXZuzlWA27nAx7xFTpabrXENpRkIAGv0cmL/NRF6OFA+Vs0hUey4n0NI=; c=relaxed/relaxed; s=default; d=rock-chips.com; v=1; bh=wiOcpYgO5JDj+FjoQaOM0eym/Auz/dWfyTv2lzex6Rs=; h=date:mime-version:subject:message-id:from; Hi Conor, On 5/15/2026 2:19 AM, Conor Dooley wrote: > On Thu, May 14, 2026 at 03:01:32PM +0800, Damon Ding wrote: >> Add data-lanes property support to the port@1 endpoint for physical >> lane mapping configuration. >> >> Signed-off-by: Damon Ding >> --- >> .../bindings/display/bridge/analogix,dp.yaml | 24 +++++++++++++++---- >> 1 file changed, 20 insertions(+), 4 deletions(-) >> >> diff --git a/Documentation/devicetree/bindings/display/bridge/analogix,dp.yaml b/Documentation/devicetree/bindings/display/bridge/analogix,dp.yaml >> index 62f0521b0924..a82f9b7776c0 100644 >> --- a/Documentation/devicetree/bindings/display/bridge/analogix,dp.yaml >> +++ b/Documentation/devicetree/bindings/display/bridge/analogix,dp.yaml >> @@ -36,19 +36,35 @@ properties: >> Hotplug detect GPIO. >> Indicates which GPIO should be used for hotplug detection >> >> + data-lanes: >> + $ref: /schemas/types.yaml#/definitions/uint32-array >> + deprecated: true > > Why are you adding a new property as deprecated? Why does this duplicate > what you're adding to the port node? At the very least, your commit is > lacking an explanation. > pw-bot: changes-requested > Thank you for the review. I referenced the implementation in Documentation/devicetree/bindings/display/msm/dp-controller.yaml. After evaluating QCOM DP driver and other drivers, I agree that implementing 'data-lanes' in the endpoint node is the preferred and common approach nowadays. The top-level `data-lanes` property together with the `deprecated` mark was leftover content from my early reference and arrangement, which I neglected to delete before submitting. It is redundant, unreasonable and should not have been added at all. I will fix it in the next version. Best regards, Damon > >> + minItems: 1 >> + maxItems: 4 >> + items: >> + maximum: 3 >> + >> ports: >> $ref: /schemas/graph.yaml#/properties/ports >> >> 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. >> + 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 >> -- >> 2.34.1 >>