From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Alexandre Courbot <gnurou@gmail.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Zhu Lejun <lejun.zhu@linux.intel.com>,
Yang Bin <bin.yang@intel.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] gpio: Convert two Intel GPIO drivers to use irqchip helpers
Date: Fri, 25 Jul 2014 09:54:45 +0300 [thread overview]
Message-ID: <1406271288-15995-1-git-send-email-mika.westerberg@linux.intel.com> (raw)
Hi,
As discussed in this thread:
https://www.mail-archive.com/linux-gpio%40vger.kernel.org/msg02929.html
This series converts the Intel Lynxpoint and Baytrail GPIO drivers to use
the new irqchip helper functions and then moves ACPI event registration to
happen in the helpers as well.
Mika Westerberg (3):
gpio: lynxpoint: Convert to use gpiolib irqchip
pinctrl: baytrail: Convert to use gpiolib irqchip
gpio / ACPI: Move event handling registration to gpiolib irqchip helpers
drivers/gpio/Kconfig | 2 +-
drivers/gpio/gpio-lynxpoint.c | 93 ++++++++++----------------------------
drivers/gpio/gpiolib-acpi.c | 38 ++++++++++++----
drivers/gpio/gpiolib.c | 4 ++
drivers/gpio/gpiolib.h | 9 ++++
drivers/pinctrl/Kconfig | 2 +-
drivers/pinctrl/pinctrl-baytrail.c | 87 ++++++++---------------------------
7 files changed, 87 insertions(+), 148 deletions(-)
--
2.0.1
next reply other threads:[~2014-07-25 6:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 6:54 Mika Westerberg [this message]
2014-07-25 6:54 ` [PATCH 1/3] gpio: lynxpoint: Convert to use gpiolib irqchip Mika Westerberg
2014-07-25 6:54 ` [PATCH 2/3] pinctrl: baytrail: " Mika Westerberg
2014-07-25 6:54 ` [PATCH 3/3] gpio / ACPI: Move event handling registration to gpiolib irqchip helpers Mika Westerberg
2014-07-28 10:22 ` [PATCH 0/3] gpio: Convert two Intel GPIO drivers to use " Linus Walleij
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=1406271288-15995-1-git-send-email-mika.westerberg@linux.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=bin.yang@intel.com \
--cc=gnurou@gmail.com \
--cc=lejun.zhu@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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).