public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Raphaël Teysseyre" <rteysseyre@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Joe Xue <lgxue@hotmail.com>, Bryan Wu <cooloney@gmail.com>,
	"rpurdie@rpsys.net" <rpurdie@rpsys.net>,
	Linux LED Subsystem <linux-leds@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] leds: Add status code trigger
Date: Wed, 11 Mar 2015 16:10:14 +0100	[thread overview]
Message-ID: <1426086614.59115.14.camel@localhost> (raw)
In-Reply-To: <20150310192226.GB11260@amd>

Le mardi 10 mars 2015 à 20:22 +0100, Pavel Machek a écrit :
> Hi!
> 
> > This patch is very similar to mine patten trigger and all features are covered by my patch.
> > If you are considering to take this feature, could you consider my patch instead?
> > http://thread.gmane.org/gmane.linux.documentation/19116/focus=19135
> 
> That one is indeed better than this patch (as it supports almost
> arbitrary blinking pattern on single LED, it will not help much with
> smooth brightness control.

I agree, that patch supports more features than mine, I didn't find it
while browsing the mailing list archive.

> 
> Would solution below work for you?
> 
> Best regards,
> 									Pavel
> 
> > > I think I have interface to handle most of the issues: array of
> > > integers in "brightness, length in miliseconds".
> > > 
> > > So for example slowly blinking LED would be "0 1000msec, 255 1000
> > > msec". On off pattern would be "0 1000msec, 255 0msec, 255 1000msec, 0
> > > 0msec".
> > > 
> > > Rapahael, this should be able to do all the stuff you want to do. It
> > > can also do morse code, slow blinks, and combination of both. Do you
> > > want to try implementing it?
> >  		 	   		  
> 

I could implement it. This is how I'd do it :
When activated, the trigger would export three
sysfs attributes : pattern, pattern_repeat, and pattern_once.

	pattern : list of brightness/time couple, separated by newlines
		For the slowly blinking LED of your example,
		this attribute would contain :
		0 1000
		255 1000

		For a heartbeat-like pattern :
		0 1000
		255 100
		0 100
		255 100

	pattern_repeat : repeat this pattern indefinitely ?
		1 -> yes, 0 -> no

	pattern_once : if pattern_repeat = 0, writing 1 to this
		file makes the pattern run once .

Does that seem OK to you?

Regards,
Raphaël




  reply	other threads:[~2015-03-11 15:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1424334377.11286.3.camel@localhost>
2015-03-09 21:15 ` [PATCH RFC] leds: Add status code trigger Bryan Wu
2015-03-10  8:00   ` Pavel Machek
     [not found]     ` <BLU172-W3716E59BC9E98F60F424C4AC180@phx.gbl>
2015-03-10 19:22       ` Pavel Machek
2015-03-11 15:10         ` Raphaël Teysseyre [this message]
2015-03-11 19:02           ` Pavel Machek
2015-03-12  6:56             ` Raphaël Teysseyre
2015-03-16 10:06             ` [PATCH] leds: Add arbitrary pattern trigger Raphaël Teysseyre
2015-03-16 11:55               ` Pavel Machek
2015-03-16 16:49                 ` Raphaël Teysseyre
2015-03-16 12:20               ` Pavel Machek
2015-03-16 12:40               ` Paul Bolle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1426086614.59115.14.camel@localhost \
    --to=rteysseyre@gmail.com \
    --cc=cooloney@gmail.com \
    --cc=lgxue@hotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rpurdie@rpsys.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox