linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@codeaurora.org>
To: Trilok Soni <tsoni@codeaurora.org>
Cc: "Arve Hjønnevåg" <arve@android.com>,
	linux-arm-msm@vger.kernel.org, linux-input@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] msm: trout: add keypad support
Date: Fri, 10 Dec 2010 09:10:30 -0800	[thread overview]
Message-ID: <1292001031.8027.9.camel@m0nster> (raw)
In-Reply-To: <4D01D776.6000309@codeaurora.org>

On Fri, 2010-12-10 at 13:02 +0530, Trilok Soni wrote:

> To support this, we need to override the input device .name and submit the patches
> for matrix keypad and gpio keys and let the name come through platform data. 
> 
> You can refer how I am doing in PM8058 keypad driver patch.

ok ..

> But the real question is why can't we just do this in userspace? we should be able
> to override the keymap using setkeycode functionality, isn't it?

It might be possible, but some of the keys are missing in some of the
configurations .. If you had one big configuration with all of the gpio
lines, it might be possible that the missing gpio lines aren't
configured or don't exist.

Daniel

-- 
Sent by an consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum.



  reply	other threads:[~2010-12-10 17:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09  0:24 [PATCH] msm: trout: add keypad support Daniel Walker
2010-12-09  6:34 ` Arce, Abraham
2010-12-09  7:02   ` Trilok Soni
2010-12-09  7:06 ` Trilok Soni
2010-12-09 17:45   ` Daniel Walker
2010-12-09 22:01     ` Arve Hjønnevåg
2010-12-09 22:03       ` Daniel Walker
2010-12-10  7:32         ` Trilok Soni
2010-12-10 17:10           ` Daniel Walker [this message]
2010-12-13 18:41           ` Daniel Walker
2010-12-14  6:49             ` Trilok Soni
2010-12-15  7:48 ` Pavel Machek

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=1292001031.8027.9.camel@m0nster \
    --to=dwalker@codeaurora.org \
    --cc=arve@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).