From: Krzysztof Kozlowski <krzk@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: Nick Hu <nick.hu@sifive.com>, Cyan Yang <cyan.yang@sifive.com>,
Samuel Holland <samuel.holland@sifive.com>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH] dt-bindings: power: Add SiFive Domain Management controllers
Date: Sat, 10 May 2025 16:57:44 +0200 [thread overview]
Message-ID: <c91d99c9-0ecb-4dcd-9beb-5a1e9fadc619@kernel.org> (raw)
In-Reply-To: <20250509-subtract-caramel-08d47ed3281c@spud>
On 09/05/2025 17:57, Conor Dooley wrote:
>>> + - pattern: "^sifive,[ts]mc1$"
>>> + - items:
>>> + - {}
>>> + - const: sifive,cmc3
>>> + - const: sifive,cmc2
>>> + - items:
>>> + - {}
>>> + - const: sifive,cmc2
>>
>> All of this is just unexpected. Why any compatible should come with
>> these?
>
> It's also not quite correct either, right? Or may not be correct at
> least. It permits "xxx", "tmc2", "smc1" and "xxx", "smc2", "tmc1"
> which mean that the smc and tmc must be identical in terms of
> programming model.
Yep
>
>> You need to use SoC specific compatibles.
>
> I think there's some slack to provide here, sifive are upstreaming it in
> advance of there being customers (or customers ready to upstream) and this
> format allows us to accept bindings/drivers and the customer will have
> to add a soc-specific compatible in order to actually use these in a
> dts. I think it's better to accept something along these lines than
Sure, commit msg should explain that and probably these {} wildcards
should have comment as well.
> stall out until a customer decides to upstream their user. That said, I
> would expect this to come (as you mentioned above) with the driver.
>
Best regards,
Krzysztof
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-05-10 14:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 2:16 [PATCH] dt-bindings: power: Add SiFive Domain Management controllers Nick Hu
2025-05-09 6:40 ` Krzysztof Kozlowski
2025-05-09 15:57 ` Conor Dooley
2025-05-10 14:57 ` Krzysztof Kozlowski [this message]
2025-05-12 3:28 ` Nick Hu
2025-05-12 3:26 ` Nick Hu
2025-05-12 3:20 ` Nick Hu
2025-05-12 10:39 ` Krzysztof Kozlowski
2025-05-12 11:00 ` Conor Dooley
2025-05-28 3:15 ` Nick Hu
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=c91d99c9-0ecb-4dcd-9beb-5a1e9fadc619@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=cyan.yang@sifive.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nick.hu@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.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