linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trilok Soni <soni.trilok@gmail.com>
To: Paulius Zaleckas <paulius.zaleckas@teltonika.lt>
Cc: Eric Miao <eric.y.miao@gmail.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Uli Luckas <u.luckas@road.de>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH] input: add support for generic GPIO-based matrix keypad
Date: Fri, 17 Jul 2009 14:02:57 +0530	[thread overview]
Message-ID: <5d5443650907170132rfea7649o31bb3a84d3c7c79c@mail.gmail.com> (raw)
In-Reply-To: <4A602D6D.1090707@teltonika.lt>

Hi Paulius,

On Fri, Jul 17, 2009 at 1:21 PM, Paulius
Zaleckas<paulius.zaleckas@teltonika.lt> wrote:
> Eric Miao wrote:
>> Dmitry Torokhov wrote:
>>> Hi Eric,
>>>
>>> On Fri, Jun 12, 2009 at 09:26:43PM +0800, Eric Miao wrote:
>>>> Hi Dmitry,
>>>>
>>>> I've tested the driver code, and it's basically OK except for two minor
>>>> fixes:
>>>>
>>>> 1) GPIO and IRQs have to be initialized before input_register_device(),
>>>> otherwise input->open() will be invoked before that, which will schedule
>>>> an immediate scan work and fail.
>>>>
>>>> 2) disable_irq_rows() called in init_matrix_gpio() so that by default it's
>>>> initialized to disabled - and will be enabled by input->open()
>>>>
>>> Could you please take a look at the driver as it is commited to
>>> 'for-linus' branch of my tree and let me know if you see anything wrong
>>> there? Otherwise I inted to submit it in my next update to Linus.
>>>
>>
>> Sorry Dmitry,
>>
>> Reply so late and til now I have some time to test this. The patch there
>> still has at least one issue I guess - the keycodes[] allocation size
>> should be MATRIX_MAX_ROWS * MATRIX_MAX_COLS if I understand correctly.
>>
>> I'm experiencing a problem of keypad->pdata being overwritten, and found
>> keycodes are actually accessed by [(row << 4) + col], so that should be
>> a full range.
>
> As this driver is already in the mainline and I was trying to use it...
> I get various kernel crashes due to this keycodes[] allocation size bug.
> Care to send a patch for this bug?
>
>> And one more minor issue that may not be significant is the hardcoding of
>> the '4' in this (row << 4).
>>
>> Some of the key hits on my Littleton just worked smoothly with the above
>> correction, but not all - some key hits just gave intermittent events, I
>> have no idea how's that - maybe related to my scan delay and debouncing
>> settings

Did you tried assigning max_keypmap_size in platform data to
MATRIX_MAX_COLS * MATRIX_MAX_ROWS ?

-- 
---Trilok Soni
http://triloksoni.wordpress.com
http://www.linkedin.com/in/triloksoni

  reply	other threads:[~2009-07-17  8:32 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07  8:00 [PATCH] input: add support for generic GPIO-based matrix keypad Eric Miao
2009-05-07  8:41 ` Trilok Soni
2009-05-07  8:48   ` Eric Miao
2009-05-07  8:51     ` Trilok Soni
2009-05-08  1:29       ` Eric Miao
2009-05-08  4:54         ` Trilok Soni
2009-05-08  5:52         ` Arve Hjønnevåg
2009-05-25  3:36           ` Trilok Soni
2009-05-25  7:05             ` Eric Miao
2009-05-27 13:26 ` Uli Luckas
2009-05-31 14:12   ` Eric Miao
2009-05-31 14:20     ` Russell King - ARM Linux
2009-05-31 14:29       ` Eric Miao
2009-05-31 17:38         ` Dmitry Torokhov
2009-06-01  3:43           ` Eric Miao
2009-05-31 17:39         ` Robert Jarzmik
2009-06-01  4:02           ` Eric Miao
2009-06-02 14:55     ` Uli Luckas
2009-06-02 15:14       ` Uli Luckas
2009-06-03  6:24         ` Eric Miao
2009-06-10  4:10           ` Trilok Soni
2009-07-04  5:54             ` Marek Vasut
2009-07-06  6:02               ` Eric Miao
2009-07-06 10:58                 ` Marek Vasut
     [not found]           ` <f17812d70906070704s10f8eac6ybc353041e2db5a03@mail.gmail.com>
2009-06-12  4:03             ` Dmitry Torokhov
2009-06-12 13:01               ` Trilok Soni
2009-06-12 13:26                 ` Eric Miao
2009-06-19  6:54                   ` Trilok Soni
2009-06-29 16:26                   ` Dmitry Torokhov
2009-06-30  6:43                     ` Trilok Soni
2009-07-01 12:14                       ` Kim Kyuwon
2009-07-09  9:46                     ` Eric Miao
2009-07-09 10:01                       ` Trilok Soni
2009-07-17  7:51                       ` Paulius Zaleckas
2009-07-17  8:32                         ` Trilok Soni [this message]
2009-07-17  9:20                           ` Paulius Zaleckas
2009-07-20  7:12                             ` Trilok Soni
2009-07-20 10:37                               ` Eric Miao
2009-07-20 10:43                                 ` Trilok Soni
2009-07-20 11:43                                   ` Eric Miao
2009-07-21  8:00                                 ` Dmitry Torokhov
2009-07-21  8:26                                   ` Eric Miao
2009-07-21 15:58                                     ` Dmitry Torokhov
2009-07-27  8:54                                       ` Eric Miao
2009-06-03  6:06       ` Eric Miao
2009-06-03 18:06       ` Trilok Soni

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=5d5443650907170132rfea7649o31bb3a84d3c7c79c@mail.gmail.com \
    --to=soni.trilok@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=eric.y.miao@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=paulius.zaleckas@teltonika.lt \
    --cc=u.luckas@road.de \
    /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).