From: Mike Looijmans <mike.looijmans@topic.nl>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: dri-devel@lists.freedesktop.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
Conor Dooley <conor+dt@kernel.org>,
David Airlie <airlied@gmail.com>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Jonas Karlman <jonas@kwiboo.se>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Rob Herring <robh@kernel.org>, Robert Foss <rfoss@kernel.org>,
Simona Vetter <simona@ffwll.ch>,
Thomas Zimmermann <tzimmermann@suse.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: drm/bridge: ti-tmds181: Add TI TMDS181 and SN65DP159 bindings
Date: Tue, 2 Sep 2025 16:52:48 +0200 [thread overview]
Message-ID: <dc073509-57d9-4b57-a53f-cd285bff8eae@topic.nl> (raw)
In-Reply-To: <fccbba0a-cb8f-4d71-9c91-7558cfaa8ef7@topic.nl>
On 9/2/25 16:41, Mike Looijmans wrote:
> On 9/2/25 15:46, Krzysztof Kozlowski wrote:
>> On 02/09/2025 10:46, Mike Looijmans wrote:
>>>>> + endpoint:
>>>>> + $ref: /schemas/media/video-interfaces.yaml#
>>>>> + unevaluatedProperties: false
>>>>> +
>>>>> + port@1:
>>>>> + $ref: /schemas/graph.yaml#/$defs/port-base
>>>>> + unevaluatedProperties: false
>>>>> + description: Video port for HDMI output (panel or bridge)
>>>>> +
>>>>> + properties:
>>>>> + endpoint:
>>>>> + $ref: /schemas/media/video-interfaces.yaml#
>>>>> + unevaluatedProperties: false
>>>>> +
>>>>> + required:
>>>>> + - port@0
>>>>> + - port@1
>>>>> +
>>>>> + ti,source-mode:
>>>>> + type: boolean
>>>>> + description:
>>>>> + Force chip to operate in "source" mode. Allows to use
>>>>> + a TMDS181 chip (which defaults to sink) as cable driver.
>>>>> +
>>>>> + ti,sink-mode:
>>>> Aren't these two mutually exclusive? Can same device operate in source
>>>> and in sink mode simultaneously?
>>> They're exclusive, yes. Will add that.
>> Then either define constraints per variant in if:then: or maybe better
>> use string enum. Not sure what applies where, so tricky to say which
>> choice is better.
>>
>> Best regards,
>> Krzysztof
>
> Since there's already going to be an "if" block, it simplifies parsing
> to keep the booleans. My first attempt was this, but that doesn't work
> as I'd expect. Adding "slew-rate" to the example dts results in an
> error, so apparently the "if" block doesn't do what I think it would
> and I haven't figured out yet what the correct syntax must be:
>
> if:
> properties:
> compatible:
> contains:
> const: ti,sn65dp159
> then:
> properties:
> ti,sink-mode:
> type: boolean
> description:
> Force chip to operate in "sink" mode. Allows to use
> a DP159 chip (defaults to source) for incoming signals.
> ti,dvi-mode:
> type: boolean
> description: Makes the DP159 chip operate in DVI mode.
> slew-rate:
> $ref: /schemas/types.yaml#/definitions/uint32
> minimum: 0
> maximum: 3
> default: 3
> description: Set slew rate, 0 is slowest, 3 is fastest.
> else:
> properties:
> ti,source-mode:
> type: boolean
> description:
> Force chip to operate in "source" mode. Allows to use
> a TMDS181 chip (which defaults to sink) as cable driver.
>
Hmm, apparently one cannot "add" properties in the "if:" block? The
opposite approach, disallowing properties, works, e.g.:
if:
properties:
compatible:
contains:
const: ti,sn65dp159
then:
properties:
ti,source-mode: false
else:
properties:
ti,sink-mode: false
ti,dvi-mode: false
slew-rate: false
This produces the wanted behavior, though it looks counter-intuitive to me.
--
Mike Looijmans
next prev parent reply other threads:[~2025-09-02 14:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.d6331613-729b-4f92-9c2d-d2abe6df38d5@emailsignatures365.codetwo.com>
2025-09-01 14:29 ` [PATCH v4 0/2] drm: bridge: Add TI tmds181 and sn65dp159 driver Mike Looijmans
[not found] ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.edc18686-244f-441e-a6ac-0b62492b96c8@emailsignatures365.codetwo.com>
2025-09-01 14:29 ` [PATCH v4 1/2] dt-bindings: drm/bridge: ti-tmds181: Add TI TMDS181 and SN65DP159 bindings Mike Looijmans
2025-09-02 6:53 ` Krzysztof Kozlowski
2025-09-02 8:46 ` Mike Looijmans
2025-09-02 13:46 ` Krzysztof Kozlowski
2025-09-02 14:41 ` Mike Looijmans
2025-09-02 14:52 ` Mike Looijmans [this message]
2025-09-02 15:32 ` Krzysztof Kozlowski
2025-09-02 17:29 ` Maxime Ripard
2025-09-03 6:17 ` Mike Looijmans
2025-09-03 11:12 ` Mike Looijmans
2025-09-03 15:25 ` Dmitry Baryshkov
2025-09-04 5:54 ` Mike Looijmans
[not found] ` <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.cb04edf6-4f97-4f30-891a-5e11da8a5e1f@emailsignatures365.codetwo.com>
2025-09-01 14:29 ` [PATCH v4 2/2] drm: bridge: Add TI tmds181 and sn65dp159 driver Mike Looijmans
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=dc073509-57d9-4b57-a53f-cd285bff8eae@topic.nl \
--to=mike.looijmans@topic.nl \
--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=krzk@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;
as well as URLs for NNTP newsgroup(s).