From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Chaoyi Chen <kernel@airkyi.com>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: iommu@lists.linux.dev, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: iommu: rockchip: Add support for multiple interface clocks
Date: Mon, 1 Dec 2025 16:10:29 +0800 [thread overview]
Message-ID: <98a847f7-0880-4e5b-a946-26dc81fde5d2@rock-chips.com> (raw)
In-Reply-To: <96958186-0e46-4606-ae36-239112eb31ea@kernel.org>
Hi Krzysztof,
On 12/1/2025 3:55 PM, Krzysztof Kozlowski wrote:
> On 28/11/2025 08:13, Chaoyi Chen wrote:
>> From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
>>
>> The iommu found on RK3576 NPU and RK3576 RKVDEC have 4 clock instead of
>> 2 clock. Their clock names might differ, but I don't think that matters
>> much.
>>
>> Add support for them.
>>
>> Signed-off-by: Chaoyi Chen <chaoyi.chen@rock-chips.com>
>> ---
>>
>> Changes in v2:
>> - Rewrite dt binding.
>>
>> .../bindings/iommu/rockchip,iommu.yaml | 52 ++++++++++++++++---
>> 1 file changed, 46 insertions(+), 6 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/iommu/rockchip,iommu.yaml b/Documentation/devicetree/bindings/iommu/rockchip,iommu.yaml
>> index 6ce41d11ff5e..dfa5e25476d9 100644
>> --- a/Documentation/devicetree/bindings/iommu/rockchip,iommu.yaml
>> +++ b/Documentation/devicetree/bindings/iommu/rockchip,iommu.yaml
>> @@ -27,6 +27,8 @@ properties:
>> - enum:
>> - rockchip,rk3576-iommu
>> - rockchip,rk3588-iommu
>> + - rockchip,rk3576-npu-iommu
>> + - rockchip,rk3576-rkvdec-iommu
>> - const: rockchip,rk3568-iommu
>>
>> reg:
>> @@ -42,14 +44,12 @@ properties:
>> minItems: 1
>>
>> clocks:
>> - items:
>> - - description: Core clock
>> - - description: Interface clock
>
> These go to specific variant if:then.
>
>> + minItems: 2
>> + maxItems: 4
>>
>> clock-names:
>> - items:
>> - - const: aclk
>> - - const: iface
>> + minItems: 2
>> + maxItems: 4
>
> So you just allow any names, like pink-pony.
>
> No, define common list here. Actually same for clocks.
Will fix in v3.
>
>>
>> "#iommu-cells":
>> const: 0
>> @@ -64,6 +64,46 @@ properties:
>> Some mmu instances may produce unexpected results
>> when the reset operation is used.
>>
>> +allOf:
>> + - if:
>> + properties:
>> + compatible:
>> + contains:
>> + enum:
>> + - rockchip,rk3576-npu-iommu
>> + - rockchip,rk3576-rkvdec-iommu
>> + then:
>> + properties:
>> + clocks:
>> + minItems: 4
>> + clock-names:
>> + minItems: 4
>> + - 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.
>
>
> Best regards,
> Krzysztof
>
>
--
Best,
Chaoyi
next prev parent reply other threads:[~2025-12-01 8:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 7:13 [PATCH v2 0/2] iommu/rockchip: " Chaoyi Chen
2025-11-28 7:13 ` [PATCH v2 1/2] dt-bindings: iommu: rockchip: " Chaoyi Chen
2025-11-28 8:18 ` Rob Herring (Arm)
2025-12-01 7:55 ` Krzysztof Kozlowski
2025-12-01 8:10 ` Chaoyi Chen [this message]
2025-12-01 8:39 ` Krzysztof Kozlowski
2025-12-01 8:54 ` Chaoyi Chen
2025-11-28 7:13 ` [PATCH v2 2/2] iommu/rockchip: Use devm_clk_bulk_get_all() to get multiple iface clock Chaoyi Chen
2025-11-28 7:31 ` Shawn Lin
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=98a847f7-0880-4e5b-a946-26dc81fde5d2@rock-chips.com \
--to=chaoyi.chen@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kernel@airkyi.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
/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®