From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Daniel Mack <daniel@zonque.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"dh.herrmann@gmail.com" <dh.herrmann@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2] Input: Add driver for Microchip's CAP1106
Date: Tue, 15 Jul 2014 09:41:49 -0700 [thread overview]
Message-ID: <20140715164149.GA40351@core.coreip.homeip.net> (raw)
In-Reply-To: <20140715085138.GR26465@leverpostej>
Hi Mark,
On Tue, Jul 15, 2014 at 09:51:38AM +0100, Mark Rutland wrote:
> On Mon, Jul 14, 2014 at 11:20:17AM +0100, Daniel Mack wrote:
> >
> > linux,keycode feels a bit overkill here though, so I'd rather go for a
> > fixed-size linux,keycodes property. The number of entries is fixed,
> > anyway. Would you be fine with that?
>
> Assuming no-one's likely to want a sparse keymap (i.e. one where some
> keys do nothing) then that's probably ok.
For such a small keymap, if one does not want to use some of the
buttons, setting corresponding entries to KEY_RESERVED should work well.
> >
> > I took that from the gpio-keys driver. Is there a better way to denote
> > such a feature?
>
> Unfortunately not, given current practice. My gripe is that it's a Linux
> detail that were describing rather than a property of the device. We can
> forget about that for now.
I prefer looking at it as user expressing the desired behavior of the
driver; it is up to OS to deliver such behavior ;)
Thanks.
--
Dmitry
next prev parent reply other threads:[~2014-07-15 16:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 10:06 [PATCH v2] Input: Add driver for Microchip's CAP1106 Daniel Mack
2014-07-14 9:52 ` Mark Rutland
2014-07-14 10:20 ` Daniel Mack
2014-07-15 8:51 ` Mark Rutland
2014-07-15 9:12 ` Daniel Mack
2014-07-15 14:42 ` Mark Rutland
2014-07-15 16:41 ` Dmitry Torokhov [this message]
2014-07-15 17:17 ` Mark Rutland
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=20140715164149.GA40351@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=broonie@kernel.org \
--cc=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=dh.herrmann@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=mark.rutland@arm.com \
/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).