[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180714212033.GA31950@amd>
Date: Sat, 14 Jul 2018 23:20:33 +0200
From: Pavel Machek <pavel@....cz>
To: Baolin Wang <baolin.wang@...aro.org>
Cc: Jacek Anaszewski <jacek.anaszewski@...il.com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Mark Brown <broonie@...nel.org>,
Linux LED Subsystem <linux-leds@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 1/2] leds: core: Introduce generic pattern interface
Hi!
> > It also drew my attention to the issue of desired pattern sysfs
> > interface semantics on uninitialized pattern. In your implementation
> > user seems to be unable to determine if the pattern is activated
> > or not. We should define the semantics for this use case and
> > describe it in the documentation. Possibly pattern could
> > return alone new line character then.
Let me take a step back: we have triggers.. like LED blinking.
How is that going to interact with patterns? We probably want the
patterns to be ignored in that case...?
Which suggest to me that we should treat patterns as a trigger. I
believe we do something similar with blinking already.
Then it is easy to determine if pattern is active, and pattern
vs. trigger issue is solved automatically.
Best regards,
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)
Powered by blists - more mailing lists