mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joshua Yeong <joshua.yeong@starfivetech.com>
To: rahul@summations.net, anup@brainfault.org,
	joshua.yeong@starfivetech.com, leyfoon.tan@starfivetech.com,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
	alex@ghiti.fr, rafael@kernel.org, viresh.kumar@linaro.org,
	sboyd@kernel.org, jms@oss.tenstorrent.com,
	darshan.prajapati@einfochips.com, charlie@rivosinc.com,
	dfustini@oss.tenstorrent.com, michal.simek@amd.com,
	cyy@cyyself.name, jassisinghbrar@gmail.com,
	andriy.shevchenko@linux.intel.com
Cc: linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: [PATCH 0/5] RISC-V: RPMI performance service bindings and cpufreq support
Date: Tue,  6 Jan 2026 17:21:11 +0800	[thread overview]
Message-ID: <20260106092117.3727152-1-joshua.yeong@starfivetech.com> (raw)

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

 .../firmware/riscv,rpmi-mpxy-performance.yaml |  65 ++
 .../firmware/riscv,rpmi-performance.yaml      |  62 ++
 .../devicetree/bindings/riscv/cpus.yaml       |   7 +
 MAINTAINERS                                   |   4 +
 drivers/cpufreq/Kconfig                       |  26 +-
 drivers/cpufreq/Makefile                      |   6 +-
 drivers/cpufreq/riscv-rpmi-cpufreq.c          | 976 ++++++++++++++++++
 include/linux/mailbox/riscv-rpmi-message.h    |  16 +
 8 files changed, 1155 insertions(+), 7 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/firmware/riscv,rpmi-mpxy-performance.yaml
 create mode 100644 Documentation/devicetree/bindings/firmware/riscv,rpmi-performance.yaml
 create mode 100644 drivers/cpufreq/riscv-rpmi-cpufreq.c

--
2.43.0

             reply	other threads:[~2026-01-06  9:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06  9:21 Joshua Yeong [this message]
2026-01-06  9:21 ` [PATCH 1/5] dt-bindings: firmware: Add RPMI performance service message proxy bindings Joshua Yeong
2026-01-06 10:49   ` Rob Herring (Arm)
2026-01-06  9:21 ` [PATCH 2/5] dt-bindings: firmware: Add RPMI performance service bindings Joshua Yeong
2026-01-06  9:21 ` [PATCH 3/5] dt-bindings: riscv: cpus: document performance-domains property Joshua Yeong
2026-01-06  9:21 ` [PATCH 4/5] cpufreq: Add cpufreq driver for the RISC-V RPMI performance service group Joshua Yeong
2026-01-08  3:27   ` Viresh Kumar
2026-01-08  6:48     ` Joshua Yeong
2026-01-08  6:52       ` Viresh Kumar
2026-01-12 10:47   ` Rahul Pathak
2026-01-12 11:58     ` Anup Patel
2026-01-13  2:35     ` Joshua Yeong
2026-01-13  5:31       ` Rahul Pathak
2026-01-06  9:21 ` [PATCH 5/5] MAINTAINERS: Add " Joshua Yeong
2026-01-08  5:27 ` [PATCH 0/5] RISC-V: RPMI performance service bindings and cpufreq support Rahul Pathak
2026-01-08  6:56   ` 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=20260106092117.3727152-1-joshua.yeong@starfivetech.com \
    --to=joshua.yeong@starfivetech.com \
    --cc=alex@ghiti.fr \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=charlie@rivosinc.com \
    --cc=conor+dt@kernel.org \
    --cc=cyy@cyyself.name \
    --cc=darshan.prajapati@einfochips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dfustini@oss.tenstorrent.com \
    --cc=jassisinghbrar@gmail.com \
    --cc=jms@oss.tenstorrent.com \
    --cc=krzk+dt@kernel.org \
    --cc=leyfoon.tan@starfivetech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=michal.simek@amd.com \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=rafael@kernel.org \
    --cc=rahul@summations.net \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=viresh.kumar@linaro.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®