linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kristina Martšenko" <kristina.martsenko@gmail.com>
To: Marek Vasut <marex@denx.de>
Cc: Jonathan Cameron <jic23@kernel.org>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald <pmeerw@pmeerw.net>,
	Juergen Beisert <jbe@pengutronix.de>,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>,
	Fabio Estevam <fabio.estevam@freescale.com>,
	Stefan Wahren <stefan.wahren@i2se.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-iio@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: [PATCH 2/4] iio: mxs-lradc: make ADC reads not disable touchscreen interrupts
Date: Mon, 19 Jan 2015 21:03:07 +0200	[thread overview]
Message-ID: <54BD54EB.6020704@gmail.com> (raw)
In-Reply-To: <201501180121.19946.marex@denx.de>

On 18/01/15 02:21, Marek Vasut wrote:
> On Saturday, January 17, 2015 at 01:22:09 AM, Kristina Martšenko wrote:
>> Reading a channel through sysfs, or starting a buffered capture, will
>> currently turn off the touchscreen. This is because the read_raw() and
>> buffer preenable()/postdisable() callbacks disable interrupts for all
>> LRADC channels, including those the touchscreen uses.
>>
>> So make the callbacks only disable interrupts for the channels they use.
>> This means channel 0 for read_raw() and channels 0-5 for the buffer (if
>> the touchscreen is enabled). Since the touchscreen uses different
>> channels (6 and 7), it no longer gets turned off.
>>
>> Note that only i.MX28 is affected by this issue, i.MX23 should be fine.
>>
>> Signed-off-by: Kristina Martšenko <kristina.martsenko@gmail.com>
>> ---
>>  drivers/staging/iio/adc/mxs-lradc.c | 24 +++++++++++++++++-------
>>  1 file changed, 17 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/staging/iio/adc/mxs-lradc.c
>> b/drivers/staging/iio/adc/mxs-lradc.c index fc65cd311be9..0cf276ff0dc5
>> 100644
>> --- a/drivers/staging/iio/adc/mxs-lradc.c
>> +++ b/drivers/staging/iio/adc/mxs-lradc.c
>> @@ -218,8 +218,11 @@ struct mxs_lradc {
>>  	 * channels: #6 and #7. This means that only 6 virtual channels (instead
>>  	 * of 8) will be available for buffered capture.
>>  	 */
>> -#define TS_VCH1		7
>> -#define TS_VCH2		6
>> +#define TS_VCH1				7
>> +#define TS_VCH2				6
> 
> Please fix the indent in 1/4 , so you don't have to change it again this patch.

Right, of course, I'll do that in v2.

> Reviewed-by: Marek Vasut <marex@denx.de>

Thanks for taking time to review all the patches!

Kristina

  reply	other threads:[~2015-01-19 19:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-17  0:22 [PATCH 0/4] iio: mxs-lradc: fix interactions between the touchscreen and the ADC Kristina Martšenko
2015-01-17  0:22 ` [PATCH 1/4] iio: mxs-lradc: separate touchscreen and buffer virtual channels Kristina Martšenko
2015-01-18  0:19   ` Marek Vasut
2015-01-19 19:02     ` Kristina Martšenko
2015-01-20  1:29       ` Marek Vasut
2015-01-17  0:22 ` [PATCH 2/4] iio: mxs-lradc: make ADC reads not disable touchscreen interrupts Kristina Martšenko
2015-01-18  0:21   ` Marek Vasut
2015-01-19 19:03     ` Kristina Martšenko [this message]
2015-01-17  0:22 ` [PATCH 3/4] iio: mxs-lradc: make ADC reads not unschedule touchscreen conversions Kristina Martšenko
2015-01-18  0:22   ` Marek Vasut
2015-01-19  7:20   ` Juergen Borleis
2015-01-19  7:57     ` Marek Vasut
2015-01-19 20:03       ` Kristina Martšenko
2015-01-17  0:22 ` [PATCH 4/4] iio: mxs-lradc: only update the buffer when its conversions have finished Kristina Martšenko
2015-01-18  0:23   ` Marek Vasut
2015-01-18 11:21 ` [PATCH 0/4] iio: mxs-lradc: fix interactions between the touchscreen and the ADC Stefan Wahren
2015-01-19 20:30   ` Kristina Martšenko
2015-01-20  1:32     ` Marek Vasut

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54BD54EB.6020704@gmail.com \
    --to=kristina.martsenko@gmail.com \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=fabio.estevam@freescale.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jbe@pengutronix.de \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=pmeerw@pmeerw.net \
    --cc=stefan.wahren@i2se.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).