* [PATCH 1/3] max7359_keypad: Do not set MAX7359_CFG_INTERRUPT flag
@ 2015-05-14 2:34 Evgeniy Dushistov
2015-05-15 20:52 ` Dmitry Torokhov
0 siblings, 1 reply; 2+ messages in thread
From: Evgeniy Dushistov @ 2015-05-14 2:34 UTC (permalink / raw)
To: Dmitry Torokhov; +Cc: linux-input, linux-kernel
max7359_keypad: Do not set MAX7359_CFG_INTERRUPT flag.
In datasheet of max7359, there is description of this flag:
0 - INT cleared when FIFO empty,
1 - INT cleared after host read. In this mode, I2C should read
FIFO until interrupt condition removed, or further INT may be lost.
So, if we set this flag, we have to read FIFO until it become
empty. But in interrupt we read FIFO just once.
This lead to "keyboard" hang until reboot, if we press
several keys, because of interrupt handler read just one
"press" from FIFO and clear interrupt.
Signed-off-by: Evgeniy A. Dushistov <dushistov@mail.ru>
---
drivers/input/keyboard/max7359_keypad.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/input/keyboard/max7359_keypad.c b/drivers/input/keyboard/max7359_keypad.c
index faa6da5..4e35904 100644
--- a/drivers/input/keyboard/max7359_keypad.c
+++ b/drivers/input/keyboard/max7359_keypad.c
@@ -166,7 +166,6 @@ static void max7359_close(struct input_dev *dev)
static void max7359_initialize(struct i2c_client *client)
{
max7359_write_reg(client, MAX7359_REG_CONFIG,
- MAX7359_CFG_INTERRUPT | /* Irq clears after host read */
MAX7359_CFG_KEY_RELEASE | /* Key release enable */
MAX7359_CFG_WAKEUP); /* Key press wakeup enable */
--
2.3.6
--
/Evgeniy
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH 1/3] max7359_keypad: Do not set MAX7359_CFG_INTERRUPT flag
2015-05-14 2:34 [PATCH 1/3] max7359_keypad: Do not set MAX7359_CFG_INTERRUPT flag Evgeniy Dushistov
@ 2015-05-15 20:52 ` Dmitry Torokhov
0 siblings, 0 replies; 2+ messages in thread
From: Dmitry Torokhov @ 2015-05-15 20:52 UTC (permalink / raw)
To: linux-input, linux-kernel
On Thu, May 14, 2015 at 05:34:50AM +0300, Evgeniy Dushistov wrote:
> max7359_keypad: Do not set MAX7359_CFG_INTERRUPT flag.
> In datasheet of max7359, there is description of this flag:
> 0 - INT cleared when FIFO empty,
> 1 - INT cleared after host read. In this mode, I2C should read
> FIFO until interrupt condition removed, or further INT may be lost.
>
> So, if we set this flag, we have to read FIFO until it become
> empty. But in interrupt we read FIFO just once.
> This lead to "keyboard" hang until reboot, if we press
> several keys, because of interrupt handler read just one
> "press" from FIFO and clear interrupt.
>
> Signed-off-by: Evgeniy A. Dushistov <dushistov@mail.ru>
Applied, thank you.
> ---
> drivers/input/keyboard/max7359_keypad.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/input/keyboard/max7359_keypad.c b/drivers/input/keyboard/max7359_keypad.c
> index faa6da5..4e35904 100644
> --- a/drivers/input/keyboard/max7359_keypad.c
> +++ b/drivers/input/keyboard/max7359_keypad.c
> @@ -166,7 +166,6 @@ static void max7359_close(struct input_dev *dev)
> static void max7359_initialize(struct i2c_client *client)
> {
> max7359_write_reg(client, MAX7359_REG_CONFIG,
> - MAX7359_CFG_INTERRUPT | /* Irq clears after host read */
> MAX7359_CFG_KEY_RELEASE | /* Key release enable */
> MAX7359_CFG_WAKEUP); /* Key press wakeup enable */
>
> --
> 2.3.6
>
> --
> /Evgeniy
--
Dmitry
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-05-15 20:52 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-05-14 2:34 [PATCH 1/3] max7359_keypad: Do not set MAX7359_CFG_INTERRUPT flag Evgeniy Dushistov
2015-05-15 20:52 ` Dmitry Torokhov
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).