From mboxrd@z Thu Jan 1 00:00:00 1970 From: jbe@pengutronix.de (=?iso-8859-1?q?J=FCrgen_Beisert?=) Date: Mon, 16 Sep 2013 10:10:22 +0200 Subject: [PATCH 5/6] Staging/iio/adc/touchscreen/MXS: add interrupt driven touch detection In-Reply-To: <52359259.8010202@kernel.org> References: <1378887511-24530-1-git-send-email-jbe@pengutronix.de> <1378887511-24530-6-git-send-email-jbe@pengutronix.de> <52359259.8010202@kernel.org> Message-ID: <201309161010.22151.jbe@pengutronix.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Jonathan, On Sunday 15 September 2013 12:56:25 Jonathan Cameron wrote: > On 09/11/13 09:18, Juergen Beisert wrote: > > For battery driven systems it is a very bad idea to collect the > > touchscreen data within a kernel busy loop. > > > > This change uses the features of the hardware to delay and accumulate > > samples in hardware to avoid a high interrupt and CPU load. > > > > Note: this is only tested on an i.MX23 SoC yet. > > > > Signed-off-by: Juergen Beisert > > CC: linux-arm-kernel at lists.infradead.org > > CC: devel at driverdev.osuosl.org > > CC: Marek Vasut > > CC: Fabio Estevam > > CC: Jonathan Cameron > > While this driver is placed in IIO within staging at the moment, these > changes are definitely input related. Hence I have cc'd Dmitry and the > input list. > > I am personaly a little uncomfortable that we have such a complex bit of > input code sat within an IIO driver but such is life. Maybe an MFD for this ADC unit would be a better way to go? Currently I have a different problem with this driver, because the ADC unit monitors the battery as well. And the charging driver from the power subsystem needs these values to charge the battery in a correct manner. > [...] Regards, Juergen -- Pengutronix e.K. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?| Juergen Beisert ? ? ? ? ? ? | Linux Solutions for Science and Industry ? ? ?| http://www.pengutronix.de/ |