From: Miguel Aguilar <miguel.aguilar@ridgerun.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: nsnehaprabha@ti.com,
davinci-linux-open-source@linux.davincidsp.com,
linux-input@vger.kernel.org, todd.fischer@ridgerun.com,
diego.dompe@ridgerun.com, clark.becker@ridgerun.com,
santiago.nunez@ridgerun.com
Subject: Re: [PATCH 2/3] Davinci: DM365: Enable DaVinci Key Scan support for DM365 EVM
Date: Fri, 25 Sep 2009 08:26:32 -0600 [thread overview]
Message-ID: <4ABCD318.5080307@ridgerun.com> (raw)
In-Reply-To: <4ABCCF30.2090802@ridgerun.com>
Miguel Aguilar wrote:
> Dmitry Torokhov wrote:
>> On Thu, Sep 24, 2009 at 10:54:00AM -0600, miguel.aguilar@ridgerun.com
>> wrote:
>>>
>>> +/* Masks for the various keys on the DM365 EVM */
>>> +#define KEY_DM365_KEY2 0
>>> +#define KEY_DM365_LEFT 1
>>> +#define KEY_DM365_EXIT 2
>>> +#define KEY_DM365_DOWN 3
>>> +#define KEY_DM365_ENTER 4
>>> +#define KEY_DM365_UP 5
>>> +#define KEY_DM365_KEY1 6
>>> +#define KEY_DM365_RIGHT 7
>>> +#define KEY_DM365_MENU 8
>>> +#define KEY_DM365_REC 9
>>> +#define KEY_DM365_REW 10
>>> +#define KEY_DM365_SKIPMINUS 11
>>> +#define KEY_DM365_STOP 12
>>> +#define KEY_DM365_FF 13
>>> +#define KEY_DM365_SKIPPLUL 14
>>> +#define KEY_DM365_PLAYPAUSE 15
>>> +
>>> +#ifdef CONFIG_KEYBOARD_DAVINCI
>>> +static unsigned short dm365evm_keymap[] = {
>>> + KEY_DM365_KEY2,
>>> + KEY_DM365_LEFT,
>>> + KEY_DM365_EXIT,
>>> + KEY_DM365_DOWN,
>>> + KEY_DM365_ENTER,
>>> + KEY_DM365_UP,
>>> + KEY_DM365_KEY1,
>>> + KEY_DM365_RIGHT,
>>> + KEY_DM365_MENU,
>>> + KEY_DM365_REC,
>>> + KEY_DM365_REW,
>>> + KEY_DM365_SKIPMINUS,
>>> + KEY_DM365_STOP,
>>> + KEY_DM365_FF,
>>> + KEY_DM365_SKIPPLUL,
>>> + KEY_DM365_PLAYPAUSE,
>>
>> These are not standard key codes, why don't you use the ones defined in
>> linux/input.h?
>>
>
> These keys make sense for the DM365 EVM, they are defined in the board
> specific file which is the proper way to do that. Using the standard
> keys would be confusing for identifying the real key names defined in
> the board itself. Is it really necessary to use the standard keys?, if
> not lets keep the board specific names.
> --
> 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
In case that the standard keys should be used what are the proper key codes for
these 16 keys?
next prev parent reply other threads:[~2009-09-25 14:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 16:54 [PATCH 2/3] Davinci: DM365: Enable DaVinci Key Scan support for DM365 EVM miguel.aguilar
2009-09-25 4:01 ` Dmitry Torokhov
2009-09-25 14:09 ` Miguel Aguilar
2009-09-25 14:26 ` Miguel Aguilar [this message]
2009-09-28 17:02 ` 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=4ABCD318.5080307@ridgerun.com \
--to=miguel.aguilar@ridgerun.com \
--cc=clark.becker@ridgerun.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=diego.dompe@ridgerun.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=nsnehaprabha@ti.com \
--cc=santiago.nunez@ridgerun.com \
--cc=todd.fischer@ridgerun.com \
/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).