Re: [PATCH v5 1/2] Input: gpio_keys.c: Added support for device-tree platform data

[David Jander <david.jander@protonic.nl>]

On Thu, 23 Jun 2011 07:25:37 -0600
Grant Likely <grant.likely@secretlab.ca> wrote:

> On Thu, Jun 23, 2011 at 6:39 AM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> >> > +       - gpios: OF devcie-tree gpio specificatin.
> >> > +       - label: Descriptive name of the key.
> >> > +       - linux,code: Keycode to emit.
> >>
> >> The fact that this is the Linux internal keycode definitions still
> >> makes me nervous.  Is there no existing standard for keycodes emitted
> >> by keyboard devices?
> >
> > There is but no standard lookup table. For Intel MID we do a translation
> > between Linux key names in the firmware and keycodes but there isn't a
> > generic helper for it.
> 
> I suppose the Linux keycodes are exported out to userspace, and are
> therefore an ABI which will not change.  Okay.

Right.
If I am not mistaken, it started out being AT keyboard scancodes one day, but
nowadays it is a huge (and very useful) list of all possible keyboard-like
input events that can exist in linux. We use one such handy niche-code:
CYCLE_WINDOWS. We couldn't use this code if we were forced to emulate some
existing keyboard which probably wouldn't have this nifty key. It just fits
perfectly the intended function of the key. I have openbox configured to
handle it more or less like ALT+TAB.

Best regards,

-- 
David Jander
Protonic Holland.
--
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