From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andi Shyti <andi.shyti@samsung.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Andi Shyti <andi@etezian.org>
Subject: Re: [PATCH] Input: stmfts: set IRQ_NOAUTOEN to the irq flag
Date: Mon, 22 Jan 2018 17:37:03 -0800 [thread overview]
Message-ID: <20180123013703.nj7ohi4rylz4om6o@dtor-ws> (raw)
In-Reply-To: <20170927125831.11759-1-andi.shyti@samsung.com>
On Wed, Sep 27, 2017 at 09:58:31PM +0900, Andi Shyti wrote:
> The interrupt is requested before the device is powered on and
> it's value in some cases cannot be reliable. It happens on some
> devices that an interrupt is generated as soon as requested
> before having the chance to disable the irq.
>
> Set the irq flag as IRQ_NOAUTOEN before requesting it.
>
> This patch mutes the error:
>
> stmfts 2-0049: failed to read events: -11
>
> received sometimes during boot time.
>
> Signed-off-by: Andi Shyti <andi.shyti@samsung.com>
Applied, thank you.
> ---
> drivers/input/touchscreen/stmfts.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/input/touchscreen/stmfts.c b/drivers/input/touchscreen/stmfts.c
> index 2351199189a4..362de0001b33 100644
> --- a/drivers/input/touchscreen/stmfts.c
> +++ b/drivers/input/touchscreen/stmfts.c
> @@ -689,6 +689,14 @@ static int stmfts_probe(struct i2c_client *client,
>
> input_set_drvdata(sdata->input, sdata);
>
> + /*
> + * stmfts_power_on expects interrupt to be disabled, but
> + * at this point the device is still off and I do not trust
> + * the status of the irq line that can generate some spurious
> + * interrupts. To be on the safe side it's better to not enable
> + * the interrupts during their request.
> + */
> + irq_set_status_flags(client->irq, IRQ_NOAUTOEN);
> err = devm_request_threaded_irq(&client->dev, client->irq,
> NULL, stmfts_irq_handler,
> IRQF_ONESHOT,
> @@ -696,9 +704,6 @@ static int stmfts_probe(struct i2c_client *client,
> if (err)
> return err;
>
> - /* stmfts_power_on expects interrupt to be disabled */
> - disable_irq(client->irq);
> -
> dev_dbg(&client->dev, "initializing ST-Microelectronics FTS...\n");
>
> err = stmfts_power_on(sdata);
> --
> 2.14.2
>
--
Dmitry
prev parent reply other threads:[~2018-01-23 1:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170927125843epcas2p3a703ab81e165bdaf5bfd100dc08f9ae1@epcas2p3.samsung.com>
2017-09-27 12:58 ` [PATCH] Input: stmfts: set IRQ_NOAUTOEN to the irq flag Andi Shyti
2018-01-23 1:37 ` Dmitry Torokhov [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=20180123013703.nj7ohi4rylz4om6o@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=andi.shyti@samsung.com \
--cc=andi@etezian.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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