[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <491560f1-ee50-43ef-b258-adb5859cb05a@kernel.org>
Date: Mon, 1 Dec 2025 09:39:09 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Chaoyi Chen <chaoyi.chen@...k-chips.com>, Chaoyi Chen
<kernel@...kyi.com>, Joerg Roedel <joro@...tes.org>,
Will Deacon <will@...nel.org>, Robin Murphy <robin.murphy@....com>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Heiko Stuebner <heiko@...ech.de>
Cc: iommu@...ts.linux.dev, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-rockchip@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: iommu: rockchip: Add support for
multiple interface clocks
On 01/12/2025 09:10, Chaoyi Chen wrote:
>>> + - if:
>>> + properties:
>>> + compatible:
>>> + items:
>>> + - const: rockchip,iommu
>>> + - const: rockchip,rk3568-iommu
>>> + then:
>>> + properties:
>>> + clocks:
>>> + maxItems: 2
>>
>> Why this is unspecific now? Please look at other examples how it is
>> done, e.g. Samsung clocks.
>
> I looked at some examples. Maybe it need to set both minItems and
> maxItems here? I'm not sure I understood your point.
Individual items were described before. Now they are not, so first item
can be anything.
You need to define the list. If the devices have completely different
clocks, then you would go with Samsung approach. But devices should not
have completely different clocks, so you should define common parts in
top-level and just narrow number of items here. maxItems is enough in
such case.
Best regards,
Krzysztof
Powered by blists - more mailing lists