From: Liu Ying <victor.liu@nxp.com>
To: Biju Das <biju.das.jz@bp.renesas.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Cc: "andrzej.hajda@intel.com" <andrzej.hajda@intel.com>,
"neil.armstrong@linaro.org" <neil.armstrong@linaro.org>,
"rfoss@kernel.org" <rfoss@kernel.org>,
"laurent.pinchart" <laurent.pinchart@ideasonboard.com>,
"jonas@kwiboo.se" <jonas@kwiboo.se>,
"jernej.skrabec@gmail.com" <jernej.skrabec@gmail.com>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"mripard@kernel.org" <mripard@kernel.org>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
"airlied@gmail.com" <airlied@gmail.com>,
"simona@ffwll.ch" <simona@ffwll.ch>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"quic_jesszhan@quicinc.com" <quic_jesszhan@quicinc.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
"sakari.ailus@linux.intel.com" <sakari.ailus@linux.intel.com>,
"hverkuil@xs4all.nl" <hverkuil@xs4all.nl>,
"tomi.valkeinen@ideasonboard.com"
<tomi.valkeinen@ideasonboard.com>,
"quic_bjorande@quicinc.com" <quic_bjorande@quicinc.com>,
"geert+renesas@glider.be" <geert+renesas@glider.be>,
"dmitry.baryshkov@linaro.org" <dmitry.baryshkov@linaro.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"nfraprado@collabora.com" <nfraprado@collabora.com>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"sam@ravnborg.org" <sam@ravnborg.org>,
"marex@denx.de" <marex@denx.de>
Subject: Re: [PATCH v4 08/13] dt-bindings: display: Document dual-link LVDS display common properties
Date: Tue, 29 Oct 2024 15:35:05 +0800 [thread overview]
Message-ID: <a166da61-8cd4-44c9-987b-94d8a62faf82@nxp.com> (raw)
In-Reply-To: <TY3PR01MB1134610B42A1D3424D97B04CA864B2@TY3PR01MB11346.jpnprd01.prod.outlook.com>
On 10/29/2024, Biju Das wrote:
> Hi Liu Ying,
Hi Biju,
>
>> -----Original Message-----
>> From: Liu Ying <victor.liu@nxp.com>
>> Sent: 29 October 2024 07:13
>> Subject: Re: [PATCH v4 08/13] dt-bindings: display: Document dual-link LVDS display common properties
>>
>> On 10/29/2024, Biju Das wrote:
>>> Hi Liu Ying,
>>
>> Hi Biju,
>>
>>>
>>>> -----Original Message-----
>>>> From: Liu Ying <victor.liu@nxp.com>
>>>> Sent: 29 October 2024 06:17
>>>> Subject: Re: [PATCH v4 08/13] dt-bindings: display: Document
>>>> dual-link LVDS display common properties
>>>>
>>>> On 10/28/2024, Liu Ying wrote:
>>>>> Dual-link LVDS displays receive odd pixels and even pixels
>>>>> separately from dual LVDS links. One link receives odd pixels and
>>>>> the other receives even pixels. Some of those displays may also use
>>>>> only one LVDS link to receive all pixels, being odd and even agnostic.
>>>>> Document common properties for those displays by extending LVDS
>>>>> display common properties defined in lvds.yaml.
>>>>>
>>>>> Suggested-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>>>>> Signed-off-by: Liu Ying <victor.liu@nxp.com>
>>>>> ---
>>>>> v4:
>>>>> * Squash change for advantech,idk-2121wr.yaml and
>>>>> panel-simple-lvds-dual-ports.yaml with lvds-dual-ports.yaml.
>>>>> (Rob)
>>>>> * Improve description in lvds-dual-ports.yaml. (Krzysztof)
>>>>>
>>>>> v3:
>>>>> * New patch. (Dmitry)
>>>>>
>>>>> .../bindings/display/lvds-dual-ports.yaml | 76 +++++++++++++++++++
>>>>> .../display/panel/advantech,idk-2121wr.yaml | 14 +---
>>>>> .../panel/panel-simple-lvds-dual-ports.yaml | 20 +----
>>>>> 3 files changed, 78 insertions(+), 32 deletions(-) create mode
>>>>> 100644
>>>>> Documentation/devicetree/bindings/display/lvds-dual-ports.yaml
>>>>>
>>>>> diff --git
>>>>> a/Documentation/devicetree/bindings/display/lvds-dual-ports.yaml
>>>>> b/Documentation/devicetree/bindings/display/lvds-dual-ports.yaml
>>>>> new file mode 100644
>>>>> index 000000000000..5f7a30640404
>>>>> --- /dev/null
>>>>> +++ b/Documentation/devicetree/bindings/display/lvds-dual-ports.yaml
>>>>> @@ -0,0 +1,76 @@
>>>>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) %YAML 1.2
>>>>> +---
>>>>> +$id: http://devicetree.org/schemas/display/lvds-dual-ports.yaml#
>>>>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>>>>> +
>>>>> +title: Dual-link LVDS Display Common Properties
>>>>> +
>>>>> +maintainers:
>>>>> + - Liu Ying <victor.liu@nxp.com>
>>>>> +
>>>>> +description: |
>>>>> + Common properties for LVDS displays with dual LVDS links. Extend
>>>>> +LVDS display
>>>>> + common properties defined in lvds.yaml.
>>>>> +
>>>>> + Dual-link LVDS displays receive odd pixels and even pixels
>>>>> + separately from the dual LVDS links. One link receives odd pixels
>>>>> + and the other receives even pixels. Some of those displays may
>>>>> + also use only one LVDS link to receive all pixels, being odd and even agnostic.
>>>>> +
>>>>> +allOf:
>>>>> + - $ref: lvds.yaml#
>>>>> +
>>>>> +properties:
>>>>> + ports:
>>>>> + $ref: /schemas/graph.yaml#/properties/ports
>>>>> +
>>>>> + properties:
>>>>> + port@0:
>>>>> + $ref: /schemas/graph.yaml#/$defs/port-base
>>>>> + unevaluatedProperties: false
>>>>> + description: the first LVDS input link
>>>>> +
>>>>> + properties:
>>>>> + dual-lvds-odd-pixels:
>>>>> + type: boolean
>>>>> + description: the first LVDS input link for odd pixels
>>>>> +
>>>>> + dual-lvds-even-pixels:
>>>>> + type: boolean
>>>>> + description: the first LVDS input link for even pixels
>>>>> +
>>>>> + oneOf:
>>>>> + - required: [dual-lvds-odd-pixels]
>>>>> + - required: [dual-lvds-even-pixels]
>>>>> + - properties:
>>>>> + dual-lvds-odd-pixels: false
>>>>> + dual-lvds-even-pixels: false
>>>>> +
>>>>> + port@1:
>>>>> + $ref: /schemas/graph.yaml#/$defs/port-base
>>>>> + unevaluatedProperties: false
>>>>> + description: the second LVDS input link
>>>>> +
>>>>> + properties:
>>>>> + dual-lvds-odd-pixels:
>>>>> + type: boolean
>>>>> + description: the second LVDS input link for odd pixels
>>>>> +
>>>>> + dual-lvds-even-pixels:
>>>>> + type: boolean
>>>>> + description: the second LVDS input link for even pixels
>>>>> +
>>>>> + oneOf:
>>>>> + - required: [dual-lvds-odd-pixels]
>>>>> + - required: [dual-lvds-even-pixels]
>>>>> + - properties:
>>>>> + dual-lvds-odd-pixels: false
>>>>> + dual-lvds-even-pixels: false
>>>>
>>>> Hmm, I should require port@0 or port@1.
>>>
>>> For dual LVDS, you need 3 ports as common use case
>>
>> For LVDS panels, only two ports for LVDS sink are needed.
>> For display bridges with LVDS sink, one additional output port is needed. However, I'm not sure if
>> this output port should be documented in this binding or not, because it doesn't look common enough
>> considering the LVDS panels.
>>
>>>
>>> 2 input ports and 1 outport and all are required properties.
>>
>> The output port cannot be required for LVDS panels at least.
>
> Ack.
>
>>
>> We need to require one or two input ports, because IT6263 may use one LVDS link or two.
>
> This patch is for generic dual link common cases and is not applicable for IT6263 single link case.
Based on previous discussion(especially Dmitry's suggestion),
this binding should cover display bridges that can use one
LVDS sink port or two LVDS sink ports, like IT6263. To be
clear, those bridges may have two modes(supported by one
chip) - single LVDS sink link mode and dual LVDS sink link
mode. Those bridges are considered as common dual-link
LVDS displays. That's why I was asked to extract the common
properties to this schema when adding IT6263 DT binding.
>
>
> Cheers,
> Biju
>
>>
>>>
>>> Cheers,
>>> Biju
>>>
>>>> Will wait a while for comments and add this in next version.
>>>>
>>>> --8<--
>>>> anyOf:
>>>> - required:
>>>> - port@0
>>>> - required:
>>>> - port@1
>>>> --8<--
>>>>
>>>>> +
>>>>> +required:
>>>>> + - ports
>>>>> +
>>>>> +additionalProperties: true
>>>>> +
>>>>> +...
>>>>
>>>> [...]
>>>>
>>>> --
>>>> Regards,
>>>> Liu Ying
>>>
>>
>> --
>> Regards,
>> Liu Ying
>
--
Regards,
Liu Ying
next prev parent reply other threads:[~2024-10-29 7:34 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 2:37 [PATCH v4 00/13] Add ITE IT6263 LVDS to HDMI converter support Liu Ying
2024-10-28 2:37 ` [PATCH v4 01/13] arm64: dts: imx8mp-skov-revb-mi1010ait-1cp1: Set "media_disp2_pix" clock rate to 70MHz Liu Ying
2024-10-28 2:37 ` [PATCH v4 02/13] drm/bridge: fsl-ldb: Get the next non-panel bridge Liu Ying
2024-10-28 2:37 ` [PATCH v4 03/13] drm/bridge: fsl-ldb: Use clk_round_rate() to validate "ldb" clock rate Liu Ying
2024-10-30 10:30 ` Maxime Ripard
2024-10-31 2:40 ` Liu Ying
2024-11-19 2:16 ` Liu Ying
2024-10-28 2:37 ` [PATCH v4 04/13] media: uapi: Add MEDIA_BUS_FMT_RGB101010_1X7X5_{SPWG, JEIDA} Liu Ying
2024-11-05 10:52 ` Sakari Ailus
2024-11-05 11:26 ` Dmitry Baryshkov
2024-10-28 2:37 ` [PATCH v4 05/13] drm: of: Get MEDIA_BUS_FMT_RGB101010_1X7X5_{JEIDA, SPWG} LVDS data mappings Liu Ying
2024-10-28 2:37 ` [PATCH v4 06/13] drm: of: Add drm_of_lvds_get_dual_link_pixel_order_sink() Liu Ying
2024-10-28 2:37 ` [PATCH v4 07/13] dt-bindings: display: lvds-data-mapping: Add 30-bit RGB pixel data mappings Liu Ying
2024-10-28 2:37 ` [PATCH v4 08/13] dt-bindings: display: Document dual-link LVDS display common properties Liu Ying
2024-10-29 6:16 ` Liu Ying
2024-10-29 6:58 ` Biju Das
2024-10-29 7:13 ` Liu Ying
2024-10-29 7:17 ` Biju Das
2024-10-29 7:35 ` Liu Ying [this message]
2024-10-29 7:48 ` Biju Das
2024-10-29 8:25 ` Liu Ying
2024-11-01 17:18 ` Rob Herring
2024-10-29 7:33 ` Biju Das
2024-10-29 8:01 ` Liu Ying
2024-10-29 8:51 ` Biju Das
2024-10-29 9:07 ` Liu Ying
2024-10-29 9:18 ` Biju Das
2024-10-28 2:37 ` [PATCH v4 09/13] dt-bindings: display: bridge: Add ITE IT6263 LVDS to HDMI converter Liu Ying
2024-10-28 8:07 ` Biju Das
2024-11-01 17:21 ` Rob Herring (Arm)
2024-10-28 2:37 ` [PATCH v4 10/13] drm/bridge: " Liu Ying
2024-10-28 8:09 ` Biju Das
2024-10-28 9:20 ` Dmitry Baryshkov
2024-10-28 2:37 ` [PATCH v4 11/13] arm64: dts: imx8mp-evk: Add NXP LVDS to HDMI adapter cards Liu Ying
2024-10-28 2:37 ` [PATCH v4 12/13] arm64: defconfig: Enable ITE IT6263 driver Liu Ying
2024-10-28 2:37 ` [PATCH v4 13/13] MAINTAINERS: Add maintainer for " Liu Ying
2024-10-28 9:21 ` Dmitry Baryshkov
2024-10-28 10:19 ` [PATCH v4 00/13] Add ITE IT6263 LVDS to HDMI converter support Dmitry Baryshkov
2024-10-28 11:12 ` Biju Das
2024-10-28 12:19 ` Dmitry Baryshkov
2024-10-29 2:41 ` Liu Ying
2024-10-30 3:16 ` Dmitry Baryshkov
2024-10-30 9:02 ` Biju Das
2024-10-31 18:20 ` Dmitry Baryshkov
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=a166da61-8cd4-44c9-987b-94d8a62faf82@nxp.com \
--to=victor.liu@nxp.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=arnd@arndb.de \
--cc=biju.das.jz@bp.renesas.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=geert+renesas@glider.be \
--cc=hverkuil@xs4all.nl \
--cc=imx@lists.linux.dev \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marex@denx.de \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=nfraprado@collabora.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=quic_bjorande@quicinc.com \
--cc=quic_jesszhan@quicinc.com \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sakari.ailus@linux.intel.com \
--cc=sam@ravnborg.org \
--cc=shawnguo@kernel.org \
--cc=simona@ffwll.ch \
--cc=thierry.reding@gmail.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tzimmermann@suse.de \
--cc=will@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