From: David Brownell <david-b@pacbell.net>
To: hartleys <hartleys@visionengravers.com>
Cc: linux-input@vger.kernel.org, OMAP <linux-omap@vger.kernel.org>
Subject: Re: [patch/rfc 2.6.28-rc2] input: twl4030_keypad driver
Date: Thu, 5 Feb 2009 17:11:57 -0800 [thread overview]
Message-ID: <200902051711.57605.david-b@pacbell.net> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE1909011A53D4@mi8nycmail19.Mi8.com>
On Friday 30 January 2009, hartleys wrote:
> > I'd support an overall cleanup patch that fixes all those things at once.
>
> How's this for a starting point? I'm willing to create a cleanup patch
> for all the mach-omap1, mach-omap2, and mach-pxa users.
>
> Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
I think none of the twl4030 keypad users are in mainline, so far...
My first reaction to this is that it's a bit incomplete.
It replaces only the KEY() macro in the $SUBJECT patch:
- There are two more public ones (for board files):
* KEY_PERSISTENT flags row/column values to ignore
* PERSISTENT_KEY (sigh) generates a row/col entry
with such a marking (instead of a keycode)
- Plus two driver-internal ones:
* ROWCOL_MASK to strip R/C from KEY()
* KEYCODE_MASK to stip the keycode from a KEY()
If there is going to be something reusable across the whole
input subsystem (for drivers that don't need fancy stuff),
it should really address the whole problem...
- Dave
> ---
>
> diff --git a/include/linux/input.h b/include/linux/input.h
> index 1249a0c..0879493 100644
> --- a/include/linux/input.h
> +++ b/include/linux/input.h
> @@ -598,6 +598,14 @@ struct input_absinfo {
> #define KEY_CNT (KEY_MAX+1)
>
> /*
> + * Macro to pack the row/col of a key on a matrix keypad and it's associated
> + * KEY_* code into into an array. 4 bits are used for both the row and column
> + * allowing for up to a 16x16 keypad. The row (_r) and column (_c) are
> + * interchangable depending on a keypad drivers usage.
> + */
> +#define MATRIX_KEY(_r, _c, _v) (((_r) << 28) | ((_c) << 24) | (_v))
> +
> +/*
> * Relative axes
> */
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-02-06 1:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 0:13 [patch/rfc 2.6.28-rc2] input: twl4030_keypad driver David Brownell
2009-01-22 7:09 ` Trilok Soni
2009-01-22 17:42 ` David Brownell
2009-01-22 17:57 ` Trilok Soni
2009-01-30 0:17 ` hartleys
2009-01-30 0:57 ` David Brownell
2009-01-30 17:13 ` hartleys
2009-02-06 1:11 ` David Brownell [this message]
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=200902051711.57605.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=hartleys@visionengravers.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-omap@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.