public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yury Norov <yury.norov@gmail.com>
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>,
	"Danilo Krummrich" <dakr@kernel.org>,
	linux-pm@vger.kernel.org,
	"Vincent Guittot" <vincent.guittot@linaro.org>,
	rust-for-linux@vger.kernel.org,
	"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
	"Erik Schilling" <erik.schilling@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Joakim Bech" <joakim.bech@linaro.org>,
	"Rob Herring" <robh@kernel.org>, "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 V9 11/17] rust: opp: Add abstractions for the OPP table
Date: Fri, 11 Apr 2025 12:29:58 -0400	[thread overview]
Message-ID: <Z_lDhj220aqU44P4@yury> (raw)
In-Reply-To: <1961fd9a4ef44dbda18a63eb832dc3a3176c2314.1744366571.git.viresh.kumar@linaro.org>

On Fri, Apr 11, 2025 at 04:25:10PM +0530, Viresh Kumar wrote:
> Introduce Rust abstractions for `struct opp_table`, enabling access to
> OPP tables from Rust.
> 
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
>  rust/kernel/opp.rs | 495 ++++++++++++++++++++++++++++++++++++++++++++-
>  1 file changed, 494 insertions(+), 1 deletion(-)
> 
> diff --git a/rust/kernel/opp.rs b/rust/kernel/opp.rs
> index e4780b41664f..e074009e4b7a 100644
> --- a/rust/kernel/opp.rs
> +++ b/rust/kernel/opp.rs
> @@ -11,8 +11,9 @@
>  use crate::{
>      bindings,
>      clk::Hertz,
> +    cpumask::{Cpumask, CpumaskVar},
>      device::Device,
> -    error::{code::*, to_result, Result},
> +    error::{code::*, from_err_ptr, to_result, Error, Result},
>      ffi::c_ulong,
>      types::{ARef, AlwaysRefCounted, Opaque},
>  };
> @@ -172,6 +173,477 @@ fn freq(&self) -> Hertz {
>      }
>  }
>  
> +/// [`OPP`] search options.
> +///
> +/// ## Examples
> +///
> +/// Defines how to search for an [`OPP`] in a [`Table`] relative to a frequency.
> +///
> +/// ```
> +/// use kernel::clk::Hertz;
> +/// use kernel::error::Result;
> +/// use kernel::opp::{OPP, SearchType, Table};
> +/// use kernel::types::ARef;
> +///
> +/// fn find_opp(table: &Table, freq: Hertz) -> Result<ARef<OPP>> {
> +///     let opp = table.opp_from_freq(freq, Some(true), None, SearchType::Exact)?;
> +///
> +///     pr_info!("OPP frequency is: {:?}\n", opp.freq(None));
> +///     pr_info!("OPP voltage is: {:?}\n", opp.voltage());
> +///     pr_info!("OPP level is: {}\n", opp.level());
> +///     pr_info!("OPP power is: {:?}\n", opp.power());
> +///
> +///     Ok(opp)
> +/// }
> +/// ```
> +#[derive(Copy, Clone, Debug, Eq, PartialEq)]
> +pub enum SearchType {
> +    /// Match the exact frequency.
> +    Exact,
> +    /// Find the highest frequency less than or equal to the given value.
> +    Floor,
> +    /// Find the lowest frequency greater than or equal to the given value.
> +    Ceil,
> +}
> +
> +/// A reference-counted OPP table.
> +///
> +/// Rust abstraction for the C `struct opp_table`.
> +///
> +/// # Invariants
> +///
> +/// The pointer stored in `Self` is non-null and valid for the lifetime of the [`Table`].
> +///
> +/// Instances of this type are reference-counted.
> +///
> +/// ## Examples
> +///
> +/// The following example demonstrates how to get OPP [`Table`] for a [`Cpumask`] and set its
> +/// frequency.
> +///
> +/// ```
> +/// use kernel::clk::Hertz;
> +/// use kernel::cpumask::Cpumask;
> +/// use kernel::device::Device;
> +/// use kernel::error::Result;
> +/// use kernel::opp::Table;
> +/// use kernel::types::ARef;
> +///
> +/// fn get_table(dev: &ARef<Device>, mask: &mut Cpumask, freq: Hertz) -> Result<Table> {
> +///     let mut opp_table = Table::from_of_cpumask(dev, mask)?;
> +///
> +///     if opp_table.opp_count()? == 0 {
> +///         return Err(EINVAL);
> +///     }
> +///
> +///     pr_info!("Max transition latency is: {} ns\n", opp_table.max_transition_latency_ns());
> +///     pr_info!("Suspend frequency is: {:?}\n", opp_table.suspend_freq());
> +///
> +///     opp_table.set_rate(freq)?;
> +///     Ok(opp_table)
> +/// }
> +/// ```
> +pub struct Table {
> +    ptr: *mut bindings::opp_table,
> +    dev: ARef<Device>,
> +    em: bool,
> +    of: bool,
> +    cpumask_box: Option<CpumaskVar>,

The other fields have short names. Maybe just 'cpus' instead of
cpumask_box? If you want to put the type of variable into the name, it
should be a cpumask_var.

> +}

  reply	other threads:[~2025-04-11 16:30 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11 10:54 [PATCH V9 00/17] Rust abstractions for clk, cpumask, cpufreq, OPP Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 01/17] rust: cpumask: Use non-atomic helpers Viresh Kumar
2025-04-11 15:20   ` Yury Norov
2025-04-11 10:55 ` [PATCH V9 02/17] rust: cpumask: Add few more helpers Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 03/17] rust: cpumask: Add initial abstractions Viresh Kumar
2025-04-11 15:54   ` Yury Norov
2025-04-14 11:29     ` Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 04/17] MAINTAINERS: Add entry for Rust cpumask API Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 05/17] rust: clk: Add helpers for Rust code Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 06/17] rust: clk: Add initial abstractions Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 07/17] rust: macros: enable use of hyphens in module names Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 08/17] cpufreq: Use enum for cpufreq flags that use BIT() Viresh Kumar
2025-04-11 16:07   ` Yury Norov
2025-04-11 17:05     ` Miguel Ojeda
2025-04-11 10:55 ` [PATCH V9 09/17] rust: cpu: Add from_cpu() Viresh Kumar
2025-04-11 16:18   ` Yury Norov
2025-04-11 18:03     ` Danilo Krummrich
2025-04-11 10:55 ` [PATCH V9 10/17] rust: opp: Add initial abstractions for OPP framework Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 11/17] rust: opp: Add abstractions for the OPP table Viresh Kumar
2025-04-11 16:29   ` Yury Norov [this message]
2025-04-11 10:55 ` [PATCH V9 12/17] rust: opp: Add abstractions for the configuration options Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 13/17] rust: cpufreq: Add initial abstractions for cpufreq framework Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 14/17] rust: cpufreq: Extend abstractions for policy and driver ops Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 15/17] rust: cpufreq: Extend abstractions for driver registration Viresh Kumar
2025-04-11 11:58   ` Danilo Krummrich
2025-04-14  8:47     ` Viresh Kumar
2025-04-14  9:39       ` Danilo Krummrich
2025-04-14 10:52         ` Viresh Kumar
2025-04-14 11:51           ` Danilo Krummrich
2025-04-11 10:55 ` [PATCH V9 16/17] rust: opp: Extend OPP abstractions with cpufreq support Viresh Kumar
2025-04-11 10:55 ` [PATCH V9 17/17] 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_lDhj220aqU44P4@yury \
    --to=yury.norov@gmail.com \
    --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@kernel.org \
    --cc=dakr@redhat.com \
    --cc=erik.schilling@linaro.org \
    --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 \
    /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