From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-out.m-online.net ([212.18.0.10]:41506 "EHLO mail-out.m-online.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757219Ab3IPPKi convert rfc822-to-8bit (ORCPT ); Mon, 16 Sep 2013 11:10:38 -0400 From: Marek Vasut To: =?iso-8859-1?q?J=FCrgen_Beisert?= Subject: Re: [PATCH 5/6] Staging/iio/adc/touchscreen/MXS: add interrupt driven touch detection Date: Mon, 16 Sep 2013 17:10:36 +0200 Cc: linux-arm-kernel@lists.infradead.org, Jonathan Cameron , linux-iio@vger.kernel.org, devel@driverdev.osuosl.org, fabio.estevam@freescale.com, jic23@cam.ac.uk, Torokhov , "linux-input@vger.kernel.org" , Otavio Salvador References: <1378887511-24530-1-git-send-email-jbe@pengutronix.de> <201309161623.48247.marex@denx.de> <201309161634.54603.jbe@pengutronix.de> In-Reply-To: <201309161634.54603.jbe@pengutronix.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Message-Id: <201309161710.36726.marex@denx.de> Sender: linux-iio-owner@vger.kernel.org List-Id: linux-iio@vger.kernel.org Dear Jürgen Beisert, > Hi Marek, > > On Monday 16 September 2013 16:23:48 Marek Vasut wrote: > > > 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@lists.infradead.org > > > > > CC: devel@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. > > > > Are you planning to post the power block patches too ? > > When they will work: yes. Currently it crashes all the time. The PMIC is a > beast... Full ACK Best regards, Marek Vasut