From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wadim Egorov <w.egorov@phytec.de>,
andrzej.hajda@intel.com, neil.armstrong@linaro.org,
rfoss@kernel.org
Cc: Laurent.pinchart@ideasonboard.com, jonas@kwiboo.se,
jernej.skrabec@gmail.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
simona@ffwll.ch, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
bbrezillon@kernel.org, conor+dt@kernel.org, krzk+dt@kernel.org,
robh@kernel.org, upstream@lists.phytec.de
Subject: Re: [PATCH 2/2] dt-bindings: display: bridge: sil,sii9022: Add data-lines
Date: Thu, 3 Oct 2024 15:26:31 +0200 [thread overview]
Message-ID: <ca913f6a-c028-456d-9f9f-0c3183d8a921@kernel.org> (raw)
In-Reply-To: <d28be8e9-b235-43e0-aaed-dd65a87c5797@phytec.de>
On 03/10/2024 13:56, Wadim Egorov wrote:
>
>
> Am 03.10.24 um 12:03 schrieb Krzysztof Kozlowski:
>> On 03/10/2024 10:20, Wadim Egorov wrote:
>>> The SI9022 HDMI transmitter can be configured with 16, 18, or 24 input
>>> data lines. This commit introduces the data-lines property to the input
>>
>> lines? lanes? What are lines? like pins?
>
> Yes, "lines" in this context refers to the number of pins used for the
> input pixel data bus, which can support 16, 18, or 24-bit wide data
> buses. These are parallel data lines (or pins) that carry uncompressed
> digital video to the HDMI transmitter.
>
>>
>>> endpoint, specifying the number of parallel RGB input pins connected
>>> to the transmitter.
>>>
>>> Signed-off-by: Wadim Egorov <w.egorov@phytec.de>
>>> ---
>>> .../bindings/display/bridge/sil,sii9022.yaml | 13 ++++++++++++-
>>> 1 file changed, 12 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/Documentation/devicetree/bindings/display/bridge/sil,sii9022.yaml b/Documentation/devicetree/bindings/display/bridge/sil,sii9022.yaml
>>> index 5a69547ad3d7..24306f8eb107 100644
>>> --- a/Documentation/devicetree/bindings/display/bridge/sil,sii9022.yaml
>>> +++ b/Documentation/devicetree/bindings/display/bridge/sil,sii9022.yaml
>>> @@ -81,9 +81,20 @@ properties:
>>>
>>> properties:
>>> port@0:
>>> - $ref: /schemas/graph.yaml#/properties/port
>>> + unevaluatedProperties: false
>>> + $ref: /schemas/graph.yaml#/$defs/port-base
>>> description: Parallel RGB input port
>>>
>>> + properties:
>>> + endpoint:
>>> + $ref: /schemas/graph.yaml#/$defs/endpoint-base
>>> + unevaluatedProperties: false
>>> +
>>> + properties:
>>> + data-lines:
>>
>> No, this will confuse everyone. Considering lack of description how
>> anyone would figure out what this means?
>
> I guess from working with the hardware/reference manual and using this chip?
>
> I don't think it is overly confusing, especially since the port is
> already described as the "Parallel RGB input port" which clearly implies
> the use of pins for data transmission.
I am surprised you do not find data-lanes and data-lines confusing. For
non-native English speakers this even might sound the same.
You used earlier pins and bits, so maybe it's the same as bus-width,
which is already used all over the bindings, including one of the bridges.
Anyway a generic property should go to video-interfaces.
>
> I am open to other suggestions if you believe a different name would
> improve clarity.
>
> Btw, bridge/toshiba,tc358768.yaml, which performs a similar function,
> also uses the term data-lines.
Then this has to go to common schema.
Oh, wait, video-interfaces already have it!
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-03 13:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 8:20 [PATCH 1/2] drm/bridge: sii902x: Provide data-lines property to input endpoint Wadim Egorov
2024-10-03 8:20 ` [PATCH 2/2] dt-bindings: display: bridge: sil,sii9022: Add data-lines Wadim Egorov
2024-10-03 10:03 ` Krzysztof Kozlowski
2024-10-03 11:56 ` Wadim Egorov
2024-10-03 13:26 ` Krzysztof Kozlowski [this message]
2024-10-04 5:38 ` Wadim Egorov
2024-10-03 9:43 ` [PATCH 1/2] drm/bridge: sii902x: Provide data-lines property to input endpoint Aradhya Bhatia
2024-10-04 6:19 ` Aradhya Bhatia
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=ca913f6a-c028-456d-9f9f-0c3183d8a921@kernel.org \
--to=krzk@kernel.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=bbrezillon@kernel.org \
--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=krzk+dt@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=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=upstream@lists.phytec.de \
--cc=w.egorov@phytec.de \
/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;
as well as URLs for NNTP newsgroup(s).