From: Pavel Machek <pavel@ucw.cz>
To: Andreas Klinger <ak@it-klinger.de>
Cc: jacek.anaszewski@gmail.com, ben.whitten@gmail.com,
geert+renesas@glider.be, w@1wt.eu, pombredanne@nexb.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: Re: [PATCH] leds: ledtrig-morse: send out morse code
Date: Fri, 29 Jun 2018 09:17:24 +0200 [thread overview]
Message-ID: <20180629071724.GA10079@amd> (raw)
In-Reply-To: <20180629064147.GA3219@arbeit>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
> > Yeah, well... I don't think decoding sentences in morse code is going
> > to be much fun.
> >
> > And we don't really want encoder in kernel. Just do encoding in
> > userspace, and use pattern trigger to display it.
> >
> > For many uses, morse code is "too geeky", and other patterns will be
> > used.
> >
> > Like " X " for error 1, " X X " for error 2, " .xX .xX " for
> > charging, " .xXx. " for everything okay...
> >
>
> The hardware i'm using is not able to adjust brightness. It can just switch the
> LED on or off. That's it.
>
> If anybody is interested i can submit a version 2 of the morse trigger with the
> improvements suggested by Greg and Geert. Please let me know.
I'd prefer more general pattern trigger.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-06-29 7:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 13:42 [PATCH] leds: ledtrig-morse: send out morse code Andreas Klinger
2018-06-28 13:54 ` Greg KH
2018-06-28 15:36 ` Geert Uytterhoeven
2018-06-28 18:21 ` Willy Tarreau
2018-06-28 18:56 ` Pavel Machek
2018-06-28 20:29 ` Andreas Klinger
2018-06-28 20:45 ` Pavel Machek
2018-06-29 6:41 ` Andreas Klinger
2018-06-29 7:17 ` Pavel Machek [this message]
2018-06-29 7:21 ` Geert Uytterhoeven
2018-06-29 7:29 ` Pavel Machek
2018-06-29 7:48 ` Geert Uytterhoeven
2018-06-29 8:07 ` Pavel Machek
2018-06-29 8:24 ` Greg KH
2018-06-29 9:23 ` Pavel Machek
2018-06-28 20:33 ` Andreas Klinger
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=20180629071724.GA10079@amd \
--to=pavel@ucw.cz \
--cc=ak@it-klinger.de \
--cc=ben.whitten@gmail.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pombredanne@nexb.com \
--cc=w@1wt.eu \
/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;
as well as URLs for NNTP newsgroup(s).