linux-kernel - Re: [PATCH v8 1/2] leds: core: Introduce LED pattern trigger

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180912191820.GA27704@amd>
Date:   Wed, 12 Sep 2018 21:18:20 +0200
From:   Pavel Machek <pavel@....cz>
To:     Jacek Anaszewski <jacek.anaszewski@...il.com>
Cc:     Bjorn Andersson <bjorn.andersson@...aro.org>,
        Baolin Wang <baolin.wang@...aro.org>, rteysseyre@...il.com,
        broonie@...nel.org, linus.walleij@...aro.org,
        linux-leds@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v8 1/2] leds: core: Introduce LED pattern trigger

Hi!

> >>> diff --git a/Documentation/ABI/testing/sysfs-class-led-trigger-pattern b/Documentation/ABI/testing/sysfs-class-led-trigger-pattern
> >> [..]
> >>> +What:		/sys/class/leds/<led>/hw_pattern
> >>> +Date:		September 2018
> >>> +KernelVersion:	4.20
> >>> +Description:
> >>> +		Specify a hardware pattern for the LED, for LED hardware that
> >>> +		supports autonomously controlling brightness over time, according
> >>> +		to some preprogrammed hardware patterns.
> >>> +
> >>> +		Since different LED hardware can have different semantics of
> >>> +		hardware patterns, each driver is expected to provide its own
> >>> +		description for the hardware patterns in their ABI documentation
> >>> +		file.
> >>> +
> >>
> >> So, after a full circle we're back at drivers with support for hardware
> >> patterns should have their own ABI for setting that pattern.
> >>
> >> The controls for my hardware is:
> >> * a list of brightness values
> >> * the rate of the pattern
> >> * a flag to indicate that the pattern should be played from start
> >>   to end, end to start or start to end to start
> >> * a boolean indicating if the pattern should be played once or repeated
> >>   indefinitely.
> > 
> > No, we are not back to full circle.
> > 
> > Or at least we should not be.
> > 
> > Yes, hw_pattern can have some limitation pattern does not, but if you
> > take values from hw_pattern file and put them into pattern file, you
> > should get the same pattern (with more power being consumed). And that
> > property is kind of important for me, because it should keep the ABI
> > reasonable.
> 
> If you looked at what we agreed on with Baolin, you'd realize
> that this property is in no way preserved.
> This is what the whole story is about - we're introducing hw_pattern
> because of difficulties in describing breathing pattern by a series
> of [brightness delta_t] tuples.
> 
> And Bjorn presented another example. I'm inclined to leave the
> definition of hw_pattern semantics to the LED class drivers,
> and allow them to create related sysfs files.

Please lets not do that.

We already have drivers that do that and it is complete
nightmare. Some take binary code for the tiny CPU driving the LED.

What exactly is the problem? [brightness delta_t] can describe
anything single LED can do in finite time. You are right, that
[brightness delta_t] sequence may get rather long, and it may be hard
to turn that sequence into parameters. Are there any _interesting_
sequences hardware can do but [brightness delta_t] can not store
reasonably?

Thanks,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)