From: Danilo Krummrich <dakr@kernel.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
"Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
"Danilo Krummrich" <dakr@redhat.com>,
"Viresh Kumar" <vireshk@kernel.org>, "Nishanth Menon" <nm@ti.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
linux-pm@vger.kernel.org,
"Vincent Guittot" <vincent.guittot@linaro.org>,
rust-for-linux@vger.kernel.org,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Joakim Bech" <joakim.bech@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Yury Norov" <yury.norov@gmail.com>,
"Burak Emir" <bqe@google.com>,
"Rasmus Villemoes" <linux@rasmusvillemoes.dk>,
"Russell King" <linux@armlinux.org.uk>,
linux-clk@vger.kernel.org,
"Michael Turquette" <mturquette@baylibre.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V10 14/15] rust: opp: Extend OPP abstractions with cpufreq support
Date: Wed, 16 Apr 2025 14:46:52 +0200 [thread overview]
Message-ID: <Z_-mvB7hibFD4Q34@pollux> (raw)
In-Reply-To: <20250416095943.f3jxy55bamekscst@vireshk-i7>
On Wed, Apr 16, 2025 at 03:29:43PM +0530, Viresh Kumar wrote:
> On 16-04-25, 10:52, Danilo Krummrich wrote:
> > This config is needed quite often, it probably makes sense to move this code in
> > its own Rust module, i.e.:
> >
> > #[cfg(CONFIG_CPU_FREQ)]
> > pub mod freq;
>
> Like this ?
Yes, I thought of a separate file, but I that should work as well.
>
> diff --git a/rust/kernel/opp.rs b/rust/kernel/opp.rs
> index 734be8b6d0ef..f4cabe859c43 100644
> --- a/rust/kernel/opp.rs
> +++ b/rust/kernel/opp.rs
> @@ -20,10 +20,67 @@
> };
>
> #[cfg(CONFIG_CPU_FREQ)]
> -use crate::cpufreq;
> +// Frequency table implementation.
> +mod freq {
> + use crate::cpufreq;
> + use core::ops::Deref;
> + use super::*;
> +
> + /// OPP frequency table.
> + ///
> + /// A [`cpufreq::Table`] created from [`Table`].
> + pub struct FreqTable {
> + dev: ARef<Device>,
> + ptr: *mut bindings::cpufreq_frequency_table,
> + }
> +
> + impl FreqTable {
> + /// Creates a new instance of [`FreqTable`] from [`Table`].
> + pub(crate) fn new(table: &Table) -> Result<Self> {
> + let mut ptr: *mut bindings::cpufreq_frequency_table = ptr::null_mut();
> +
> + // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
> + // requirements.
> + to_result(unsafe {
> + bindings::dev_pm_opp_init_cpufreq_table(table.dev.as_raw(), &mut ptr)
> + })?;
> +
> + Ok(Self {
> + dev: table.dev.clone(),
> + ptr,
> + })
> + }
> +
> + // Returns a reference to the underlying [`cpufreq::Table`].
> + #[inline]
> + fn table(&self) -> &cpufreq::Table {
> + // SAFETY: The `ptr` is guaranteed by the C code to be valid.
> + unsafe { cpufreq::Table::from_raw(self.ptr) }
> + }
> + }
> +
> + impl Deref for FreqTable {
> + type Target = cpufreq::Table;
> +
> + #[inline]
> + fn deref(&self) -> &Self::Target {
> + self.table()
> + }
> + }
> +
> + impl Drop for FreqTable {
> + fn drop(&mut self) {
> + // SAFETY: The pointer was created via `dev_pm_opp_init_cpufreq_table`, and is only
> + // freed here.
> + unsafe {
> + bindings::dev_pm_opp_free_cpufreq_table(self.dev.as_raw(), &mut self.as_raw())
> + };
> + }
> + }
> +}
>
> #[cfg(CONFIG_CPU_FREQ)]
> -use core::ops::Deref;
> +pub use freq::FreqTable;
>
> use core::{marker::PhantomData, ptr};
>
> @@ -502,60 +559,6 @@ extern "C" fn config_regulators(
> }
> }
>
> -/// OPP frequency table.
> -///
> -/// A [`cpufreq::Table`] created from [`Table`].
> -#[cfg(CONFIG_CPU_FREQ)]
> -pub struct FreqTable {
> - dev: ARef<Device>,
> - ptr: *mut bindings::cpufreq_frequency_table,
> -}
> -
> -#[cfg(CONFIG_CPU_FREQ)]
> -impl FreqTable {
> - /// Creates a new instance of [`FreqTable`] from [`Table`].
> - fn new(table: &Table) -> Result<Self> {
> - let mut ptr: *mut bindings::cpufreq_frequency_table = ptr::null_mut();
> -
> - // SAFETY: The requirements are satisfied by the existence of [`Device`] and its safety
> - // requirements.
> - to_result(unsafe {
> - bindings::dev_pm_opp_init_cpufreq_table(table.dev.as_raw(), &mut ptr)
> - })?;
> -
> - Ok(Self {
> - dev: table.dev.clone(),
> - ptr,
> - })
> - }
> -
> - // Returns a reference to the underlying [`cpufreq::Table`].
> - #[inline]
> - fn table(&self) -> &cpufreq::Table {
> - // SAFETY: The `ptr` is guaranteed by the C code to be valid.
> - unsafe { cpufreq::Table::from_raw(self.ptr) }
> - }
> -}
> -
> -#[cfg(CONFIG_CPU_FREQ)]
> -impl Deref for FreqTable {
> - type Target = cpufreq::Table;
> -
> - #[inline]
> - fn deref(&self) -> &Self::Target {
> - self.table()
> - }
> -}
> -
> -#[cfg(CONFIG_CPU_FREQ)]
> -impl Drop for FreqTable {
> - fn drop(&mut self) {
> - // SAFETY: The pointer was created via `dev_pm_opp_init_cpufreq_table`, and is only freed
> - // here.
> - unsafe { bindings::dev_pm_opp_free_cpufreq_table(self.dev.as_raw(), &mut self.as_raw()) };
> - }
> -}
> -
> /// A reference-counted OPP table.
> ///
> /// Rust abstraction for the C `struct opp_table`.
>
> --
> viresh
next prev parent reply other threads:[~2025-04-16 12:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 6:39 [PATCH V10 00/15] Rust abstractions for clk, cpumask, cpufreq, OPP Viresh Kumar
2025-04-16 6:39 ` [PATCH V10 01/15] rust: cpumask: Add few more helpers Viresh Kumar
2025-04-16 6:39 ` [PATCH V10 02/15] rust: cpumask: Add initial abstractions Viresh Kumar
2025-04-16 6:39 ` [PATCH V10 03/15] MAINTAINERS: Add entry for Rust cpumask API Viresh Kumar
2025-04-16 6:39 ` [PATCH V10 04/15] rust: clk: Add helpers for Rust code Viresh Kumar
2025-04-16 6:39 ` [PATCH V10 05/15] rust: clk: Add initial abstractions Viresh Kumar
2025-04-16 6:39 ` [PATCH V10 06/15] rust: macros: enable use of hyphens in module names Viresh Kumar
2025-04-16 6:39 ` [PATCH V10 07/15] rust: cpu: Add from_cpu() Viresh Kumar
2025-04-16 6:39 ` [PATCH V10 08/15] rust: opp: Add initial abstractions for OPP framework Viresh Kumar
2025-04-16 6:39 ` [PATCH V10 09/15] rust: opp: Add abstractions for the OPP table Viresh Kumar
2025-04-16 6:39 ` [PATCH V10 10/15] rust: opp: Add abstractions for the configuration options Viresh Kumar
2025-04-16 6:39 ` [PATCH V10 11/15] rust: cpufreq: Add initial abstractions for cpufreq framework Viresh Kumar
2025-04-16 9:14 ` Danilo Krummrich
2025-04-16 9:37 ` Viresh Kumar
2025-04-16 12:25 ` Danilo Krummrich
2025-04-17 8:34 ` Viresh Kumar
2025-04-17 8:00 ` Benno Lossin
2025-04-17 8:08 ` Viresh Kumar
2025-04-16 6:39 ` [PATCH V10 12/15] rust: cpufreq: Extend abstractions for policy and driver ops Viresh Kumar
2025-04-16 6:39 ` [PATCH V10 13/15] rust: cpufreq: Extend abstractions for driver registration Viresh Kumar
2025-04-16 9:04 ` Danilo Krummrich
2025-04-16 10:17 ` Viresh Kumar
2025-04-16 10:59 ` Danilo Krummrich
2025-04-17 8:29 ` Viresh Kumar
2025-04-16 6:39 ` [PATCH V10 14/15] rust: opp: Extend OPP abstractions with cpufreq support Viresh Kumar
2025-04-16 8:52 ` Danilo Krummrich
2025-04-16 9:59 ` Viresh Kumar
2025-04-16 10:31 ` Miguel Ojeda
2025-04-16 10:40 ` Viresh Kumar
2025-04-16 10:47 ` Miguel Ojeda
2025-04-16 12:46 ` Danilo Krummrich [this message]
2025-04-16 6:39 ` [PATCH V10 15/15] cpufreq: Add Rust-based cpufreq-dt driver 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=Z_-mvB7hibFD4Q34@pollux \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.bennee@linaro.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=bqe@google.com \
--cc=dakr@redhat.com \
--cc=gary@garyguo.net \
--cc=joakim.bech@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linux@rasmusvillemoes.dk \
--cc=manos.pitsidianakis@linaro.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mturquette@baylibre.com \
--cc=nm@ti.com \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tmgross@umich.edu \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@kernel.org \
--cc=yury.norov@gmail.com \
/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).