From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753965Ab3L0Abm (ORCPT ); Thu, 26 Dec 2013 19:31:42 -0500 Received: from blu0-omc4-s27.blu0.hotmail.com ([65.55.111.166]:7295 "EHLO blu0-omc4-s27.blu0.hotmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751229Ab3L0Abl convert rfc822-to-8bit (ORCPT ); Thu, 26 Dec 2013 19:31:41 -0500 X-TMN: [1r7GzfZhq5k/5td0g0WdvDKstvTFFvZv] X-Originating-Email: [lgxue@hotmail.com] Message-ID: From: Joe Xue To: Pavel Machek CC: "cooloney@gmail.com" , "rpurdie@rpsys.net" , "rob@landley.net" , "milo.kim@ti.com" , "linux-leds@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-doc@vger.kernel.org" Subject: RE: [PATCH] Add the LED burst trigger Date: Thu, 26 Dec 2013 19:31:40 -0500 Importance: Normal In-Reply-To: <20131226142607.GA15225@amd.pavel.ucw.cz> References: <1387895407-28031-1-git-send-email-lgxue@hotmail.com>,<20131225230935.GB13593@amd.pavel.ucw.cz>,,<20131226142607.GA15225@amd.pavel.ucw.cz> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 X-OriginalArrivalTime: 27 Dec 2013 00:31:40.0527 (UTC) FILETIME=[02AF67F0:01CF029B] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, I'm writing the Morse code trigger. what about this echo "-.-. *"> patten -              a long on then a off .              a short on then a off space     a long off *             mean repeat the patten s             mean indicate the patten just one time then stop Do we also need a "step_length_ms" as Pavel's suggestion? If so, we can define long on as 2*step_length_ms and short on as 1*step_length_ms. Any other parameters do you guys think we should add? Any suggestion is very appreciated. Thanks Joe ---------------------------------------- > Date: Thu, 26 Dec 2013 15:26:08 +0100 > From: pavel@ucw.cz > To: lgxue@hotmail.com > CC: cooloney@gmail.com; rpurdie@rpsys.net; rob@landley.net; milo.kim@ti.com; linux-leds@vger.kernel.org; linux-kernel@vger.kernel.org; linux-doc@vger.kernel.org > Subject: Re: [PATCH] Add the LED burst trigger > > Hi! > >> Yes, Morse code can indicate any means. But when we look at the LEDs, would we like to also have a Morse code book in hand? >> >> The burst led blink idea is because it is easy to use and easy to describe. Mostly when users on site are describing the LEDs states to the support engineer. >> > > Well.. above 7 or so blinks, people will be unable to count. "one > short, one long" will help to extend that. > > Plus, there may be patterns such as "keep it ON, count number of brief > OFFs"... > > That's why I suggested: > >>> echo 40> step_length_ms >>> echo "- - - "> pattern >>> >>> do the same trick? >>> >>> Plus, you could for example do >>> >>> echo "- --- "> pattern >>> >>> to do morse code... > > Interface > > (Note that your client stripped some spaces out of it). > > With that, it should be very easy to program all the reasonable > blinking patterns for single LED without PWM. > Pavel > -- > (english) http://www.livejournal.com/~pavelmachek > (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html