From: jbe@pengutronix.de (Jürgen Beisert)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/6] Staging/iio/adc/touchscreen/MXS: add interrupt driven touch detection
Date: Tue, 17 Sep 2013 09:33:08 +0200 [thread overview]
Message-ID: <201309170933.08505.jbe@pengutronix.de> (raw)
In-Reply-To: <20130916152846.GC12105@core.coreip.homeip.net>
Hi Dmitry,
On Monday 16 September 2013 17:28:46 Dmitry Torokhov wrote:
> [...]
> > > static int mxs_lradc_ts_register(struct mxs_lradc *lradc)
> > > @@ -641,6 +1056,7 @@ static void mxs_lradc_ts_unregister(struct
> > > mxs_lradc *lradc)
> > >
> > > cancel_work_sync(&lradc->ts_work);
> > >
> > > + mxs_lradc_disable_ts(lradc);
> > > input_unregister_device(lradc->ts_input);
> > > }
>
> This looks iffy... Normally you disable the device so that it does not
> generate more interrupts, and then cancel outstanding work(s), otherwise
> newly generated interrupts may cause more work to be scheduled. Or I
> missed some of the context and this is not a concern here?
This part gets removed in patch 6/6:
@@ -1054,8 +891,6 @@ static void mxs_lradc_ts_unregister(struct mxs_lradc *lradc)
????????if (!lradc->use_touchscreen)
????????????????return;
?
-???????cancel_work_sync(&lradc->ts_work);
-
????????mxs_lradc_disable_ts(lradc);
????????input_unregister_device(lradc->ts_input);
?}
But you are right, I should move this into patch 5/6.
Thanks
Regards,
Juergen
--
Pengutronix e.K. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?| Juergen Beisert ? ? ? ? ? ? |
Linux Solutions for Science and Industry ? ? ?| http://www.pengutronix.de/ |
next prev parent reply other threads:[~2013-09-17 7:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 8:18 [RFCv4] staging/iio/adc: change the MXS touchscreen driver implementation Juergen Beisert
2013-09-11 8:18 ` [PATCH 1/6] Staging/iio/adc/touchscreen/MXS: distinguish i.MX23's and i.MX28's LRADC Juergen Beisert
2013-09-11 8:18 ` [PATCH 2/6] Staging/iio/adc/touchscreen/MXS: separate i.MX28 specific register bits Juergen Beisert
2013-09-15 10:27 ` Jonathan Cameron
2013-09-11 8:18 ` [PATCH 3/6] Staging/iio/adc/touchscreen/MXS: simplify register access Juergen Beisert
2013-09-15 10:35 ` Jonathan Cameron
2013-09-16 8:17 ` Jürgen Beisert
2013-09-16 18:39 ` Jonathan Cameron
2013-09-16 14:15 ` Marek Vasut
2013-09-11 8:18 ` [PATCH 4/6] Staging/iio/adc/touchscreen/MXS: add i.MX23 support to the LRADC touchscreen driver Juergen Beisert
2013-09-15 10:50 ` Jonathan Cameron
2013-09-16 8:14 ` Jürgen Beisert
2013-09-16 14:19 ` Marek Vasut
2013-09-11 8:18 ` [PATCH 5/6] Staging/iio/adc/touchscreen/MXS: add interrupt driven touch detection Juergen Beisert
2013-09-15 10:56 ` Jonathan Cameron
2013-09-15 16:10 ` Jonathan Cameron
2013-09-16 8:38 ` Jürgen Beisert
2013-09-16 8:10 ` Jürgen Beisert
2013-09-16 9:37 ` Jürgen Beisert
2013-09-16 14:23 ` Marek Vasut
2013-09-16 14:34 ` Jürgen Beisert
2013-09-16 15:10 ` Marek Vasut
2013-09-16 15:30 ` Jonathan Cameron
2013-09-19 12:49 ` Jürgen Beisert
2013-09-19 16:12 ` Jonathan Cameron
2013-09-16 15:28 ` Dmitry Torokhov
2013-09-17 7:33 ` Jürgen Beisert [this message]
2013-09-11 8:18 ` [PATCH 6/6] Staging/iio/adc/touchscreen/MXS: Remove old touchscreen detection implementation Juergen Beisert
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=201309170933.08505.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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).