linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: Paulius Zaleckas <paulius.zaleckas@teltonika.lt>
Cc: linux-input@vger.kernel.org, s.hauer@pengutronix.de,
	linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: [PATCH, v2] input/imx2x: generic keypad handler for i.MX SoCs
Date: Fri, 17 Apr 2009 21:26:44 +0200	[thread overview]
Message-ID: <200904172126.45126.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <49E8A70B.3020209@teltonika.lt>

> IMO it would be better if board code would not provide
> "handle" function, but instead it would provide 'keyboard <->
> input event' map structure/array.

Not in my context.

Currently, a map can only do a stateless transposition. It cannot 
implement a cell-phone like keyboard, e.g. one press on the key 
yields a "1" input event, two presses yield a "a", three a "b", 
four a "c".

One can argue that you can do this in user-space, but for one of 
my devices (not for which this patch is) the 
kernel-implementation of this allows me to switch to vc1 
(framebuffer console) and log in and issue commands via the 
cell-phone like keyboard.

  reply	other threads:[~2009-04-17 19:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 14:40 [PATCH, v2] input/imx2x: generic keypad handler for i.MX SoCs Holger Schurig
2009-04-17 14:55 ` Holger Schurig
2009-04-17 15:47 ` Lothar Waßmann
2009-04-17 19:23   ` Holger Schurig
2009-04-18  7:51     ` Russell King - ARM Linux
2009-04-17 15:58 ` Paulius Zaleckas
2009-04-17 19:26   ` Holger Schurig [this message]
2009-04-17 16:04 ` Dmitry Torokhov
2009-04-17 19:40   ` Holger Schurig
2009-04-18 23:15     ` Dmitry Torokhov
2009-04-20 11:08       ` Holger Schurig
2009-04-18 14:27 ` Sascha Hauer
2009-06-05  9:51 ` Martin Fuzzey

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=200904172126.45126.hs4233@mail.mn-solutions.de \
    --to=hs4233@mail.mn-solutions.de \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-input@vger.kernel.org \
    --cc=paulius.zaleckas@teltonika.lt \
    --cc=s.hauer@pengutronix.de \
    /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).