From: Daniel Mack <zonque@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: cap1106 - allow changing key mapping from userspace
Date: Thu, 07 Aug 2014 08:50:24 +0200 [thread overview]
Message-ID: <53E321B0.9040701@gmail.com> (raw)
In-Reply-To: <20140807062033.GD651@core.coreip.homeip.net>
Hi Dmitry,
On 08/07/2014 08:20 AM, Dmitry Torokhov wrote:
> On Sun, Jul 20, 2014 at 06:20:49PM -0700, Dmitry Torokhov wrote:
>> Wire up support for EVIOC{G|S}KEYCODE to allow users change key mappings
>> from userspace.
>>
>> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
>> ---
>>
>> Just compiled, not tested.
>
> *ping* Any chance you could give it a try? Thanks!
Oh, sorry, I didn't realize you're waiting for me on this.
Unfortunately, I can't test it myself anymore, as I had to return the
board I found this chip on. But as the change looks very straight
forward, I'd suggest you just apply that patch and I ask the vendor to
give it a quick try. In case of any problems, I'll let you know. Does
that sound feasible?
Thanks,
Daniel
>
>>
>> drivers/input/keyboard/cap1106.c | 8 +++++++-
>> 1 file changed, 7 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/input/keyboard/cap1106.c b/drivers/input/keyboard/cap1106.c
>> index f7d7a0d..180b184 100644
>> --- a/drivers/input/keyboard/cap1106.c
>> +++ b/drivers/input/keyboard/cap1106.c
>> @@ -64,7 +64,7 @@ struct cap1106_priv {
>> struct input_dev *idev;
>>
>> /* config */
>> - unsigned int keycodes[CAP1106_NUM_CHN];
>> + unsigned short keycodes[CAP1106_NUM_CHN];
>> };
>>
>> static const struct reg_default cap1106_reg_defaults[] = {
>> @@ -272,6 +272,12 @@ static int cap1106_i2c_probe(struct i2c_client *i2c_client,
>> for (i = 0; i < CAP1106_NUM_CHN; i++)
>> __set_bit(priv->keycodes[i], priv->idev->keybit);
>>
>> + __clear_bit(KEY_RESERVED, priv->idev->keybit);
>> +
>> + priv->idev->keycode = priv->keycodes;
>> + priv->idev->keycodesize = sizeof(priv->keycodes[0]);
>> + priv->idev->keycodemax = ARRAY_SIZE(priv->keycodes);
>> +
>> priv->idev->id.vendor = CAP1106_MANUFACTURER_ID;
>> priv->idev->id.product = CAP1106_PRODUCT_ID;
>> priv->idev->id.version = rev;
>> --
>> 2.0.0.526.g5318336
>>
>>
>> --
>> Dmitry
>
next prev parent reply other threads:[~2014-08-07 6:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 1:20 [PATCH] Input: cap1106 - allow changing key mapping from userspace Dmitry Torokhov
2014-08-07 6:20 ` Dmitry Torokhov
2014-08-07 6:50 ` Daniel Mack [this message]
2014-08-08 6:50 ` Dmitry Torokhov
2014-08-08 10:27 ` Daniel Mack
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=53E321B0.9040701@gmail.com \
--to=zonque@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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