| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CABa6EMYdY9WBN0+edgcEFc0uiBmWUDert7nXCN+FWeRMG=0S6A@mail.gmail.com>
Date: Thu, 13 May 2021 15:47:19 -0500
From: Doug Zobel <dougdev334@...il.com>
To: Rob Herring <robh@...nel.org>
Cc: Pavel Machek <pavel@....cz>,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
linux-leds@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] dt: bindings: lp55xx: Add predefined LED pattern
Sorry for the re-send. I didn't realize gmail was sending everything
HTML encoded.
On Wed, May 12, 2021 at 9:20 PM Rob Herring <robh@...nel.org> wrote:
>
> On Tue, May 11, 2021 at 03:48:34PM -0500, Doug Zobel wrote:
> > Add a new device tree object for LP5562 predfined led patterns.
>
> If you are going to define something generic looking, put it in a
> generic binding.
I'm not clear on what this would be. After re-running the
dt_binding_check with DT_CHECKER_FLAGS=-m, I see that the pattern
object definitions I have won't work since the numbering conflicts
with the existing led objects. I was going to move these patterns
under a new 'predefine-patterns' object. Is this what you mean by a
'generic binding'?
> I don't know that this belongs in DT though. Won't a user want to create
> their own patterns? That means there should be a sysfs interface (which
> we either already have or has been attempted IIRC).
Yes, there is a sysfs interface for running patterns via the firmware
loading interface. The firmware loading interface doesn't seem well
suited for constantly changing the pattern that the LED driver runs.
I found it to be slow and unreliable when quickly changing the LED
pattern. The existing predef pattern functionality works much better.
Unfortunately the only way to define the patterns for it is via the
platform data structure. Adding the predef patterns to the device
tree seemed like a good way to make use of the existing functionality
in the driver.
> >
> > Signed-off-by: Doug Zobel <dougdev334@...il.com>
> > ---
> > .../devicetree/bindings/leds/leds-lp55xx.yaml | 103 +++++++++++++++++-
> > 1 file changed, 102 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/devicetree/bindings/leds/leds-lp55xx.yaml b/Documentation/devicetree/bindings/leds/leds-lp55xx.yaml
> > index f552cd143d5b..2524a84fe688 100644
> > --- a/Documentation/devicetree/bindings/leds/leds-lp55xx.yaml
> > +++ b/Documentation/devicetree/bindings/leds/leds-lp55xx.yaml
> > @@ -100,6 +100,31 @@ patternProperties:
> > $ref: /schemas/types.yaml#/definitions/string
> > description: name of channel
> >
> > + "(^pattern@[0-9a-f]$|pattern)":
> > + type: object
> > + $ref: common.yaml#
> > + description: |
> > + LP5562 sepcific object. LED pattern program saved to and run on LP5562.
> > + properties:
> > + pat-name:
> > + $ref: /schemas/types.yaml#/definitions/string
> > + description: Name of pattern program
> > +
> > + pat-r:
> > + $ref: /schemas/types.yaml#/definitions/uint8-array
> > + description: |
> > + Program data for red channel. See LP5562 datasheet for program format specification.
> > +
> > + pat-g:
> > + $ref: /schemas/types.yaml#/definitions/uint8-array
> > + description: |
> > + Program data for green channel. See LP5562 datasheet for program format specification.
> > +
> > + pat-b:
> > + $ref: /schemas/types.yaml#/definitions/uint8-array
> > + description: |
> > + Program data for blue channel. See LP5562 datasheet for program format specification.
> > +
> > required:
> > - compatible
> > - reg
> > @@ -223,6 +248,82 @@ examples:
> > };
> > };
> > };
> > - };
> >
> > + led-controller@30 {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > + compatible = "ti,lp5562";
> > + reg = <0x30>;
> > +
> > + led@0 {
> > + reg = <0>;
> > + chan-name = "red";
> > + color = <LED_COLOR_ID_RED>;
> > + };
> > +
> > + led@1 {
> > + reg = <1>;
> > + chan-name = "green";
> > + color = <LED_COLOR_ID_GREEN>;
> > + };
> > +
> > + led@2 {
> > + reg = <2>;
> > + chan-name = "blue";
> > + color = <LED_COLOR_ID_BLUE>;
> > + };
> > +
> > + pattern@1 {
> > + /* Pulsing blue pattern
> > + * Blue:
> > + * 027F: Ramp up 50%
> > + * 027F: Ramp up 50%
> > + * 4600: Wait 100ms
> > + * 02FF: Ramp down 50%
> > + * 02FF: Ramp down 50%
> > + * 4600: Wait 100ms
> > + * 0000: Goto start
> > + */
> > + pat-name = "Pulsing Blue";
> > + pat-b = [02 7f 02 7f 46 00 02 ff 02 ff 46 00 00 00];
> > + };
> > +
> > + pattern@2 {
> > + /*
> > + * HSV rainbow
> > + * Red:
> > + * 40FF: Set PWM 255
> > + * 41FF: Ramp down 50%
> > + * 41FF: Ramp down 50%
> > + * 41FF: Wait 1/2 ramp time
> > + * 41FF: Wait 1/2 ramp time
> > + * 417F: Ramp up 50%
> > + * 417F: Ramp up 50%
> > + * 0000: Goto start
> > + * Green:
> > + * 4000: Set PWM 0
> > + * 417F: Ramp up 50%
> > + * 417F: Ramp up 50%
> > + * 41FF: Ramp down 50%
> > + * 41FF: Ramp down 50%
> > + * 41FF: Wait 1/2 ramp time
> > + * 41FF: Wait 1/2 ramp time
> > + * 0000: Goto start
> > + * Blue:
> > + * 4000: Set PWM 0
> > + * 41FF: Wait 1/2 ramp time
> > + * 41FF: Wait 1/2 ramp time
> > + * 417F: Ramp up 50%
> > + * 417F: Ramp up 50%
> > + * 41FF: Ramp down 50%
> > + * 41FF: Ramp down 50%
> > + * 0000: Goto start
> > + */
> > + pat-name = "HSV Rainbow";
> > + pat-r = [40 ff 41 FF 41 FF 41 FF 41 FF 41 7F 41 7F 00 00];
> > + pat-g = [40 00 41 7F 41 7F 41 FF 41 FF 41 FF 41 FF 00 00];
> > + pat-b = [40 00 41 FF 41 FF 41 7F 41 7F 41 FF 41 FF 00 00];
> > + };
> > + };
> > + };
> > ...
> > --
> > 2.20.1
> >
Powered by blists - more mailing lists