From: Daniel Almeida <daniel.almeida@collabora.com>
To: "Michael Turquette" <mturquette@baylibre.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" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Viresh Kumar" <viresh.kumar@linaro.org>
Cc: Alexandre Courbot <acourbot@nvidia.com>,
linux-clk@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH] rust: clk: use the type-state pattern
Date: Wed, 30 Jul 2025 10:52:55 -0300 [thread overview]
Message-ID: <6EDE1C11-8654-404D-98AC-0D102090C15F@collabora.com> (raw)
In-Reply-To: <20250729-clk-type-state-v1-1-896b53816f7b@collabora.com>
[…]
> }
>
> - /// Enable the clock.
> + /// Attempts to convert the [`Clk`] to a [`Prepared`] state.
> ///
> - /// Equivalent to the kernel's [`clk_enable`] API.
> + /// Equivalent to the kernel's [`clk_prepare`] API.
> ///
> - /// [`clk_enable`]: https://docs.kernel.org/core-api/kernel-api.html#c.clk_enable
> + /// [`clk_prepare`]: https://docs.kernel.org/core-api/kernel-api.html#c.clk_prepare
> #[inline]
> - pub fn enable(&self) -> Result {
> - // SAFETY: By the type invariants, self.as_raw() is a valid argument for
> - // [`clk_enable`].
> - to_result(unsafe { bindings::clk_enable(self.as_raw()) })
> + pub fn prepare(self) -> Result<Clk<Prepared>, Error<Unprepared>> {
> + // We will be transferring the ownership of our `clk_get()` count to
> + // `Clk<Prepared>`.
> + let clk = ManuallyDrop::new(self);
> +
> + // SAFETY: By the type invariants, self.0 is a valid argument for [`clk_prepare`].
I just noticed that some comments still refer to the old “self.0” field, but that doesn’t exist anymore.
I’ll fix that in v2.
> + to_result(unsafe { bindings::clk_prepare(clk.as_raw()) })
> + .map(|()| Clk {
> + inner: clk.inner,
> + _phantom: PhantomData,
> + })
> + .map_err(|error| Error {
> + error,
> + clk: ManuallyDrop::into_inner(clk),
> + })
> }
> + }
>
— Daniel
prev parent reply other threads:[~2025-07-30 13:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 21:38 [PATCH] rust: clk: use the type-state pattern Daniel Almeida
2025-07-30 6:23 ` Viresh Kumar
2025-07-30 12:27 ` Daniel Almeida
2025-07-30 14:48 ` Viresh Kumar
2025-07-30 7:29 ` Daniel Sedlak
2025-07-30 8:20 ` Benno Lossin
2025-07-30 12:59 ` Daniel Almeida
2025-07-30 13:27 ` Daniel Sedlak
2025-07-30 13:30 ` Daniel Almeida
2025-07-30 13:39 ` Alice Ryhl
2025-07-30 13:45 ` Daniel Almeida
2025-07-30 8:29 ` Danilo Krummrich
2025-07-30 12:25 ` Daniel Almeida
2025-07-30 8:03 ` Danilo Krummrich
2025-07-30 12:13 ` Daniel Almeida
2025-07-30 12:24 ` Danilo Krummrich
2025-07-30 13:52 ` Daniel Almeida [this message]
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=6EDE1C11-8654-404D-98AC-0D102090C15F@collabora.com \
--to=daniel.almeida@collabora.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=mturquette@baylibre.com \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tmgross@umich.edu \
--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