linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Alban Bedel <alban.bedel@avionic-design.de>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] Input: tca8418 - Add support for shared interrupt
Date: Mon, 5 Nov 2012 10:58:06 -0800	[thread overview]
Message-ID: <20121105185806.GA18149@core.coreip.homeip.net> (raw)
In-Reply-To: <1352132052-19771-1-git-send-email-alban.bedel@avionic-design.de>

Hi Alban,

On Mon, Nov 05, 2012 at 05:14:12PM +0100, Alban Bedel wrote:
> Signed-off-by: Alban Bedel <alban.bedel@avionic-design.de>
> ---
>  drivers/input/keyboard/tca8418_keypad.c |   10 +++++++---
>  1 files changed, 7 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/input/keyboard/tca8418_keypad.c b/drivers/input/keyboard/tca8418_keypad.c
> index fc9cc94..5adc655 100644
> --- a/drivers/input/keyboard/tca8418_keypad.c
> +++ b/drivers/input/keyboard/tca8418_keypad.c
> @@ -225,16 +225,18 @@ static irqreturn_t tca8418_irq_handler(int irq, void *dev_id)
>  	if (error) {
>  		dev_err(&keypad_data->client->dev,
>  			"unable to read REG_INT_STAT\n");
> -		goto exit;
> +		return IRQ_NONE;
>  	}
>  
> +	if (!reg)
> +		return IRQ_NONE;
> +
>  	if (reg & INT_STAT_OVR_FLOW_INT)
>  		dev_warn(&keypad_data->client->dev, "overflow occurred\n");
>  
>  	if (reg & INT_STAT_K_INT)
>  		tca8418_read_keypad(keypad_data);
>  
> -exit:
>  	/* Clear all interrupts, even IRQs we didn't check (GPI, CAD, LCK) */
>  	reg = 0xff;
>  	error = tca8418_write_byte(keypad_data, REG_INT_STAT, reg);
> @@ -377,7 +379,9 @@ static int __devinit tca8418_keypad_probe(struct i2c_client *client,
>  		client->irq = gpio_to_irq(client->irq);
>  
>  	error = request_threaded_irq(client->irq, NULL, tca8418_irq_handler,
> -				     IRQF_TRIGGER_FALLING | IRQF_ONESHOT,
> +				     IRQF_TRIGGER_FALLING |
> +				     IRQF_SHARED |
> +				     IRQF_ONESHOT,
>  				     client->name, keypad_data);

I do not think that using ONESHOT IRQ handlers in shared interrupt
configuration is a good idea as that interrupt will stay masked until
the keypad is done processing it, which may take some time.

Thanks.

-- 
Dmitry

  reply	other threads:[~2012-11-05 18:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05 16:14 [PATCH] Input: tca8418 - Add support for shared interrupt Alban Bedel
2012-11-05 18:58 ` Dmitry Torokhov [this message]
2012-11-06 16:34   ` Alban Bedel
2012-11-08 16:45     ` Dmitry Torokhov

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=20121105185806.GA18149@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=alban.bedel@avionic-design.de \
    --cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).