mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: riyer@nvidia.com
Cc: jj@chaosbits.net, tsoni@codeaurora.org, shubhrajyoti@ti.com,
	ccross@android.com, konkers@android.com, olof@lixom.net,
	achew@nvidia.com, linux-tegra@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH v3] input: tegra-kbc - Add tegra keyboard driver
Date: Mon, 10 Jan 2011 14:16:24 -0800	[thread overview]
Message-ID: <20110110221624.GA16445@core.coreip.homeip.net> (raw)
In-Reply-To: <1294422307-19107-1-git-send-email-riyer@nvidia.com>

Hi Rakesh,

On Fri, Jan 07, 2011 at 09:45:07AM -0800, riyer@nvidia.com wrote:
> +
> +struct tegra_kbc {
> +	void __iomem *mmio;
> +	struct input_dev *idev;
> +	int irq;
> +	unsigned int wake_enable_rows;
> +	unsigned int wake_enable_cols;
> +	spinlock_t lock;
> +	unsigned int repoll_time;
> +	unsigned long cp_dly_jiffies;
> +	int fifo[KBC_MAX_KPENT];
> +	const struct tegra_kbc_platform_data *pdata;
> +	int *plain_keycode;
> +	int *fn_keycode;

There should not be separate keycodes for FN and normal kys - FN is just
a modifier, like SHIFT or CTRL or ALT are and shoudl be handled in upper
layers.

Also you should wire up keycode/keycodemax/keycodesize in input_dev
structuire so that keymap can be retrieved via EVIOCGKEYCODE and
modified via EVIOGSKEYCODE. Also, because keymap is modifiable, the
original keymap should be copied in per-device structure, leaving
original intact. It (the original) also should be marked as const.

Since this papears to be a matrix keypad consider using definitions from
linux/input/matrix_keypad.h

Thank you.

-- 
Dmitry

  parent reply	other threads:[~2011-01-10 22:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07 17:45 riyer
2011-01-10 19:40 ` Rakesh Iyer
2011-01-10 20:53 ` Trilok Soni
2011-01-10 21:11   ` Rakesh Iyer
2011-01-11  7:24     ` Trilok Soni
2011-01-11  7:41       ` Colin Cross
2011-01-10 22:16 ` Dmitry Torokhov [this message]
2011-01-10 22:49   ` Rakesh Iyer
2011-01-10 23:06     ` Dmitry Torokhov
2011-01-11 19:34       ` Rakesh Iyer
2011-01-11 20:01         ` Dmitry Torokhov
2011-01-11 14:33     ` Pavel Machek
     [not found] ` <AANLkTimUrKOX6ydXx8zUukk2+fBYQxEsp3=6qZwm5KRD@mail.gmail.com>
2011-01-10 23:33   ` Mohamed Ikbel Boulabiar
2011-01-10 23:56     ` Rakesh Iyer
2011-01-11  7:22     ` Trilok Soni

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=20110110221624.GA16445@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=achew@nvidia.com \
    --cc=ccross@android.com \
    --cc=jj@chaosbits.net \
    --cc=konkers@android.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=riyer@nvidia.com \
    --cc=shubhrajyoti@ti.com \
    --cc=tsoni@codeaurora.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

all inboxes | Powered by JetHome®