From: "Michael Walle" <mwalle@kernel.org>
To: "Krzysztof Kozlowski" <krzk@kernel.org>, "Swamil Jain" <s-jain1@ti.com>
Cc: <jyri.sarha@iki.fi>, <tomi.valkeinen@ideasonboard.com>,
<airlied@gmail.com>, <simona@ffwll.ch>,
<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<tzimmermann@suse.de>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>, <aradhya.bhatia@linux.dev>,
<dri-devel@lists.freedesktop.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <devarsht@ti.com>,
<praneeth@ti.com>, <h-shenoy@ti.com>, <u-kumar1@ti.com>
Subject: Re: [PATCH v3 1/3] dt-bindings: display: ti,am65x-dss: Add am62p dss compatible
Date: Wed, 14 Jan 2026 11:41:47 +0100 [thread overview]
Message-ID: <DFO8ZDZM41FK.28NIFO8J4E74C@kernel.org> (raw)
In-Reply-To: <20260108-expert-whippet-of-downpour-ba277f@quoll>
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 297 bytes --]
next prev parent reply other threads:[~2026-01-14 10:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 17:45 [PATCH v3 0/3] Add Display support for AM62P SoC Swamil Jain
2026-01-07 17:45 ` [PATCH v3 1/3] dt-bindings: display: ti,am65x-dss: Add am62p dss compatible Swamil Jain
2026-01-08 8:51 ` Krzysztof Kozlowski
2026-01-14 10:41 ` Michael Walle [this message]
2026-01-16 10:08 ` Swamil Jain
2026-01-15 16:54 ` Swamil Jain
2026-01-16 10:25 ` Krzysztof Kozlowski
2026-01-07 17:45 ` [PATCH v3 2/3] drm/tidss: Power up attached PM domains on probe Swamil Jain
2026-01-09 14:18 ` Tomi Valkeinen
2026-01-15 19:55 ` Swamil Jain
2026-01-14 10:25 ` Michael Walle
2026-01-07 17:45 ` [PATCH v3 3/3] drm: tidss: tidss_drv: Add support for AM62P display subsystem Swamil Jain
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=DFO8ZDZM41FK.28NIFO8J4E74C@kernel.org \
--to=mwalle@kernel.org \
--cc=airlied@gmail.com \
--cc=aradhya.bhatia@linux.dev \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=h-shenoy@ti.com \
--cc=jyri.sarha@iki.fi \
--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=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=s-jain1@ti.com \
--cc=simona@ffwll.ch \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tzimmermann@suse.de \
--cc=u-kumar1@ti.com \
/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