From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Michael Hennerich <michael.hennerich@analog.com>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"device-drivers-devel@blackfin.uclinux.org"
<device-drivers-devel@blackfin.uclinux.org>,
Drivers <Drivers@analog.com>
Subject: Re: [PATCH] input: keyboard: adp5589-keys: Add support for the ADP5585 derivatives
Date: Thu, 4 Aug 2011 00:55:42 -0700 [thread overview]
Message-ID: <20110804075542.GC31276@core.coreip.homeip.net> (raw)
In-Reply-To: <4E3A4EFD.5030507@analog.com>
On Thu, Aug 04, 2011 at 09:49:17AM +0200, Michael Hennerich wrote:
> On 08/04/2011 05:19 AM, Dmitry Torokhov wrote:
> >On Wed, Aug 03, 2011 at 10:30:08AM +0200, Michael Hennerich wrote:
> >>On 07/29/2011 03:00 PM, michael.hennerich@analog.com wrote:
> >>>From: Michael Hennerich<michael.hennerich@analog.com>
> >>>
> >>>The ADP5585 family keypad decoder and IO expander is similar to the ADP5589,
> >>>however it features less IO pins, and lacks hardware assisted key-lock
> >>>functionality. Unfortunately the register addresses are different, as well as
> >>>the event codes and bit organization within the port related registers.
> >>>
> >>>Move ADP5589 Register defines from the header file into the main source file.
> >>>Add new defines while making sure we don't break existing platform_data.
> >>>Add register address translation, and turn device specific defines into variables.
> >>>Introduce some helper functions and disable functions that doesn't
> >>>exist on the added devices.
> >>>
> >>>Signed-off-by: Michael Hennerich<michael.hennerich@analog.com>
> >>>---
> >>> drivers/input/keyboard/Kconfig | 4 +-
> >>> drivers/input/keyboard/adp5589-keys.c | 607 ++++++++++++++++++++++++++-------
> >>> include/linux/input/adp5589.h | 157 ++++-----
> >>> 3 files changed, 549 insertions(+), 219 deletions(-)
> >>>
> >>Hi Dmitry,
> >>
> >>If you prefer support for the ADP5585 as separate driver, please let
> >>me know.
> >Hi Michael,
> >
> >No, I actually like this approach very much, but do you think we could
> >have adp5589-keys.c, adp5585-keys.c and adp558x-keys-core.c? The
> >register definitions put all in one file are a bit overwhelming...
>
> Hi Dmitry,
>
> The register look-up table used for the ADP5585 also requires the
> ADP5589 defines.
> Also the core file would need the ADP5589 defines. So I don't think
> splitting stuff into
> 3 source files will greatly improve things.
Hmm... let me mull this over...
--
Dmitry
next prev parent reply other threads:[~2011-08-04 7:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 13:00 [PATCH] input: keyboard: adp5589-keys: Add support for the ADP5585 derivatives michael.hennerich
2011-08-03 8:30 ` Michael Hennerich
2011-08-04 3:19 ` Dmitry Torokhov
2011-08-04 7:49 ` Michael Hennerich
2011-08-04 7:55 ` Dmitry Torokhov [this message]
2011-09-02 8:08 ` Hennerich, Michael
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=20110804075542.GC31276@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=Drivers@analog.com \
--cc=device-drivers-devel@blackfin.uclinux.org \
--cc=linux-input@vger.kernel.org \
--cc=michael.hennerich@analog.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).