linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dmitry.torokhov@gmail.com (Dmitry Torokhov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 4/5(7)] input: serio: add support for Amstrad Delta serial keyboard port
Date: Tue, 4 May 2010 13:58:00 -0700	[thread overview]
Message-ID: <20100504205800.GD29428@core.coreip.homeip.net> (raw)
In-Reply-To: <20100504204836.GJ30601@n2100.arm.linux.org.uk>

On Tue, May 04, 2010 at 09:48:36PM +0100, Russell King - ARM Linux wrote:
> On Tue, May 04, 2010 at 01:40:41PM -0700, Tony Lindgren wrote:
> > * Janusz Krzysztofik <jkrzyszt@tis.icnet.pl> [100427 18:09]:
> > > The patch introduces a serio driver that supports a keyboard serial port found
> > > on the Amstrad Delta videophone board.
> > > 
> > > After initializing the hardware, the driver reads its input data from a buffer
> > > filled in by the board FIQ (Fast Interrupt Request) handler.
> > > 
> > > Standard AT keyboard driver (atkbd) will be used on top of the serio layer for 
> > > handling the E3 keyboard (called mailboard) connected to the port. Since the 
> > > device generated scancodes differ from what the atkbd expects, a custom key 
> > > code to scan code table must be loaded from userspace for the keyboard to be 
> > > useable.
> 
> What's the rationale for this approach?  There's no requirement for the
> atkbd driver to be used for all keyboards.  It seems very obscure (and
> backward) way to do things.
> 
> Why not implement the serio driver for the IO level, and a separate
> keyboard driver which can handle the protocol and interpret the
> scancodes?

Because it is AT-like keyboard with messed up scancodes, it responds to
our probes as a regular keyboard so we can't auto-select proper keymap.
If you were to connect a standard PS/2 keyboard to E3 port it would work
without any special keymap.

-- 
Dmitry

  reply	other threads:[~2010-05-04 20:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28  0:52 [PATCH v4 0/5(7)] OMAP1: Amstrad Delta: add FIQ based support for external keyboard Janusz Krzysztofik
2010-04-28  0:58 ` [PATCH v4 0.1/5(7)] OMAP: add missing FIQ_START definition required for arch/arm/kernel/fiq.c compilation Janusz Krzysztofik
2010-04-28  2:15   ` [RESUBMIT] " Janusz Krzysztofik
2010-04-28  1:01 ` [PATCH v4 1/5(7)] OMAP1: Amstrad Delta: add FIQ handler for serial keyboard port interrupt processing Janusz Krzysztofik
2010-04-28  1:03 ` [PATCH v4 2/5(7)] OMAP1: Amstrad Delta: add a handler for processing interrupts generated by the FIQ routine Janusz Krzysztofik
2010-04-28  1:05 ` [PATCH v4 2.1/5(7)] OMAP1: Amstrad Delta: update board initialization code for complete modem IRQ GPIO line setup Janusz Krzysztofik
2010-04-28  1:07 ` [PATCH v4 3/5(7)] OMAP1: Amstrad Delta: use FIQ for processing GPIO interrupts Janusz Krzysztofik
2010-04-28  1:10 ` [PATCH v4 4/5(7)] input: serio: add support for Amstrad Delta serial keyboard port Janusz Krzysztofik
2010-05-04 20:40   ` Tony Lindgren
2010-05-04 20:48     ` Russell King - ARM Linux
2010-05-04 20:58       ` Dmitry Torokhov [this message]
2010-04-28  1:14 ` [PATCH v4 5/5(7)] OMAP1: Amstrad Delta: modify defconfig for external keyboard support Janusz Krzysztofik

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=20100504205800.GD29428@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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 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).