All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarod Wilson <jarod@redhat.com>
To: Dharam Kumar <dharam.kumar.gupta@gmail.com>
Cc: linux-input <linux-input@vger.kernel.org>
Subject: Re: Missing Key-codes from <linux/input.h> file
Date: Mon, 25 Jun 2012 10:26:06 -0400	[thread overview]
Message-ID: <20120625142606.GA13212@redhat.com> (raw)
In-Reply-To: <CAOt5+pRZ=qqEZ2Ra3yFbLqoHhDGFkzHs4cEXvFv5trbukd4MdA@mail.gmail.com>

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


  reply	other threads:[~2012-06-25 14:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25 14:09 Missing Key-codes from <linux/input.h> file Dharam Kumar
2012-06-25 14:26 ` Jarod Wilson [this message]
2012-06-25 14:45   ` Dharam Kumar
2012-06-28  6:14     ` Dharam Kumar

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=20120625142606.GA13212@redhat.com \
    --to=jarod@redhat.com \
    --cc=dharam.kumar.gupta@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 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.