From: Weike Chen <alvin.chen@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
Boon Leong Ong <boon.leong.ong@intel.com>,
Andriy Shevchenko <andriy.shevchenko@intel.com>,
Mika Westerberg <mika.westerberg@intel.com>,
Hock Leong Kweh <hock.leong.kweh@intel.com>,
Darren Hart <dvhart@linux.intel.com>,
Alvin Chen <alvin.chen@intel.com>
Subject: [PATCH 0/3] The Designware GPIO Supporting
Date: Wed, 27 Aug 2014 10:46:25 -0700 [thread overview]
Message-ID: <1409161588-19417-1-git-send-email-alvin.chen@intel.com> (raw)
Hi,
These patches are for Intel Quark X1000 designware GPIO supporting. The first
patch enables the Synopsys DesignWare APB GPIO driver to support the MFD device.
And the Quark designware GPIO controller is registered as MFD device,
because Quark exports a single PCI device with both GPIO and I2C functions.
It is about reviewing the GPIO changes in gpio-dwapb, and in near future,
the Quark I2C driver and the MFD driver that binds these GPIO & I2C
functions will be sent subsequently. The second patch enables the gpio
'debounce' feature. And the third patch enables the power management.
Weike Chen (3):
GPIO: gpio-dwapb: Enable platform driver binding to MFD driver
GPIO: gpio-dwapb: Support Debounce
GPIO: gpio-dwapb: Suspend & Resume PM enabling
drivers/gpio/Kconfig | 1 -
drivers/gpio/gpio-dwapb.c | 296 +++++++++++++++++++++++++-----
include/linux/platform_data/gpio-dwapb.h | 32 ++++
3 files changed, 280 insertions(+), 49 deletions(-)
create mode 100644 include/linux/platform_data/gpio-dwapb.h
--
1.7.9.5
next reply other threads:[~2014-08-27 9:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 17:46 Weike Chen [this message]
2014-08-27 17:46 ` [PATCH 1/3] GPIO: gpio-dwapb: Enable platform driver binding to MFD driver Weike Chen
[not found] ` <1409161588-19417-2-git-send-email-alvin.chen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-09-03 6:57 ` Linus Walleij
2014-09-03 20:03 ` Sebastian Andrzej Siewior
2014-09-04 2:00 ` Chen, Alvin
[not found] ` <20140904073027.GA3336@breakpoint.cc>
[not found] ` <4656BEB6164FC34F8171C6538F1A595B2E982558@SHSMSX101.ccr.corp.intel.com>
2014-09-04 12:01 ` Shevchenko, Andriy
2014-08-27 17:46 ` [PATCH 2/3] GPIO: gpio-dwapb: Support Debounce Weike Chen
2014-08-28 15:11 ` atull
2014-08-29 7:38 ` Shevchenko, Andriy
2014-09-01 3:03 ` Chen, Alvin
2014-08-27 17:46 ` [PATCH 3/3] GPIO: gpio-dwapb: Suspend & Resume PM enabling Weike Chen
2014-08-27 16:15 ` atull
2014-08-28 1:09 ` Chen, Alvin
2014-08-28 15:01 ` atull
2014-09-01 3:20 ` Chen, Alvin
[not found] ` <1409161588-19417-4-git-send-email-alvin.chen-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-09-04 16:45 ` Linus Walleij
2014-09-05 2:09 ` Chen, Alvin
2014-09-05 8:00 ` Linus Walleij
2014-09-05 8:20 ` Chen, Alvin
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=1409161588-19417-1-git-send-email-alvin.chen@intel.com \
--to=alvin.chen@intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=boon.leong.ong@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dvhart@linux.intel.com \
--cc=gnurou@gmail.com \
--cc=grant.likely@linaro.org \
--cc=hock.leong.kweh@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@intel.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).