From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Alex Gaynor" <alex.gaynor@gmail.com>,
"Alice Ryhl" <aliceryhl@google.com>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Benno Lossin" <benno.lossin@proton.me>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Michael Turquette" <mturquette@baylibre.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Stephen Boyd" <sboyd@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Russell King <linux@armlinux.org.uk>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org
Subject: [PATCH V2 0/2] rust: Add basic clock bindings
Date: Fri, 21 Feb 2025 12:03:37 +0530 [thread overview]
Message-ID: <cover.1740118863.git.viresh.kumar@linaro.org> (raw)
Hello,
This adds initial bindings for the clk APIs. These provide the minimal
functionality needed for common use cases, making them straightforward
to introduce in the first iteration.
These will be used by Rust based cpufreq / OPP layers to begin with.
For now I have added them under the maintainership umbrella of the common clk
framework, please let me know if I should do it differently.
This was posted earlier as part of the series implementing cpufreq/OPP Rust
bindings [1] (since its V6 version). In order to make sure this gets properly
reviewed and I don't accidentally miss relevant reviewers, I am posting it
separately now.
If possible, I would like to get these merged via the PM tree along with
cpufreq/OPP bindings, but its okay otherwise too.
--
Viresh
[1] https://lore.kernel.org/all/cover.1738832118.git.viresh.kumar@linaro.org/
V1->V2:
- Post this as an independent series.
- Include more APIs, apart from clk_get() and clk_put().
Viresh Kumar (2):
rust: Add clk helpers
rust: Add basic bindings for clk APIs
MAINTAINERS | 2 +
rust/bindings/bindings_helper.h | 1 +
rust/helpers/clk.c | 57 +++++++++++++++++
rust/helpers/helpers.c | 1 +
rust/kernel/clk.rs | 104 ++++++++++++++++++++++++++++++++
rust/kernel/lib.rs | 1 +
6 files changed, 166 insertions(+)
create mode 100644 rust/helpers/clk.c
create mode 100644 rust/kernel/clk.rs
--
2.31.1.272.g89b43f80a514
next reply other threads:[~2025-02-21 6:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 6:33 Viresh Kumar [this message]
2025-02-21 6:33 ` [PATCH V2 1/2] rust: Add clk helpers Viresh Kumar
2025-02-21 13:19 ` Daniel Almeida
2025-02-21 6:33 ` [PATCH V2 2/2] rust: Add basic bindings for clk APIs Viresh Kumar
2025-02-21 13:30 ` Daniel Almeida
2025-02-21 13:56 ` Danilo Krummrich
2025-02-21 14:29 ` Daniel Almeida
2025-02-21 14:47 ` Danilo Krummrich
2025-02-21 15:28 ` Sebastian Reichel
2025-02-21 21:59 ` Rob Herring
2025-02-24 9:59 ` Viresh Kumar
2025-03-05 20:09 ` Rob Herring
2025-03-06 4:48 ` Viresh Kumar
2025-02-24 9:45 ` Viresh Kumar
2025-02-21 14:42 ` Daniel Almeida
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=cover.1740118863.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=a.hindborg@kernel.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=gary@garyguo.net \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mturquette@baylibre.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tmgross@umich.edu \
/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