[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<SH0PR01MB08414F0C86E4A624D0F08EFDF9852@SH0PR01MB0841.CHNPR01.prod.partner.outlook.cn>
Date: Thu, 8 Jan 2026 06:56:01 +0000
From: Joshua Yeong <joshua.yeong@...rfivetech.com>
To: Rahul Pathak <rahul@...mations.net>
CC: "anup@...infault.org" <anup@...infault.org>, Leyfoon Tan
<leyfoon.tan@...rfivetech.com>, "robh@...nel.org" <robh@...nel.org>,
"krzk+dt@...nel.org" <krzk+dt@...nel.org>, "conor+dt@...nel.org"
<conor+dt@...nel.org>, "pjw@...nel.org" <pjw@...nel.org>,
"palmer@...belt.com" <palmer@...belt.com>, "aou@...s.berkeley.edu"
<aou@...s.berkeley.edu>, "alex@...ti.fr" <alex@...ti.fr>, "rafael@...nel.org"
<rafael@...nel.org>, "viresh.kumar@...aro.org" <viresh.kumar@...aro.org>,
"sboyd@...nel.org" <sboyd@...nel.org>, "jms@....tenstorrent.com"
<jms@....tenstorrent.com>, "darshan.prajapati@...fochips.com"
<darshan.prajapati@...fochips.com>, "charlie@...osinc.com"
<charlie@...osinc.com>, "dfustini@....tenstorrent.com"
<dfustini@....tenstorrent.com>, "michal.simek@....com"
<michal.simek@....com>, "cyy@...self.name" <cyy@...self.name>,
"jassisinghbrar@...il.com" <jassisinghbrar@...il.com>,
"andriy.shevchenko@...ux.intel.com" <andriy.shevchenko@...ux.intel.com>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>
Subject: RE: [PATCH 0/5] RISC-V: RPMI performance service bindings and cpufreq
support
On Thursday, January 8, 2026 1:27 PM, Rahul Pathak <rahul@...mations.net> wrote:
> On Tue, Jan 6, 2026 at 2:51 PM Joshua Yeong <joshua.yeong@...rfivetech.com> wrote:
> >
> > This patch series introduces support for the RISC-V RPMI (RISC-V
> > Platform Management Interface) performance service, covering both
> > Device Tree bindings and a corresponding cpufreq driver.
> >
> > The first part of the series adds YAML bindings to describe the RPMI
> > performance service as provided by platform firmware, as well as the
> > supervisor-level controller interface exposed to the operating system.
> > The bindings also document how CPU nodes reference performance domains managed by RPMI.
> >
> > The final patch builds on these definitions by introducing a cpufreq
> > driver that leverages the RPMI performance service to manage CPU
> > frequency scaling on RISC-V systems. The driver supports RPMI access
> > through SBI-based transport mechanisms as well as dedicated supervisor-mode transports.
> >
> > RPMI specification reference [1] and [2]
> >
> > Test Environment is as follows:
> > https://github.com/yeongjoshua/linux/tree/v6.19-rc4/rpmi-performance
> > https://github.com/riscv-software-src/opensbi
> > https://github.com/yeongjoshua/qemu/tree/rpmi-dev-upstream
> >
> > Use '-M virt -M rpmi=true' when running qemu
> >
> > [1] https://github.com/riscv-non-isa/riscv-sbi-doc/releases
> > [2] https://github.com/riscv-non-isa/riscv-rpmi/releases
> >
> > Joshua Yeong (5):
> > dt-bindings: firmware: Add RPMI performance service message proxy
> > bindings
> > dt-bindings: firmware: Add RPMI performance service bindings
> > dt-bindings: riscv: cpus: document performance-domains property
> > cpufreq: Add cpufreq driver for the RISC-V RPMI performance service
> > group
> > MAINTAINERS: Add RISC-V RPMI performance service group
>
>
> Hi Joshua,
>
> I have a general question - RPMI performance service group is primarily defined for devices but can also be used for CPUs.
> Do you plan to add a RPMI devfreq driver too for devices?
>
> Thanks
> Rahul
Hi Rahul,
My side is yet to test performance service group with devfreq but should have no problem like you mentioned.
I will have a look after the other RPMI service group upstreamed on my side.
Thanks
Powered by blists - more mailing lists