From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Patch 1/2][PXA27x] initial keypad support
Date: Wed, 12 Dec 2007 06:05:58 +0100 [thread overview]
Message-ID: <fb249edb0712112105h160a342bo36d968500c1395aa@mail.gmail.com> (raw)
In-Reply-To: <475F3D80.3080102@kama-aina.net>
Hi,
On 12/12/2007, Armin <akuster@kama-aina.net> wrote:
> Here is an attempt to add PXA27x keypad support. It currently only
> supports the matrix type interface. It still needs direct and
> mulitswitch support added.
>
> Just wanted to get something out there for folks to pound on.
>
> Comment and feedback welcome.
Here are some comments:
* Several bits in KPC and KPREC should be reset on read. The IRQ
should be reset when it becomes masked in KPC, and potentially
asserted when it becomes unmasked.
* It's wasteful to go through all keys in the 8x8 matrix on every
event. It can be avoided easily by mapping qemu keycode to matrix
position, rather than position to keycode, for example the PalmT|E
matrix keypad does that.
* Please convert the indentation in the file to use spaces, before
considering for inclusion.
* The bit definitions and pxa2xx_keypad_s struct are local to the
keypad module so they shouldn't be in the header file exposed to the
whole world.
* Please set a copyright owner.
Regarding mainstone keypad patch:
* Probably not worth to stick the keymap in a file of its own since it
is not shared between different machines - it's an integral part of
mainstone.
Thanks,
Andrew
next prev parent reply other threads:[~2007-12-12 5:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 1:46 [Qemu-devel] [Patch 1/2][PXA27x] initial keypad support Armin
2007-12-12 5:05 ` andrzej zaborowski [this message]
2007-12-13 2:47 ` Armin
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=fb249edb0712112105h160a342bo36d968500c1395aa@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=qemu-devel@nongnu.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).