From mboxrd@z Thu Jan 1 00:00:00 1970 From: simon@mungewell.org Subject: Re: Building BarGraph with LED subsystem Date: Fri, 16 Mar 2012 12:38:50 -0400 Message-ID: References: <1b29a178dd288b0f17608b5815ca77a5.squirrel@mungewell.org> <20323.25792.171143.809563@quad.stoffel.home> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Return-path: Received: from host171.canaca.com ([67.55.55.225]:36722 "EHLO host171.canaca.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031294Ab2CPQiv (ORCPT ); Fri, 16 Mar 2012 12:38:51 -0400 In-Reply-To: <20323.25792.171143.809563@quad.stoffel.home> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: John Stoffel Cc: simon@mungewell.org, linux-input@vger.kernel.org, linux-kernel@vger.kernel.org > While making the kernel more complex... esp for a feature which is of > such limited use. Is the concept of a bargraph of LEDs really a 'limited use'? I can think of several uses... I mean isn't flashing or a heart beat just as limited ;-) > Do it all in userland, it's easier, you can use > floating point math, etc. And to test changes, you don't have to > recompile a module and unload/reload it, etc. For my application a user-land stub would do math to work out threshold values and push current value (in the right format) into the LED subsystem. Once kernel framework is provided it should not need re-compilation on a case by case basis. Simon