From: "Opensource [Steve Twiss]" <stwiss.opensource@diasemi.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Samuel Ortiz <sameo@linux.intel.com>
Cc: David Dajun Chen <david.chen@diasemi.com>,
LKML-INPUT <linux-input@vger.kernel.org>,
LKML-KERNEL <linux-kernel@vger.kernel.org>,
Mark Brown <broonie@linaro.org>,
Philipp Zabel <p.zabel@pengutronix.de>
Subject: [PATCH V1 0/2] da9063: Support for OnKey
Date: Mon, 10 Mar 2014 16:24:04 +0000 [thread overview]
Message-ID: <cover.1394468644.git.stwiss.opensource@diasemi.com> (raw)
From: Opensource [Steve Twiss] <stwiss.opensource@diasemi.com>
This patch series adds support for the DA9063 OnKey.
It has been split into two parts because the OnKey driver
requires a minor alteration to the da9063-core.c file and
the platform data header file. These parts have been
separated out.
- Add a new OnKey driver for DA9063;
- Minor addition "ONKEY" name to OnKey IRQ resource structure;
Thank you,
Steve Twiss, Dialog Semiconductor Ltd.
S Twiss (2):
mfd: da9063: Linkages for ONKEY support in core files
input: misc: da9063: OnKey driver
drivers/input/misc/Kconfig | 10 ++
drivers/input/misc/Makefile | 1 +
drivers/input/misc/da9063-onkey.c | 209 ++++++++++++++++++++++++++++++++++++++
drivers/mfd/da9063-core.c | 1 +
include/linux/mfd/da9063/pdata.h | 1 +
5 files changed, 222 insertions(+)
create mode 100644 drivers/input/misc/da9063-onkey.c
--
end-of-patch for PATCH V1
next reply other threads:[~2014-03-10 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 16:24 Opensource [Steve Twiss] [this message]
2014-03-10 16:24 ` [PATCH V1 2/2] input: misc: da9063: OnKey driver Opensource [Steve Twiss]
2014-03-10 16:24 ` [PATCH V1 1/2] mfd: da9063: Linkages for ONKEY support in core files Opensource [Steve Twiss]
2014-03-10 16:40 ` Lee Jones
2014-03-10 17:16 ` Opensource [Steve Twiss]
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=cover.1394468644.git.stwiss.opensource@diasemi.com \
--to=stwiss.opensource@diasemi.com \
--cc=broonie@linaro.org \
--cc=david.chen@diasemi.com \
--cc=dmitry.torokhov@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=sameo@linux.intel.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).