All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	Joshua Yeong <joshua.yeong@starfivetech.com>,
	"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: Sat, 26 Sep 2026 22:21:22 +0100	[thread overview]
Message-ID: <20260926-peddling-share-5e5e8dffaa63@spud> (raw)
In-Reply-To: <a5d0d4df-7e8e-4f12-b011-e41b66efd8a7@sirena.org.uk>


[-- Attachment #1.1: Type: text/plain, Size: 1094 bytes --]

On Fri, Sep 25, 2026 at 06:15:35PM +0100, Mark Brown wrote:
> On Fri, Sep 25, 2026 at 05:18:08PM +0200, Krzysztof Kozlowski wrote:
> > On 25/09/2026 09:14, Joshua Yeong wrote:
> 
> > > While the above method works but I'm trying to get the entire simplify to the following.
> 
> > > user-app-b {
> > > 	compatible = "...";
> > > 	voltage-domains = <&rpmi-voltage 0x01>;
> 
> > I see. Why power domains do not fit here?
> 
> The spec seems to map very clearly onto voltage regulators, it describes
> voltages in mV:
> 
>   https://github.com/riscv-non-isa/riscv-rpmi/blob/main/src/srvgrp-voltage.adoc
> 
> I really don't see any problem describing this as regulators, it seems
> to fulfil exactly the same role as SCMI regulators, supporting things
> like SD slots where the OS genuinely needs to control voltages on a
> mostly system power controller system.

Unless I misunderstand your intent, me either. The binding permits
having regulator subnodes too, so culling this "voltage-domain" business
and going for the regulators alone shouldn't be much of a shift.



[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 161 bytes --]

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	Joshua Yeong <joshua.yeong@starfivetech.com>,
	"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: Sat, 26 Sep 2026 22:21:22 +0100	[thread overview]
Message-ID: <20260926-peddling-share-5e5e8dffaa63@spud> (raw)
In-Reply-To: <a5d0d4df-7e8e-4f12-b011-e41b66efd8a7@sirena.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]

On Fri, Sep 25, 2026 at 06:15:35PM +0100, Mark Brown wrote:
> On Fri, Sep 25, 2026 at 05:18:08PM +0200, Krzysztof Kozlowski wrote:
> > On 25/09/2026 09:14, Joshua Yeong wrote:
> 
> > > While the above method works but I'm trying to get the entire simplify to the following.
> 
> > > user-app-b {
> > > 	compatible = "...";
> > > 	voltage-domains = <&rpmi-voltage 0x01>;
> 
> > I see. Why power domains do not fit here?
> 
> The spec seems to map very clearly onto voltage regulators, it describes
> voltages in mV:
> 
>   https://github.com/riscv-non-isa/riscv-rpmi/blob/main/src/srvgrp-voltage.adoc
> 
> I really don't see any problem describing this as regulators, it seems
> to fulfil exactly the same role as SCMI regulators, supporting things
> like SD slots where the OS genuinely needs to control voltages on a
> mostly system power controller system.

Unless I misunderstand your intent, me either. The binding permits
having regulator subnodes too, so culling this "voltage-domain" business
and going for the regulators alone shouldn't be much of a shift.



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-09-26 21:21 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
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 [this message]
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=20260926-peddling-share-5e5e8dffaa63@spud \
    --to=conor@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=krzk@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.