From: Liu Ying <victor.liu@nxp.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, 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, maarten.lankhorst@linux.intel.com,
tzimmermann@suse.de, airlied@gmail.com, simona@ffwll.ch
Subject: Re: [PATCH 3/5] dt-bindings: display: simple-bridge: Document DPI color encoder
Date: Thu, 6 Mar 2025 13:49:05 +0800 [thread overview]
Message-ID: <b6320f0b-8605-455f-b834-57a8bdaf3f91@nxp.com> (raw)
In-Reply-To: <20250304-wandering-tangible-doberman-5b6dd0@houat>
On 03/04/2025, Maxime Ripard wrote:
> On Tue, Mar 04, 2025 at 06:15:28PM +0800, Liu Ying wrote:
>> A DPI color encoder, as a simple display bridge, converts input DPI color
>> coding to output DPI color coding, like Adafruit Kippah DPI hat[1] which
>> converts input 18-bit pixel data to 24-bit pixel data(with 2 low padding
>> bits in every color component though). Document the DPI color encoder.
>>
>> [1] https://learn.adafruit.com/adafruit-dpi-display-kippah-ttl-tft/downloads
>>
>> Signed-off-by: Liu Ying <victor.liu@nxp.com>
>
> So it's just a bunch of signals that aren't wired / set to the ground? I
> assume to free a few GPIOs?
Yes. Freed pins could work as GPIOs or other functions.
>
> I guess that makes sense.
>
>> ---
>> .../display/bridge/simple-bridge.yaml | 89 ++++++++++++++++++-
>> 1 file changed, 87 insertions(+), 2 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/display/bridge/simple-bridge.yaml b/Documentation/devicetree/bindings/display/bridge/simple-bridge.yaml
>> index 43cf4df9811a..c1747c033040 100644
>> --- a/Documentation/devicetree/bindings/display/bridge/simple-bridge.yaml
>> +++ b/Documentation/devicetree/bindings/display/bridge/simple-bridge.yaml
>> @@ -27,6 +27,7 @@ properties:
>> - const: adi,adv7123
>> - enum:
>> - adi,adv7123
>> + - dpi-color-encoder
>
> I don't think we can claim that there's a generic DPI color encoder.
> Maybe we can add the prefix dumb or transparent?
TBH, I don't have a best compatible string and open to suggestions.
"dpi-color-encoder" came up to my mind just because the MIPI DPI standard
documentation mentions *color coding* and this bridge changes the coding,
hence *encoder*.
If folks think "dumb-dpi-color-encoder" or "transparent-dpi-color-encoder"
are good enough, I'd use it. Just let me know which one to use.
>
>> - dumb-vga-dac
>> - ti,opa362
>> - ti,ths8134
>> @@ -37,13 +38,31 @@ properties:
>>
>> properties:
>> port@0:
>> - $ref: /schemas/graph.yaml#/properties/port
>> + $ref: /schemas/graph.yaml#/$defs/port-base
>> + unevaluatedProperties: false
>> description: The bridge input
>>
>> + properties:
>> + endpoint:
>> + $ref: /schemas/media/video-interfaces.yaml#
>> + unevaluatedProperties: false
>> +
>> + properties:
>> + dpi-color-coding: true
>> +
>> port@1:
>> - $ref: /schemas/graph.yaml#/properties/port
>> + $ref: /schemas/graph.yaml#/$defs/port-base
>> + unevaluatedProperties: false
>> description: The bridge output
>>
>> + properties:
>> + endpoint:
>> + $ref: /schemas/media/video-interfaces.yaml#
>> + unevaluatedProperties: false
>> +
>> + properties:
>> + dpi-color-coding: true
>> +
>> required:
>> - port@0
>> - port@1
>> @@ -61,6 +80,44 @@ required:
>>
>> additionalProperties: false
>>
>> +allOf:
>> + - $ref: /schemas/display/dpi-color-coding.yaml#
>> + - if:
>> + properties:
>> + compatible:
>> + contains:
>> + const: dpi-color-encoder
>> + then:
>> + properties:
>> + ports:
>> + properties:
>> + port@0:
>> + properties:
>> + endpoint:
>> + required:
>> + - dpi-color-coding
>> +
>> + port@1:
>> + properties:
>> + endpoint:
>> + required:
>> + - dpi-color-coding
>> + else:
>> + properties:
>> + ports:
>> + properties:
>> + port@0:
>> + properties:
>> + endpoint:
>> + properties:
>> + dpi-color-coding: false
>> +
>> + port@1:
>> + properties:
>> + endpoint:
>> + properties:
>> + dpi-color-coding: false
>> +
>
> Also it complicates the binding enough to warrant for another binding for
> that specific "component".
Do you suggest to write a separate/new DT binding for this bridge?
>
>> examples:
>> - |
>> bridge {
>> @@ -88,4 +145,32 @@ examples:
>> };
>> };
>>
>> + - |
>> + bridge {
>> + compatible = "dpi-color-enoder";
>
> You have a typo in the compatible.
Hmm, good catch! I did upgrade dtschema to version 2025.2 with pip3 and
didn't see any warnings/errors reported by dt_binding_check, weird...
>
> Maxime
--
Regards,
Liu Ying
next prev parent reply other threads:[~2025-03-06 5:47 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 10:15 [PATCH 0/5] drm/bridge: simple-bridge: Add DPI color encoder support Liu Ying
2025-03-04 10:15 ` [PATCH 1/5] dt-bindings: display: Document DPI color codings Liu Ying
2025-03-04 10:33 ` Maxime Ripard
2025-03-05 7:51 ` Krzysztof Kozlowski
2025-03-05 8:26 ` Maxime Ripard
2025-03-05 12:16 ` Krzysztof Kozlowski
2025-03-06 7:13 ` Liu Ying
2025-03-04 10:15 ` [PATCH 2/5] drm/of: Add drm_of_dpi_get_color_coding() Liu Ying
2025-03-04 10:15 ` [PATCH 3/5] dt-bindings: display: simple-bridge: Document DPI color encoder Liu Ying
2025-03-04 10:38 ` Maxime Ripard
2025-03-06 5:49 ` Liu Ying [this message]
2025-03-04 11:27 ` Rob Herring (Arm)
2025-03-04 15:23 ` Rob Herring
2025-03-05 9:35 ` Alexander Stein
2025-03-05 16:38 ` Rob Herring
2025-03-06 7:02 ` Liu Ying
2025-03-06 11:35 ` Maxime Ripard
2025-03-06 20:34 ` Rob Herring
2025-03-07 3:25 ` Liu Ying
2025-03-10 9:53 ` Maxime Ripard
2025-03-11 2:29 ` Liu Ying
2025-03-11 7:44 ` Maxime Ripard
2025-03-07 3:10 ` Liu Ying
2025-03-10 9:44 ` Maxime Ripard
2025-03-11 2:38 ` Liu Ying
2025-03-11 7:52 ` Maxime Ripard
2025-03-04 10:15 ` [PATCH 4/5] drm/bridge: simple-bridge: Add DPI color encoder support Liu Ying
2025-03-04 10:40 ` Maxime Ripard
2025-03-06 5:57 ` Liu Ying
2025-03-04 10:15 ` [PATCH 5/5] drm/bridge: simple-bridge: Add next panel support Liu Ying
2025-03-04 10:41 ` Maxime Ripard
2025-03-06 6:17 ` Liu Ying
2025-03-04 15:00 ` [PATCH 0/5] drm/bridge: simple-bridge: Add DPI color encoder support Alexander Stein
2026-01-12 9:31 ` Francesco Dolcini
2026-01-12 9:44 ` Liu Ying
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=b6320f0b-8605-455f-b834-57a8bdaf3f91@nxp.com \
--to=victor.liu@nxp.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--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 \
/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
all inboxes | Powered by JetHome®