* Missing Key-codes from <linux/input.h> file
@ 2012-06-25 14:09 Dharam Kumar
2012-06-25 14:26 ` Jarod Wilson
0 siblings, 1 reply; 4+ messages in thread
From: Dharam Kumar @ 2012-06-25 14:09 UTC (permalink / raw)
To: linux-input
Hi,
I'm working on a module which is an input device and hence it needs to
report certain key events.
While browsing through the <linux/input.h>, I did find most of the
key-codes(which I need to use) already defined but not all.
Few of the KEY_xxx which i could not find are:
a.) A Key for going to the previous channel.
b.) Keys for Moving upper-right, lower-right, upper-left and
lower-left direction(probably a GUI(or a grid of icons),where you move
diagonally)
d.) A key for Subpicture (this 'subpicture' key is defined in CEA-931C).
Any pointers?
Thanks,
Dharam
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Missing Key-codes from <linux/input.h> file
2012-06-25 14:09 Missing Key-codes from <linux/input.h> file Dharam Kumar
@ 2012-06-25 14:26 ` Jarod Wilson
2012-06-25 14:45 ` Dharam Kumar
0 siblings, 1 reply; 4+ messages in thread
From: Jarod Wilson @ 2012-06-25 14:26 UTC (permalink / raw)
To: Dharam Kumar; +Cc: linux-input
On Mon, Jun 25, 2012 at 07:39:25PM +0530, Dharam Kumar wrote:
> Hi,
> I'm working on a module which is an input device and hence it needs to
> report certain key events.
>
> While browsing through the <linux/input.h>, I did find most of the
> key-codes(which I need to use) already defined but not all.
>
> Few of the KEY_xxx which i could not find are:
>
> a.) A Key for going to the previous channel.
I believe that's what this one is intended for:
#define KEY_PREVIOUS 0x19c
> b.) Keys for Moving upper-right, lower-right, upper-left and
> lower-left direction(probably a GUI(or a grid of icons),where you move
> diagonally)
Sounds a bit like joystick functionality, which already exists.
> d.) A key for Subpicture (this 'subpicture' key is defined in CEA-931C).
Could have sworn there was a picture-in-picture button, which may or may
not be the same thing, but I don't see it now...
--
Jarod Wilson
jarod@redhat.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Missing Key-codes from <linux/input.h> file
2012-06-25 14:26 ` Jarod Wilson
@ 2012-06-25 14:45 ` Dharam Kumar
2012-06-28 6:14 ` Dharam Kumar
0 siblings, 1 reply; 4+ messages in thread
From: Dharam Kumar @ 2012-06-25 14:45 UTC (permalink / raw)
To: Jarod Wilson; +Cc: linux-input
On Mon, Jun 25, 2012 at 7:56 PM, Jarod Wilson <jarod@redhat.com> wrote:
> On Mon, Jun 25, 2012 at 07:39:25PM +0530, Dharam Kumar wrote:
>> Hi,
>> I'm working on a module which is an input device and hence it needs to
>> report certain key events.
>>
>> While browsing through the <linux/input.h>, I did find most of the
>> key-codes(which I need to use) already defined but not all.
>>
>> Few of the KEY_xxx which i could not find are:
>>
>> a.) A Key for going to the previous channel.
>
> I believe that's what this one is intended for:
>
> #define KEY_PREVIOUS 0x19c
>
Hmm..I looked at it, but i was not sure ,whether it is the right key
code for the 'Previous channel'.
To be specific about what the key is supposed to do:
"Select the channel used before most recent new channel selection."
Also, there is another define:
#define KEY_LAST 0x195 /* Recall last */
confusing...No?
>> b.) Keys for Moving upper-right, lower-right, upper-left and
>> lower-left direction(probably a GUI(or a grid of icons),where you move
>> diagonally)
>
> Sounds a bit like joystick functionality, which already exists.
Will you please be bit more specfic? Which keys/defines exactly you
are talking about?
Apologies for me being so naive. :)
>
>> d.) A key for Subpicture (this 'subpicture' key is defined in CEA-931C).
>
> Could have sworn there was a picture-in-picture button, which may or may
> not be the same thing, but I don't see it now...
>
> --
> Jarod Wilson
> jarod@redhat.com
>
--
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Missing Key-codes from <linux/input.h> file
2012-06-25 14:45 ` Dharam Kumar
@ 2012-06-28 6:14 ` Dharam Kumar
0 siblings, 0 replies; 4+ messages in thread
From: Dharam Kumar @ 2012-06-28 6:14 UTC (permalink / raw)
To: Jarod Wilson; +Cc: linux-input
Hi Jarod, All
I'm giving some more info regarding what I queried earlier. I hope
this will put my query in better light.
The missing keys which I've mentioned earlier are basically Remote
Controller keys as specified in MHL specifications( www.mhltech.org ).
Now, as MHL Specifications are closely related to HDMI(and CEC), hence
most probably these 'missing' keys are part of HDMI/CEC specifications
too. And hence, my doubt on why these standard keys are missing from
<linux/input.h> ?
Jarod,
You previously mentioned some of the missing keys being similar to
Joystick keys. I will really appreciate if you could pin-point the
location of joystick keys' existence ? It makes sense to me too if
joystick(basically a wired remote control) keys are similar to
TV/Monitor Remote Control keys.
In case, the keys (like upper-left, upper-right, lower-left,
lower-right ) are different from Joystick keys(and hence missing from
input.h ), How can I proceed to add these keys ?
Thanks and Regards,
Dharam
On Mon, Jun 25, 2012 at 8:15 PM, Dharam Kumar
<dharam.kumar.gupta@gmail.com> wrote:
> On Mon, Jun 25, 2012 at 7:56 PM, Jarod Wilson <jarod@redhat.com> wrote:
>> On Mon, Jun 25, 2012 at 07:39:25PM +0530, Dharam Kumar wrote:
>>> Hi,
>>> I'm working on a module which is an input device and hence it needs to
>>> report certain key events.
>>>
>>> While browsing through the <linux/input.h>, I did find most of the
>>> key-codes(which I need to use) already defined but not all.
>>>
>>> Few of the KEY_xxx which i could not find are:
>>>
>>> a.) A Key for going to the previous channel.
>>
>> I believe that's what this one is intended for:
>>
>> #define KEY_PREVIOUS 0x19c
>>
>
> Hmm..I looked at it, but i was not sure ,whether it is the right key
> code for the 'Previous channel'.
> To be specific about what the key is supposed to do:
> "Select the channel used before most recent new channel selection."
> Also, there is another define:
> #define KEY_LAST 0x195 /* Recall last */
> confusing...No?
>
>>> b.) Keys for Moving upper-right, lower-right, upper-left and
>>> lower-left direction(probably a GUI(or a grid of icons),where you move
>>> diagonally)
>>
>> Sounds a bit like joystick functionality, which already exists.
>
> Will you please be bit more specfic? Which keys/defines exactly you
> are talking about?
> Apologies for me being so naive. :)
>>
>>> d.) A key for Subpicture (this 'subpicture' key is defined in CEA-931C).
>>
>> Could have sworn there was a picture-in-picture button, which may or may
>> not be the same thing, but I don't see it now...
>>
>> --
>> Jarod Wilson
>> jarod@redhat.com
>>
--
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-06-28 6:15 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-06-25 14:09 Missing Key-codes from <linux/input.h> file Dharam Kumar
2012-06-25 14:26 ` Jarod Wilson
2012-06-25 14:45 ` Dharam Kumar
2012-06-28 6:14 ` Dharam Kumar
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.