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@xxxxxx > To: lgxue@xxxxxxxxxxx > CC: cooloney@xxxxxxxxx; rpurdie@xxxxxxxxx; rob@xxxxxxxxxxx; milo.kim@xxxxxx; linux-leds@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; linux-doc@xxxxxxxxxxxxxxx > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
