From: Markus Probst <markus.probst@posteo.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Miguel Ojeda <ojeda@kernel.org>,
Alex Gaynor <alex.gaynor@gmail.com>,
Danilo Krummrich <dakr@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Lee Jones <lee@kernel.org>, Pavel Machek <pavel@kernel.org>
Cc: "Dave Ertman" <david.m.ertman@intel.com>,
"Ira Weiny" <ira.weiny@intel.com>,
"Leon Romanovsky" <leon@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
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>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
rust-for-linux@vger.kernel.org, linux-leds@vger.kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/2] rust: leds: add led classdev abstractions
Date: Thu, 13 Nov 2025 14:20:28 +0000 [thread overview]
Message-ID: <bf4192fd466571f798023b70c3e83e19448d8149.camel@posteo.de> (raw)
In-Reply-To: <20251027200547.1038967-1-markus.probst@posteo.de>
On Mon, 2025-10-27 at 20:06 +0000, Markus Probst wrote:
> This patch series has previously been contained in
> https://lore.kernel.org/rust-for-linux/20251008181027.662616-1-markus.probst@posteo.de/T/#t
> which added a rust written led driver for a microcontroller via i2c.
>
> As the reading and writing to the i2c client via the register!
> macro has not been implemented yet [1], the patch series will only
> contain the additional abstractions required.
>
> [1] https://lore.kernel.org/rust-for-linux/DDDS2V0V2NVJ.16ZKXCKUA1HUV@kernel.org/
>
> The following changes were made:
> * add abstraction to convert a device reference to a bus device
> reference for use in class device callbacks
>
> * add basic led classdev abstractions to register and unregister leds
>
> Changes since v6:
> * fixed typos
> * improved documentation
>
> Changes since v5:
> * rename `IntoBusDevice` trait into `AsBusDevice`
> * fix documentation about `LedOps::BLOCKING`
> * removed dependency on i2c bindings
> * added `AsBusDevice` implementation for `platform::Device`
> * removed `device::Device` fallback implementation
> * document that `AsBusDevice` must not be used by drivers and is
> intended for bus and class device abstractions only.
>
> Changes since v4:
> * add abstraction to convert a device reference to a bus device
> reference
> * require the bus device as parent device and provide it in class device
> callbacks
> * remove Pin<Vec<_>> abstraction (as not relevant for the led
> abstractions)
> * fixed formatting in `led::Device::new`
> * fixed `LedOps::BLOCKING` did the inverse effect
>
> Changes since v3:
> * fixed kunit tests failing because of example in documentation
>
> Changes since v2:
> * return `Devres` on `led::Device` creation
> * replace KBox<T> with T in struct definition
> * increment and decrement reference-count of fwnode
> * make a device parent mandatory for led classdev creation
> * rename `led::Handler` to `led::LedOps`
> * add optional `brightness_get` function to `led::LedOps`
> * use `#[vtable]` instead of `const BLINK: bool`
> * use `Opaque::cast_from` instead of casting a pointer
> * improve documentation
> * improve support for older rust versions
> * use `&Device<Bound>` for parent
>
> Changes since v1:
> * fixed typos noticed by Onur Özkan
>
> Markus Probst (2):
> rust: Add trait to convert a device reference to a bus device
> reference
> rust: leds: add basic led classdev abstractions
>
> Markus Probst (2):
> rust: Add trait to convert a device reference to a bus device
> reference
> rust: leds: add basic led classdev abstractions
Hi,
So you know in advance, I will add a 3. patch for multicolor led
classdev abstractions (drivers/leds/led-class-multicolor.c,
include/linux/led-class-multicolor.h) to this patch series.
In the atmega1608 led driver (the user of these abstractions) there are
leds with different colors that share the same slot.
Technically "drivers/leds/rgb/leds-group-multicolor.c" could be used in
combination with single color leds instead, but then hardware
accelerated blinking wouldn't be supported. I think it would make more
sense to directly implement it in the driver.
The existing 2 patches shouldn't change, so feel free to review them.
Thanks
- Markus Probst
>
> rust/kernel/auxiliary.rs | 7 +
> rust/kernel/device.rs | 33 ++++
> rust/kernel/led.rs | 375 +++++++++++++++++++++++++++++++++++++++
> rust/kernel/lib.rs | 1 +
> rust/kernel/pci.rs | 7 +
> rust/kernel/platform.rs | 7 +
> rust/kernel/usb.rs | 6 +
> 7 files changed, 436 insertions(+)
> create mode 100644 rust/kernel/led.rs
next prev parent reply other threads:[~2025-11-13 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 20:06 [PATCH v7 0/2] rust: leds: add led classdev abstractions Markus Probst
2025-10-27 20:06 ` [PATCH v7 1/2] rust: Add trait to convert a device reference to a bus device reference Markus Probst
2025-11-17 22:04 ` Danilo Krummrich
2025-10-27 20:06 ` [PATCH v7 2/2] rust: leds: add basic led classdev abstractions Markus Probst
2025-10-30 10:52 ` [PATCH v7 0/2] rust: leds: add " Danilo Krummrich
2025-10-30 18:07 ` Markus Probst
2025-10-31 13:18 ` Miguel Ojeda
2025-11-08 14:49 ` Markus Probst
2025-11-09 10:25 ` Miguel Ojeda
2025-11-10 13:40 ` Lee Jones
2025-11-13 14:17 ` Markus Probst
2025-11-13 14:20 ` Markus Probst [this message]
2025-11-13 14:43 ` Markus Probst
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=bf4192fd466571f798023b70c3e83e19448d8149.camel@posteo.de \
--to=markus.probst@posteo.de \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=david.m.ertman@intel.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=ira.weiny@intel.com \
--cc=kwilczynski@kernel.org \
--cc=lee@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=pavel@kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.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;
as well as URLs for NNTP newsgroup(s).