From: Michael Grzeschik <mgr@pengutronix.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: support.opensource@diasemi.com, kernel@pengutronix.de,
linux-input@vger.kernel.org
Subject: Re: [PATCH] da9052: ensure da9052_ts_input_open will not lock up on irq flood
Date: Sat, 19 Mar 2016 10:12:38 +0100 [thread overview]
Message-ID: <20160319091238.GJ5824@pengutronix.de> (raw)
In-Reply-To: <20160311193311.GD13175@dtor-ws>
On Fri, Mar 11, 2016 at 11:33:11AM -0800, Dmitry Torokhov wrote:
> On Thu, Mar 03, 2016 at 11:52:02AM +0100, Michael Grzeschik wrote:
> > It is possible that da9052_ts_input_open is called and the touchscreen
> > is triggering continuous interrupts. In this case we will never leave
> > da9052_ts_input_open. The da9052_reg_update will never get the i2c bus
> > as the interrupt handler will continuously lock it.
> >
> > This patch switch places of da9052_reg_update and the setting of
> > tsi->stopped. This way its ensured that da9052_ts_input_open will never
> > lockup on interrupt flood.
>
> I understand what you are saying about updating register, however I do
> not understand why we would want to swap unmasking pendown event ans
> clearing the "stopped" flag.
The "stopped" flag has an locking purpose in the irq handler. My patch
ensures that the irq handler will not trigger any da9052_reg_update
before da9052_ts_input_open has finished.
On second thought, it would probably be enough to swap the call of
da9052_reg_update and da9052_enable_irq in da9052_ts_input_open.
This will have the same effect. I will send an corrected v2.
Thanks,
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2016-03-19 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 10:52 [PATCH] da9052: ensure da9052_ts_input_open will not lock up on irq flood Michael Grzeschik
2016-03-11 19:33 ` Dmitry Torokhov
2016-03-19 9:12 ` Michael Grzeschik [this message]
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=20160319091238.GJ5824@pengutronix.de \
--to=mgr@pengutronix.de \
--cc=dmitry.torokhov@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-input@vger.kernel.org \
--cc=support.opensource@diasemi.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).