u-boot.git/drivers/led, branch v2024.07

Revert "Merge patch series "arm: dts: am62-beagleplay: Fix Beagleplay Ethernet""

2024-05-19T14:16:36+00:00

When bringing in the series 'arm: dts: am62-beagleplay: Fix Beagleplay
Ethernet"' I failed to notice that b4 noticed it was based on next and
so took that as the base commit and merged that part of next to master.

This reverts commit c8ffd1356d42223cbb8c86280a083cc3c93e6426, reversing
changes made to 2ee6f3a5f7550de3599faef9704e166e5dcace35.

Reported-by: Jonas Karlman 
Signed-off-by: Tom Rini

led: Remove and add needed includes

2024-05-07T14:00:55+00:00

Remove  from this driver directory and when needed
add missing include files directly.

Signed-off-by: Tom Rini

common: Convert *.c/h from UTF-8 to ASCII enconfing

2024-04-22T17:01:48+00:00

Convert UTF-8 chars to ASCII in cases where make sense. No Copyright or
names are converted.

Signed-off-by: Michal Simek 
Reviewed-by: Tom Rini 
Acked-by: Marek Behún

led: add TI LP5562 LED driver

2023-12-13T16:35:16+00:00

Driver for the TI LP5562 4 channel LED controller. Supports
independent on/off control of all 4 channels. Supports LED_BLINK on 3
independent channels: blue/green/red. The white channel can blink, but
shares the blue channel blink rate.

Heavily based on patch originally from Doug Zobel [1].

I have modified it so it matches the DT bindings in the linux tree,
and also follows the linux driver implementation more closely. This
should address Tom's concerns, and also matches my goal of making the
U-Boot driver work with our existing .dts which is known to work in
linux.

As our boards only have the R,G,B outputs connected, I have not
actually tested how the white channel behaves, but the R,G,B work
exactly as expected.

[1] https://lore.kernel.org/u-boot/1547150757-1561-1-git-send-email-douglas.zobel@climate.com/

Cc: Doug Zobel 
Signed-off-by: Rasmus Villemoes

led: led_pwm: use led_bind_generic() helper

2023-12-13T16:35:15+00:00

Use the helper led_bind_generic() to reduce code duplication.

Signed-off-by: Rasmus Villemoes 
Reviewed-by: Christian Gmeiner

led: led_gpio: use led_bind_generic() helper

2023-12-13T16:35:15+00:00

Use the helper led_bind_generic() to reduce code duplication.

Signed-off-by: Rasmus Villemoes 
Reviewed-by: Christian Gmeiner

led: introduce led_bind_generic()

2023-12-13T16:35:13+00:00

All existing drivers in drivers/led/ contain a .bind method that does
exactly the same thing, with just the actual driver name
differing. Create a helper so all those individual methods can be
changed to one-liners.

Reviewed-by: Marek Vasut 
Signed-off-by: Rasmus Villemoes

led-uclass: do not create fallback label for top-level node

2023-12-13T16:34:53+00:00

Many existing drivers, and led-uclass itself, rely on uc_plat->label
being NULL for the device representing the top node, as opposed to the
child nodes representing individual LEDs. This means that the drivers
whose .probe methods rely on this were broken by commit 83c63f0d1185
("led: Move OF "label" property parsing to core"), and also that the top
node wrongly shows up with 'led list'.

Binding the same driver to the top node as to the individual child
nodes is arguably wrong, and the approach of using a UCLASS_NOP driver
for the top node is probably better - this has for example been done in
commit 01074697801b ("led: gpio: Use NOP uclass driver for top-level
node") and commit 910b01c27c04 ("drivers: led: bcm6753: do not use null
label to find the top")

Until remaining affected drivers are fixed, we can use a heuristic
that only sets the label to the fallback value derived from the node
name if the node does not have a "compatible" property - i.e., if it
has been bound to the LED driver explicitly via
device_bind_driver_to_node(). This is similar to what commit
e3aa76644c2a ("led: gpio: Check device compatible string to determine
the top level node") did for gpio_led, but that fix was then supplanted
by commit 01074697801b ("led: gpio: Use NOP uclass driver for top-level
node")

Fixes: 83c63f0d1185 ("led: Move OF "label" property parsing to core")
Signed-off-by: Rasmus Villemoes

led-uclass: honour ->label field populated by driver's own .bind

2023-12-13T16:34:49+00:00

If the driver's own .bind method has populated uc_plat->label, don't
override that. This is necessary for an upcoming driver for ti,lp5562,
where the DT binding unfortunately says to use "chan-name" and not
"label".

Reviewed-by: Christian Gmeiner 
Reviewed-by: Marek Vasut 
Signed-off-by: Rasmus Villemoes

drivers: led: bcm6858: do not use null label to find the top

2023-07-25T16:44:46+00:00

This driver considers that a node with an empty label is the top.
But the led class has changed, if a label is not provided for a led,
the label is filed with the node name. So we update this driver
to use a wrapper to manage the top led node.

Signed-off-by: Philippe Reynes