From: Michal Wilczynski <m.wilczynski@samsung.com>
To: Daniel Almeida <daniel.almeida@collabora.com>
Cc: "Uwe Kleine-König" <ukleinek@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>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Drew Fustini" <drew@pdp7.com>, "Guo Ren" <guoren@kernel.org>,
"Fu Wei" <wefu@redhat.com>, "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Benno Lossin" <lossin@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Drew Fustini" <fustini@kernel.org>,
linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org,
rust-for-linux@vger.kernel.org, linux-riscv@lists.infradead.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v12 2/3] rust: pwm: Add Kconfig and basic data structures
Date: Sat, 2 Aug 2025 23:19:40 +0200 [thread overview]
Message-ID: <8a99664b-8acb-4ace-9c2a-bdada5cac5cb@samsung.com> (raw)
In-Reply-To: <437DA583-95FF-4ADF-9947-1F39D242E157@collabora.com>
On 7/25/25 17:08, Daniel Almeida wrote:
> Hi Michal,
>
>
> Overall looks good, a few minor comments:
Hi,
Congratulations for getting your IoMem series merged. Thank you for your
work, as it will allow me to proceed and re-add the driver part for this
series.
>
> […]
>
>> +
>> +/// Wrapper for board-dependent PWM arguments [`struct pwm_args`](srctree/include/linux/pwm.h).
>> +#[repr(transparent)]
>> +pub struct Args(Opaque<bindings::pwm_args>);
>> +
>> +impl Args {
>> + /// Creates an `Args` wrapper from a C struct pointer.
>> + ///
>> + /// # Safety
>> + ///
>> + /// The caller must ensure that `c_args_ptr` is a valid, non-null pointer
>> + /// to `bindings::pwm_args` and that the pointed-to data is valid
>> + /// for the duration of this function call (as data is copied).
>> + unsafe fn from_c_ptr(c_args_ptr: *const bindings::pwm_args) -> Self {
>> + // SAFETY: Caller guarantees `c_args_ptr` is valid. We dereference it to copy.
>> + Args(Opaque::new(unsafe { *c_args_ptr }))
>> + }
>
> from_raw()
>
>
>> +
>> + /// Returns the period of the PWM signal in nanoseconds.
>> + pub fn period(&self) -> u64 {
>> + // SAFETY: `self.0.get()` returns a pointer to the `bindings::pwm_args`
>> + // managed by the `Opaque` wrapper. This pointer is guaranteed to be
>> + // valid and aligned for the lifetime of `self` because `Opaque` owns a copy.
>> + unsafe { (*self.0.get()).period }
>> + }
>> +
>> + /// Returns the polarity of the PWM signal.
>> + pub fn polarity(&self) -> Result<Polarity, Error> {
>> + // SAFETY: `self.0.get()` returns a pointer to the `bindings::pwm_args`
>> + // managed by the `Opaque` wrapper. This pointer is guaranteed to be
>> + // valid and aligned for the lifetime of `self`.
>> + let raw_polarity = unsafe { (*self.0.get()).polarity };
>> + Polarity::try_from(raw_polarity)
>> + }
>> +}
>> +
>> +/// Wrapper for PWM state [`struct pwm_state`](srctree/include/linux/pwm.h).
>> +#[repr(transparent)]
>> +pub struct State(bindings::pwm_state);
>
> No Opaque<T>?
Since this is a copy of the state it's fine. The Args above should
follow similar pattern, the divergence stemmed when iterating with this
series. So I would rather fix the Args to also not be Opaque as it
doesn't need to be, since it's also a copy of the original (since it's
so small and read only).
>
>> +
>> +impl State {
>> + /// Creates a `State` wrapper by taking ownership of a C `pwm_state` value.
>> + pub(crate) fn from_c(c_state: bindings::pwm_state) -> Self {
>> + State(c_state)
>> + }
>> +
>> + /// Returns `true` if the PWM signal is enabled.
>> + pub fn enabled(&self) -> bool {
>> + self.0.enabled
>> + }
>> +}
>>
>> --
>> 2.34.1
>>
>>
>
> If the lack of Opaque<T> is not a problem for whatever reason:
>
> Reviewed-by: Daniel Almeida <daniel.almeida@collabora.com>
>
> — Daniel
>
>
Best regards,
--
Michal Wilczynski <m.wilczynski@samsung.com>
next prev parent reply other threads:[~2025-08-02 21:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250717090829eucas1p2b87fb2b5115e17e740321344a116b206@eucas1p2.samsung.com>
2025-07-17 9:08 ` [PATCH v12 0/3] Rust Abstractions for PWM subsystem with TH1520 PWM driver Michal Wilczynski
[not found] ` <CGME20250717090830eucas1p191fbd4e0baa40468884307a1b6277be3@eucas1p1.samsung.com>
2025-07-17 9:08 ` [PATCH v12 1/3] pwm: Export `pwmchip_release` for external use Michal Wilczynski
[not found] ` <CGME20250717090831eucas1p282ac3df2e2f1fc2a46e12c440abfbba1@eucas1p2.samsung.com>
2025-07-17 9:08 ` [PATCH v12 2/3] rust: pwm: Add Kconfig and basic data structures Michal Wilczynski
2025-07-25 15:08 ` Daniel Almeida
2025-08-02 21:19 ` Michal Wilczynski [this message]
[not found] ` <CGME20250717090833eucas1p16c916450b59a77d81bd013527755cb21@eucas1p1.samsung.com>
2025-07-17 9:08 ` [PATCH v12 3/3] rust: pwm: Add complete abstraction layer Michal Wilczynski
2025-07-25 15:56 ` Daniel Almeida
2025-08-04 22:29 ` Michal Wilczynski
2025-08-04 23:09 ` Miguel Ojeda
2025-08-06 12:49 ` Daniel Almeida
2025-08-12 9:27 ` Michal Wilczynski
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=8a99664b-8acb-4ace-9c2a-bdada5cac5cb@samsung.com \
--to=m.wilczynski@samsung.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=alex@ghiti.fr \
--cc=aliceryhl@google.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=conor+dt@kernel.org \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=drew@pdp7.com \
--cc=fustini@kernel.org \
--cc=gary@garyguo.net \
--cc=guoren@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lossin@kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mturquette@baylibre.com \
--cc=ojeda@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=ukleinek@kernel.org \
--cc=wefu@redhat.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
all inboxes | Powered by JetHome®