From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [PATCH] leds: ledtrig-morse: send out morse code Date: Fri, 29 Jun 2018 09:29:12 +0200 Message-ID: <20180629072912.GB10079@amd> References: <20180628134227.GA1719@arbeit> <20180628185630.GA6095@amd> <20180628202955.GA1534@imap.1und1.de> <20180628204516.GA29146@amd> <20180629064147.GA3219@arbeit> <20180629071724.GA10079@amd> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KFztAG8eRSV9hGtP" Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Geert Uytterhoeven Cc: Andreas Klinger , Jacek Anaszewski , Ben Whitten , Geert Uytterhoeven , Willy Tarreau , Philippe Ombredanne , Greg KH , Linux Kernel Mailing List , linux-leds@vger.kernel.org List-Id: linux-leds@vger.kernel.org --KFztAG8eRSV9hGtP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri 2018-06-29 09:21:24, Geert Uytterhoeven wrote: > Hi Pavel, >=20 > On Fri, Jun 29, 2018 at 9:17 AM Pavel Machek wrote: > > > > Yeah, well... I don't think decoding sentences in morse code is goi= ng > > > > 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 trigge= r with the > > > improvements suggested by Greg and Geert. Please let me know. > > > > I'd prefer more general pattern trigger. >=20 > There are two parts here: > 1. The general pattern trigger (which is not yet upstream), > 2. A way to supply a string, convert it into morse code, and feed it to > the LED subsystem. >=20 > Given 1 is not yet upstream, I think Andreas solution is fine. > Once 1 is upstream, 2 can be modified to feed into 1, if available. There's no reason 2. should be in kernel ("mechanism, not policy"). Given 1. is not really more complicated than the morse trigger... please just help with pattern trigger if you want this to happen. Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --KFztAG8eRSV9hGtP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAls138gACgkQMOfwapXb+vI9qwCgkOLyrjQtpTdr4NQ1mNsrVbnz +ggAn1SEUlfJuMI6urjJhj+lEAvSgRQ0 =6+sG -----END PGP SIGNATURE----- --KFztAG8eRSV9hGtP--