From: "H Hartley Sweeten" <hartleys@visionengravers.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: RE: [PATCH] ep93xx_keypad.c: cleanup and use matrix_keypad helpers
Date: Mon, 21 Dec 2009 13:27:48 -0500 [thread overview]
Message-ID: <BD79186B4FD85F4B8E60E381CAEE19090200F172@mi8nycmail19.Mi8.com> (raw)
In-Reply-To: <20091221181959.GA6696@core.coreip.homeip.net>
On Monday, December 21, 2009 11:20 AM, Dmitry Torokhov wrote:
>
> Hi Hartley,
>
> On Mon, Dec 21, 2009 at 01:01:01PM -0500, H Hartley Sweeten wrote:
>> ep93xx_keypad.c: cleanup and use matrix_keypad helpers
>>
>> 1) use struct matrix_keymap_data to supply the keymap from the platform code
>> and use matrix_keypad_build_keymap() to initialize the keymap
>
> I;d prefer this one split out. Also, is there any in-kernel users and
> will they be converted to the new format of platform data.
I will split the patch and repost.
There are no current in-kernel users so it should not be a problem.
>> 2) namespace sanitize the local defines
>> 3) cleanup the interrupt handler to make it more understandable
>> 4) allocate the keycode matrix at run time
>
> What is the point given that the size of the keymap is still constant
> with your patch. And even if it was dynamic just stick it at the end of
> struct ep93xx_keypad as unsigned short keycodes[] and allocate in one
> shot.
No real point, I was just following the way it was done in matrix_keypad.c.
I guess it makes more sense to leave the keycode matrix as a constant. With
the EP93XX the matrix is always 8x8 since the peripheral always scans every
row/column. I will switch it back.
Are you ok with the interrupt handler change?
Regards,
Hartley
next prev parent reply other threads:[~2009-12-21 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 18:01 [PATCH] ep93xx_keypad.c: cleanup and use matrix_keypad helpers H Hartley Sweeten
2009-12-21 18:19 ` Dmitry Torokhov
2009-12-21 18:27 ` H Hartley Sweeten [this message]
2009-12-21 18:40 ` H Hartley Sweeten
2010-01-11 20:48 ` H Hartley Sweeten
2010-01-12 8:30 ` 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=BD79186B4FD85F4B8E60E381CAEE19090200F172@mi8nycmail19.Mi8.com \
--to=hartleys@visionengravers.com \
--cc=dmitry.torokhov@gmail.com \
--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).