From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Michael Hennerich <michael.hennerich@analog.com>
Cc: "Guido Martínez" <guido@vanguardiasur.com.ar>,
"Mike Frysinger" <vapier@gentoo.org>,
linux-input@vger.kernel.org,
device-drivers-devel@blackfin.uclinux.org,
"Ezequiel García" <ezequiel@vanguardiasur.com.ar>
Subject: Re: [PATCH 3/3] Input: adp5589-keys: fix event count mask
Date: Wed, 6 May 2015 16:36:00 -0700 [thread overview]
Message-ID: <20150506233600.GC5580@dtor-ws> (raw)
In-Reply-To: <5536607C.4010404@analog.com>
On Tue, Apr 21, 2015 at 04:36:44PM +0200, Michael Hennerich wrote:
> On 04/21/2015 04:21 PM, Guido Martínez wrote:
> >The event mask was specified as 0xF (4 bits) when in reality is 0x1F (5
> >bits) in order to be capable of representing all FIFO length values from
> >0 to 16.
> >
> >This caused a problem: when the keypad reported 16 pending events the
> >driver took it as 0, and did nothing. This in turn caused the keypad to
> >re-issue the interrupt over and over again.
> >
> >Fixes: 9d2e173644bb ('Input: ADP5589 - new driver for I2C Keypad Decoder and I/O Expander')
> >Signed-off-by: Guido Martínez <guido@vanguardiasur.com.ar>
> Acked-by: Michael Hennerich <michael.hennerich@analog.com>
Applied, thank you.
> >---
> > drivers/input/keyboard/adp5589-keys.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >diff --git a/drivers/input/keyboard/adp5589-keys.c b/drivers/input/keyboard/adp5589-keys.c
> >index 8709a7f..0419a7a 100644
> >--- a/drivers/input/keyboard/adp5589-keys.c
> >+++ b/drivers/input/keyboard/adp5589-keys.c
> >@@ -180,7 +180,7 @@
> > #define LOGIC2_STAT (1 << 7) /* ADP5589 only */
> > #define LOGIC1_STAT (1 << 6)
> > #define LOCK_STAT (1 << 5) /* ADP5589 only */
> >-#define KEC 0xF
> >+#define KEC 0x1F
> > /* PIN_CONFIG_D Register */
> > #define C4_EXTEND_CFG (1 << 6) /* RESET2 */
>
>
> --
> Greetings,
> Michael
>
> --
> Analog Devices GmbH Wilhelm-Wagenfeld-Str. 6 80807 Muenchen
> Sitz der Gesellschaft: Muenchen; Registergericht: Muenchen HRB 40368;
> Geschaeftsfuehrer:Dr.Carsten Suckrow, Thomas Wessel, William A. Martin,
> Margaret Seif
>
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-05-06 23:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 14:21 [PATCH 0/3] adp5589 fixes Guido Martínez
2015-04-21 14:21 ` [PATCH 1/3] Input: adp5589-keys: handle i2c errors on the irq handler Guido Martínez
[not found] ` <55366018.8050807@analog.com>
2015-05-06 23:33 ` Dmitry Torokhov
2015-05-09 19:48 ` Guido Martínez
2015-04-21 14:21 ` [PATCH 2/3] Input: adp5589-keys: fix pull mask setting Guido Martínez
2015-04-21 14:35 ` Michael Hennerich
2015-05-06 23:34 ` Dmitry Torokhov
2015-04-21 14:21 ` [PATCH 3/3] Input: adp5589-keys: fix event count mask Guido Martínez
2015-04-21 14:36 ` Michael Hennerich
2015-05-06 23:36 ` Dmitry Torokhov [this message]
2015-10-02 21:28 ` Ezequiel Garcia
2015-10-06 0:29 ` Dmitry Torokhov
2015-10-08 14:21 ` Ezequiel Garcia
2015-05-06 14:04 ` [PATCH 0/3] adp5589 fixes Guido Martínez
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=20150506233600.GC5580@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=guido@vanguardiasur.com.ar \
--cc=linux-input@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--cc=vapier@gentoo.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).