[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6db92ee3e66a45338c187ad575a759c2@AcuMS.aculab.com>
Date: Thu, 5 Jul 2018 10:56:46 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Pavel Machek' <pavel@....cz>, Willy Tarreau <w@....eu>
CC: Andreas Klinger <ak@...klinger.de>,
"jacek.anaszewski@...il.com" <jacek.anaszewski@...il.com>,
"ben.whitten@...il.com" <ben.whitten@...il.com>,
"geert+renesas@...der.be" <geert+renesas@...der.be>,
"pombredanne@...b.com" <pombredanne@...b.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-leds@...r.kernel.org" <linux-leds@...r.kernel.org>
Subject: RE: [PATCH v2] leds: ledtrig-morse: send out morse code
...
> > Well, just like we have LED and LED triggers in the kernel, I think having
> > a generic way to use patterns could be nice and in this case Morse could be
> > one such pattern, but if that means it's limited to userland to configure
> > it then it sadly voids all of its benefits.
I've been involved in a system that used morse for short error messages.
Unless you actually know morse it is completely hopeless.
With two leds next to each other you should be able to generate
a lot of easily identifiable patterns by repeating separate 4-bit
patterns (in sync) on both leds (at about 2Hz update).
David
Powered by blists - more mailing lists