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>,
"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>,
"Stephen Boyd" <sboyd@kernel.org>, "Nishanth Menon" <nm@ti.com>,
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>,
"Andrew Ballance" <andrewjballance@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V12 13/15] rust: cpufreq: Extend abstractions for driver registration
Date: Mon, 19 May 2025 13:06:50 +0200 [thread overview]
Message-ID: <aCsQylyW7R5rC15m@pollux> (raw)
In-Reply-To: <68906d67109c3b323b54469fb1ee44e10c1c5b1e.1747634382.git.viresh.kumar@linaro.org>
On Mon, May 19, 2025 at 12:37:18PM +0530, Viresh Kumar wrote:
> +/// CPU frequency driver Registration.
> +///
> +/// ## Examples
> +///
> +/// The following example demonstrates how to register a cpufreq driver.
> +///
> +/// ```
> +/// use kernel::{
> +/// cpu, cpufreq,
> +/// c_str,
> +/// device::{Bound, Device},
> +/// macros::vtable,
> +/// sync::Arc,
> +/// };
> +/// struct FooDevice;
> +///
> +/// #[derive(Default)]
> +/// struct FooDriver;
> +///
> +/// #[vtable]
> +/// impl cpufreq::Driver for FooDriver {
> +/// const NAME: &'static CStr = c_str!("cpufreq-foo");
> +/// const FLAGS: u16 = cpufreq::flags::NEED_INITIAL_FREQ_CHECK | cpufreq::flags::IS_COOLING_DEV;
> +/// const BOOST_ENABLED: bool = true;
> +///
> +/// type PData = Arc<FooDevice>;
> +///
> +/// fn init(policy: &mut cpufreq::Policy) -> Result<Self::PData> {
> +/// // Initialize here
> +/// Ok(Arc::new(FooDevice, GFP_KERNEL)?)
> +/// }
> +///
> +/// fn exit(_policy: &mut cpufreq::Policy, _data: Option<Self::PData>) -> Result<()> {
This can just be `Result`, here and below.
> +/// Ok(())
> +/// }
> +///
> +/// fn suspend(policy: &mut cpufreq::Policy) -> Result<()> {
> +/// policy.generic_suspend()
> +/// }
> +///
> +/// fn verify(data: &mut cpufreq::PolicyData) -> Result<()> {
> +/// data.generic_verify()
> +/// }
> +///
> +/// fn target_index(policy: &mut cpufreq::Policy, index: cpufreq::TableIndex) -> Result<()> {
> +/// // Update CPU frequency
> +/// Ok(())
> +/// }
> +///
> +/// fn get(policy: &mut cpufreq::Policy) -> Result<u32> {
> +/// policy.generic_get()
> +/// }
> +/// }
> +///
> +/// fn foo_probe(dev: &Device<Bound>) {
You could use a real probe function, e.g. from platform:
# struct Driver;
impl platform::Driver for SampleDriver {
# type IdInfo = ();
# const OF_ID_TABLE: Option<of::IdTable<Self::IdInfo>> = None;
fn probe(
pdev: &platform::Device<Core>,
info: Option<&Self::IdInfo>,
) -> Result<Pin<KBox<Self>>> {
...
}
}
> +/// cpufreq::Registration::<FooDriver>::new_foreign_owned(dev).unwrap();
I prefer if we do not use unwrap() in doctests, since they also serve as example
and people might think that calling unwrap() is valid thing to do.
Sorry, I didn't catch the above in my previous review -- fine for me if you do
those improvements in a subsequent patch.
next prev parent reply other threads:[~2025-05-19 11:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <HVTDJypFNQFfSQJmmYDSPU4o-irFnjmDN22RW3S0z5Kwe_hVk9kquZWElv-C2k6d5kOIiewhj_Xo2kAoTHbHgg==@protonmail.internalid>
2025-05-19 7:07 ` [PATCH V12 00/15] Rust abstractions for clk, cpumask, cpufreq, OPP Viresh Kumar
2025-05-19 7:07 ` [PATCH V12 01/15] rust: cpumask: Add few more helpers Viresh Kumar
2025-05-19 7:07 ` [PATCH V12 02/15] rust: cpumask: Add initial abstractions Viresh Kumar
2025-05-19 7:07 ` [PATCH V12 03/15] MAINTAINERS: Add entry for Rust cpumask API Viresh Kumar
2025-05-19 7:07 ` [PATCH V12 04/15] rust: clk: Add helpers for Rust code Viresh Kumar
2025-05-19 7:07 ` [PATCH V12 05/15] rust: clk: Add initial abstractions Viresh Kumar
2025-05-19 7:07 ` [PATCH V12 06/15] rust: macros: enable use of hyphens in module names Viresh Kumar
2025-05-19 8:00 ` Benno Lossin
2025-05-19 9:58 ` Viresh Kumar
2025-05-19 14:15 ` Miguel Ojeda
2025-05-20 4:33 ` Viresh Kumar
2025-05-20 6:13 ` Anisse Astier
2025-05-20 6:22 ` Viresh Kumar
2025-05-19 7:07 ` [PATCH V12 07/15] rust: cpu: Add from_cpu() Viresh Kumar
2025-05-19 7:07 ` [PATCH V12 08/15] rust: opp: Add initial abstractions for OPP framework Viresh Kumar
2025-05-19 7:07 ` [PATCH V12 09/15] rust: opp: Add abstractions for the OPP table Viresh Kumar
2025-05-19 7:07 ` [PATCH V12 10/15] rust: opp: Add abstractions for the configuration options Viresh Kumar
2025-05-19 7:07 ` [PATCH V12 11/15] rust: cpufreq: Add initial abstractions for cpufreq framework Viresh Kumar
2025-05-19 7:07 ` [PATCH V12 12/15] rust: cpufreq: Extend abstractions for policy and driver ops Viresh Kumar
2025-05-19 7:07 ` [PATCH V12 13/15] rust: cpufreq: Extend abstractions for driver registration Viresh Kumar
2025-05-19 11:06 ` Danilo Krummrich [this message]
2025-05-19 11:41 ` Benno Lossin
2025-05-19 11:49 ` Miguel Ojeda
2025-05-20 5:59 ` Viresh Kumar
2025-05-19 7:07 ` [PATCH V12 14/15] rust: opp: Extend OPP abstractions with cpufreq support Viresh Kumar
2025-05-19 7:07 ` [PATCH V12 15/15] cpufreq: Add Rust-based cpufreq-dt driver Viresh Kumar
2025-05-20 6:23 ` [PATCH V12 00/15] Rust abstractions for clk, cpumask, cpufreq, OPP Viresh Kumar
2025-06-05 19:41 ` Andreas Hindborg
2025-06-05 20:12 ` Boqun Feng
2025-06-06 4:20 ` Viresh Kumar
2025-06-06 4:19 ` Viresh Kumar
2025-06-06 10:10 ` Miguel Ojeda
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=aCsQylyW7R5rC15m@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=andrewjballance@gmail.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=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).