From: Krzysztof Kozlowski <krzk@kernel.org>
To: Joshua Yeong <joshua.yeong@starfivetech.com>,
Mark Brown <broonie@kernel.org>
Cc: "lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"rahul@summations.net" <rahul@summations.net>,
"anup@brainfault.org" <anup@brainfault.org>,
"lftan.linux@gmail.com" <lftan.linux@gmail.com>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"pjw@kernel.org" <pjw@kernel.org>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
"alex@ghiti.fr" <alex@ghiti.fr>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] dt-bindings: regulator: Add RPMI voltage service bindings
Date: Fri, 25 Sep 2026 08:07:40 +0200 [thread overview]
Message-ID: <0db3ed29-8bb8-4dc3-a4cb-cc5b9bf2e893@kernel.org> (raw)
In-Reply-To: <SH0PR01MB08411AA7F403A71D2D7470A6F9802@SH0PR01MB0841.CHNPR01.prod.partner.outlook.cn>
On 25/09/2026 04:21, Joshua Yeong wrote:
> On Thu, Sep 24, 2026 at 10:00:06PM +0100, Mark Brown <broonie@kernel.org> wrote:
>> On Wed, Sep 23, 2026 at 10:35:08PM +0200, Krzysztof Kozlowski wrote:
>>> On 23/09/2026 09:00, Joshua Yeong wrote:
>>
>>>> + voltage-service {
>>
>>> There is no such service. Don't invent names. See DT spec.
>>
>> Looks like it comes from the RPMI spec:
>>
>>
>> https://github.com/riscv-non-isa/riscv-rpmi/blob/main/src/srvgrp-volta
>> ge.adoc
>>
>>>> + "#voltage-domain-cells" on the provider, a consumer lists
>>>> + "voltage-domains = <&provider DOMAIN_ID>" and names each entry
>>>> + in "voltage-domain-names", the way it names a voltage power
>>>> + domain. Both properties belong to the consumer, so a consumer
>>>> + binding describes them
>>>> + itself:
>>
>>> And where do you explain what is that "voltage domain" and why it is
>>> completely different than everything else we have?
>>
>>> No, don't come up with your own naming for standard things.
>>
>> That also looks like what the spec says (some of the description is
>> copied pretty closely from the spec).
>
> The RPMI specification uses the word voltage instead of 'regulator' in the
> kernel here. We need something like power-domain-cells,
> performance-domain-cells or clock-cells that isn't supported by regulator
> framework. While I have no prior history on the regulator framework but
> the RPMI voltage service drivers trying to upstream here need some
> mechanism to map just the domain id to the RPMI services.
>
> The driver would still work with the existing voltage device tree structure.
> I understand other drivers may not use voltage-domain like RPMI
> voltage service, so I only add the support for this on the RPMI
> voltage driver and not on the framework side.
As discussed on IRC #devicetree, that's either power-domains or
regulator supplies. If you need anything else, you need to explain. Not we.
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Joshua Yeong <joshua.yeong@starfivetech.com>,
Mark Brown <broonie@kernel.org>
Cc: "lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"rahul@summations.net" <rahul@summations.net>,
"anup@brainfault.org" <anup@brainfault.org>,
"lftan.linux@gmail.com" <lftan.linux@gmail.com>,
"robh@kernel.org" <robh@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"pjw@kernel.org" <pjw@kernel.org>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
"alex@ghiti.fr" <alex@ghiti.fr>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] dt-bindings: regulator: Add RPMI voltage service bindings
Date: Fri, 25 Sep 2026 08:07:40 +0200 [thread overview]
Message-ID: <0db3ed29-8bb8-4dc3-a4cb-cc5b9bf2e893@kernel.org> (raw)
In-Reply-To: <SH0PR01MB08411AA7F403A71D2D7470A6F9802@SH0PR01MB0841.CHNPR01.prod.partner.outlook.cn>
On 25/09/2026 04:21, Joshua Yeong wrote:
> On Thu, Sep 24, 2026 at 10:00:06PM +0100, Mark Brown <broonie@kernel.org> wrote:
>> On Wed, Sep 23, 2026 at 10:35:08PM +0200, Krzysztof Kozlowski wrote:
>>> On 23/09/2026 09:00, Joshua Yeong wrote:
>>
>>>> + voltage-service {
>>
>>> There is no such service. Don't invent names. See DT spec.
>>
>> Looks like it comes from the RPMI spec:
>>
>>
>> https://github.com/riscv-non-isa/riscv-rpmi/blob/main/src/srvgrp-volta
>> ge.adoc
>>
>>>> + "#voltage-domain-cells" on the provider, a consumer lists
>>>> + "voltage-domains = <&provider DOMAIN_ID>" and names each entry
>>>> + in "voltage-domain-names", the way it names a voltage power
>>>> + domain. Both properties belong to the consumer, so a consumer
>>>> + binding describes them
>>>> + itself:
>>
>>> And where do you explain what is that "voltage domain" and why it is
>>> completely different than everything else we have?
>>
>>> No, don't come up with your own naming for standard things.
>>
>> That also looks like what the spec says (some of the description is
>> copied pretty closely from the spec).
>
> The RPMI specification uses the word voltage instead of 'regulator' in the
> kernel here. We need something like power-domain-cells,
> performance-domain-cells or clock-cells that isn't supported by regulator
> framework. While I have no prior history on the regulator framework but
> the RPMI voltage service drivers trying to upstream here need some
> mechanism to map just the domain id to the RPMI services.
>
> The driver would still work with the existing voltage device tree structure.
> I understand other drivers may not use voltage-domain like RPMI
> voltage service, so I only add the support for this on the RPMI
> voltage driver and not on the framework side.
As discussed on IRC #devicetree, that's either power-domains or
regulator supplies. If you need anything else, you need to explain. Not we.
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:[~2026-09-25 6:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 7:00 [PATCH v2 0/3] Add RISC-V RPMI voltage service support Joshua Yeong
2026-09-23 7:00 ` Joshua Yeong
2026-09-23 7:00 ` [PATCH v2 1/3] dt-bindings: regulator: Add RPMI voltage service bindings Joshua Yeong
2026-09-23 7:00 ` Joshua Yeong
2026-09-23 7:25 ` sashiko-bot
2026-09-23 20:35 ` Krzysztof Kozlowski
2026-09-23 20:35 ` Krzysztof Kozlowski
2026-09-24 21:00 ` Mark Brown
2026-09-24 21:00 ` Mark Brown
2026-09-25 2:21 ` Joshua Yeong
2026-09-25 2:21 ` Joshua Yeong
2026-09-25 6:07 ` Krzysztof Kozlowski [this message]
2026-09-25 6:07 ` Krzysztof Kozlowski
2026-09-25 7:14 ` Joshua Yeong
2026-09-25 7:14 ` Joshua Yeong
2026-09-25 15:18 ` Krzysztof Kozlowski
2026-09-25 15:18 ` Krzysztof Kozlowski
2026-09-25 17:15 ` Mark Brown
2026-09-25 17:15 ` Mark Brown
2026-09-26 21:21 ` Conor Dooley
2026-09-26 21:21 ` Conor Dooley
2026-09-27 6:37 ` Joshua Yeong
2026-09-27 6:37 ` Joshua Yeong
2026-09-25 17:20 ` Mark Brown
2026-09-25 17:20 ` Mark Brown
2026-09-25 6:11 ` Krzysztof Kozlowski
2026-09-25 6:11 ` Krzysztof Kozlowski
2026-09-25 17:25 ` Mark Brown
2026-09-25 17:25 ` Mark Brown
2026-09-23 7:00 ` [PATCH v2 2/3] regulator: Add RPMI voltage service Joshua Yeong
2026-09-23 7:00 ` Joshua Yeong
2026-09-23 7:29 ` sashiko-bot
2026-09-23 7:00 ` [PATCH v2 3/3] MAINTAINERS: Add RISC-V RPMI voltage driver Joshua Yeong
2026-09-23 7:00 ` Joshua Yeong
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=0db3ed29-8bb8-4dc3-a4cb-cc5b9bf2e893@kernel.org \
--to=krzk@kernel.org \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joshua.yeong@starfivetech.com \
--cc=krzk+dt@kernel.org \
--cc=lftan.linux@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=rahul@summations.net \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.