[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <DFO8ZDZM41FK.28NIFO8J4E74C@kernel.org>
Date: Wed, 14 Jan 2026 11:41:47 +0100
From: "Michael Walle" <mwalle@...nel.org>
To: "Krzysztof Kozlowski" <krzk@...nel.org>, "Swamil Jain" <s-jain1@...com>
Cc: <jyri.sarha@....fi>, <tomi.valkeinen@...asonboard.com>,
<airlied@...il.com>, <simona@...ll.ch>,
<maarten.lankhorst@...ux.intel.com>, <mripard@...nel.org>,
<tzimmermann@...e.de>, <robh@...nel.org>, <krzk+dt@...nel.org>,
<conor+dt@...nel.org>, <aradhya.bhatia@...ux.dev>,
<dri-devel@...ts.freedesktop.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <devarsht@...com>, <praneeth@...com>,
<h-shenoy@...com>, <u-kumar1@...com>
Subject: Re: [PATCH v3 1/3] dt-bindings: display: ti,am65x-dss: Add am62p
dss compatible
Hi,
On Thu Jan 8, 2026 at 9:51 AM CET, Krzysztof Kozlowski wrote:
>> + - if:
>> + properties:
>> + compatible:
>> + contains:
>> + const: ti,am62p-dss
>> + then:
>> + properties:
>> + power-domains:
>> + minItems: 1
>> + maxItems: 3
>
> This is still not constrained enough. You need to define the items
> instead. I still do not understand why number of power domains is
> flexible.
So looking at the downstream devicetree, there is one power domain
for each OLDI and for the DSS itself. Thus, in the am62p case, there
are two DSS as described above, so DSS0 has a power domain for dss0
and two power domains for the OLDI transmitters. The same for dss1
but with just one OLDI transmitter.
So I don't know why there is minItems: 1 because it's either 2 or 3.
What about the following:
..
- if:
properties:
compatible:
contains:
const: ti,am62p-dss
then:
properties:
power-domains:
minItems: 2
items:
- description: DSS controller
- description: OLDI0 transmitter
- description: OLDI1 transmitter
else:
properties:
power-domains:
maxItems: 1
-michael
Download attachment "signature.asc" of type "application/pgp-signature" (298 bytes)
Powered by blists - more mailing lists