rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux PM <linux-pm@vger.kernel.org>, rust-for-linux@vger.kernel.org
Subject: [GIT PULL] cpufreq/arm updates for 6.16
Date: Tue, 20 May 2025 11:49:44 +0530	[thread overview]
Message-ID: <20250520061944.pl3mqw2clo2roe3s@vireshk-i7> (raw)

Hi Rafael,

This contains few patches from Danilo Krummrich as well, which will
get merged via driver-core separately. Please push this to Linus once
that is merged during rc1. Thanks.

The following changes since commit a374f28700abd20e8a7d026f89aa26f759445918:

  cpufreq: fix compile-test defaults (2025-04-17 13:36:29 +0530)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git tags/cpufreq-arm-updates-6.16

for you to fetch changes up to 6c9bb86922728c7a4cceb99f131e00dd87514f20:

  cpufreq: scmi: Skip SCMI devices that aren't used by the CPUs (2025-05-20 11:24:18 +0530)

----------------------------------------------------------------
CPUFreq updates for 6.16

- Rust abstractions for CPUFreq framework (Viresh Kumar).

- Rust abstractions for OPP framework (Viresh Kumar).

- Basic Rust abstractions for Clk and Cpumask frameworks (Viresh Kumar).

- Minor cleanup to the SCMI cpufreq driver (Mike Tipton).

----------------------------------------------------------------
Anisse Astier (1):
      rust: macros: enable use of hyphens in module names

Danilo Krummrich (8):
      rust: device: implement impl_device_context_deref!
      rust: device: implement impl_device_context_into_aref!
      rust: device: implement device context for Device
      rust: platform: preserve device context in AsRef
      rust: pci: preserve device context in AsRef
      rust: device: implement Bound device context
      rust: pci: move iomap_region() to impl Device<Bound>
      rust: devres: require a bound device

Mike Tipton (1):
      cpufreq: scmi: Skip SCMI devices that aren't used by the CPUs

Viresh Kumar (16):
      Merge commit 'eaff6b62d343' of pm/linux-next into commit 'f720efda2db5' of driver-core/driver-core-next
      rust: cpumask: Add few more helpers
      rust: cpumask: Add initial abstractions
      MAINTAINERS: Add entry for Rust cpumask API
      rust: clk: Add helpers for Rust code
      rust: clk: Add initial abstractions
      rust: cpu: Add from_cpu()
      rust: opp: Add initial abstractions for OPP framework
      rust: opp: Add abstractions for the OPP table
      rust: opp: Add abstractions for the configuration options
      rust: cpufreq: Add initial abstractions for cpufreq framework
      rust: cpufreq: Extend abstractions for policy and driver ops
      rust: cpufreq: Extend abstractions for driver registration
      rust: opp: Extend OPP abstractions with cpufreq support
      cpufreq: Add Rust-based cpufreq-dt driver
      Merge branch 'rust/cpufreq-dt' into cpufreq/arm/linux-next

 MAINTAINERS                     |   11 ++
 drivers/cpufreq/Kconfig         |   12 ++
 drivers/cpufreq/Makefile        |    1 +
 drivers/cpufreq/amd-pstate.c    |    7 +-
 drivers/cpufreq/cpufreq.c       |  345 +++++++++++++++++----------------------
 drivers/cpufreq/intel_pstate.c  |   47 +++---
 drivers/cpufreq/rcpufreq_dt.rs  |  226 ++++++++++++++++++++++++++
 drivers/cpufreq/scmi-cpufreq.c  |   36 ++++-
 include/linux/cpufreq.h         |   10 +-
 rust/bindings/bindings_helper.h |    4 +
 rust/helpers/clk.c              |   66 ++++++++
 rust/helpers/cpufreq.c          |   10 ++
 rust/helpers/cpumask.c          |   25 +++
 rust/helpers/helpers.c          |    2 +
 rust/kernel/clk.rs              |  334 ++++++++++++++++++++++++++++++++++++++
 rust/kernel/cpu.rs              |   30 ++++
 rust/kernel/cpufreq.rs          | 1321 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 rust/kernel/cpumask.rs          |  330 +++++++++++++++++++++++++++++++++++++
 rust/kernel/device.rs           |   90 ++++++++++-
 rust/kernel/devres.rs           |   17 +-
 rust/kernel/lib.rs              |    7 +
 rust/kernel/opp.rs              | 1145 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 rust/kernel/pci.rs              |   33 ++--
 rust/kernel/platform.rs         |   32 +---
 rust/macros/module.rs           |   20 ++-
 25 files changed, 3861 insertions(+), 300 deletions(-)
 create mode 100644 drivers/cpufreq/rcpufreq_dt.rs
 create mode 100644 rust/helpers/clk.c
 create mode 100644 rust/helpers/cpufreq.c
 create mode 100644 rust/kernel/clk.rs
 create mode 100644 rust/kernel/cpu.rs
 create mode 100644 rust/kernel/cpufreq.rs
 create mode 100644 rust/kernel/cpumask.rs
 create mode 100644 rust/kernel/opp.rs

-- 
viresh

             reply	other threads:[~2025-05-20  6:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20  6:19 Viresh Kumar [this message]
2025-05-22 10:20 ` [GIT PULL] cpufreq/arm updates for 6.16 Rafael J. Wysocki
2025-05-28 11:35   ` Rafael J. Wysocki
2025-05-28 11:44     ` Alice Ryhl
2025-05-28 12:21       ` Rafael J. Wysocki
2025-05-29  5:03         ` Viresh Kumar

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=20250520061944.pl3mqw2clo2roe3s@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rust-for-linux@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).