Message ID | 20190715155657.22976-2-jjhiblot@ti.com |
---|---|
State | Superseded, archived |
Headers | show |
Series | leds: Add control of the voltage/current regulator to the LED core | expand |
Context | Check | Description |
---|---|---|
robh/checkpatch | success |
JJ On 7/15/19 10:56 AM, Jean-Jacques Hiblot wrote: > Most of the LEDs are powered by a voltage/current regulator. Describing it > in the device-tree makes it possible for the LED core to enable/disable it > when needed. > > Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com> > --- > Documentation/devicetree/bindings/leds/common.txt | 6 ++++++ > 1 file changed, 6 insertions(+) > > diff --git a/Documentation/devicetree/bindings/leds/common.txt b/Documentation/devicetree/bindings/leds/common.txt > index 70876ac11367..539e124b1457 100644 > --- a/Documentation/devicetree/bindings/leds/common.txt > +++ b/Documentation/devicetree/bindings/leds/common.txt > @@ -61,6 +61,11 @@ Optional properties for child nodes: > - panic-indicator : This property specifies that the LED should be used, > if at all possible, as a panic indicator. > > +- power-supply : A voltage/current regulator used to to power the LED. When a Is the phandle to a voltage/current regulator used to to power the LED > + LED is turned off, the LED core disable its regulator. The The regulator is only disabled if it is the only consumer and/or the number of users = 0. > + same regulator can power many LED (or other) devices. It is > + turned off only when all of its users disabled it. > + > - trigger-sources : List of devices which should be used as a source triggering > this LED activity. Some LEDs can be related to a specific > device and should somehow indicate its state. E.g. USB 2.0 > @@ -106,6 +111,7 @@ gpio-leds { > label = "Status"; > linux,default-trigger = "heartbeat"; > gpios = <&gpio0 0 GPIO_ACTIVE_HIGH>; > + power-supply = <&led_regulator>; > }; > > usb { Reviewed-by: Dan Murphy <dmurphy@ti.com>
On Mon 2019-07-15 17:56:56, Jean-Jacques Hiblot wrote: > Most of the LEDs are powered by a voltage/current regulator. Describing it > in the device-tree makes it possible for the LED core to enable/disable it > when needed. > > Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com> Acked-by: Pavel Machek <pavel@ucw.cz>
diff --git a/Documentation/devicetree/bindings/leds/common.txt b/Documentation/devicetree/bindings/leds/common.txt index 70876ac11367..539e124b1457 100644 --- a/Documentation/devicetree/bindings/leds/common.txt +++ b/Documentation/devicetree/bindings/leds/common.txt @@ -61,6 +61,11 @@ Optional properties for child nodes: - panic-indicator : This property specifies that the LED should be used, if at all possible, as a panic indicator. +- power-supply : A voltage/current regulator used to to power the LED. When a + LED is turned off, the LED core disable its regulator. The + same regulator can power many LED (or other) devices. It is + turned off only when all of its users disabled it. + - trigger-sources : List of devices which should be used as a source triggering this LED activity. Some LEDs can be related to a specific device and should somehow indicate its state. E.g. USB 2.0 @@ -106,6 +111,7 @@ gpio-leds { label = "Status"; linux,default-trigger = "heartbeat"; gpios = <&gpio0 0 GPIO_ACTIVE_HIGH>; + power-supply = <&led_regulator>; }; usb {
Most of the LEDs are powered by a voltage/current regulator. Describing it in the device-tree makes it possible for the LED core to enable/disable it when needed. Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com> --- Documentation/devicetree/bindings/leds/common.txt | 6 ++++++ 1 file changed, 6 insertions(+)