From: qiujiang <qiujiang@huawei.com>
To: <linus.walleij@linaro.org>, <gnurou@gmail.com>
Cc: <mika.westerberg@linux.intel.com>, <andy.shevchenko@gmail.com>,
<linux-kernel@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
<linux-acpi@vger.kernel.org>, <linuxarm@huawei.com>,
<haifeng.wei@huawei.com>, <charles.chenxin@huawei.com>
Subject: [PATCH v3 0/2] gpio: designware: add gpio-signaled acpi events support for power button
Date: Wed, 24 Feb 2016 20:33:28 +0800 [thread overview]
Message-ID: <1456317210-42742-1-git-send-email-qiujiang@huawei.com> (raw)
This patchset adds gpio-signaled acpi events support for power button
on hisilicon D02 board.
The two patches respectively:
- switch device node to fwnode
- adds gpio-signaled acpi events support for power button
This patchset is based on
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git
branch "devel"
Changes v2 -> v3
- fixed the build error reported by Kbuild test robot
Changes v1 -> v2:
- rebase to branch "devel" of Linus Walleij's repository
- split in two patch as suggested by Andy S
- add Mika's ACKs
qiujiang (2):
gpio: designware: switch device node to fwnode
gpio: designware: add gpio-signaled acpi events support for power
button
drivers/gpio/gpio-dwapb.c | 66 ++++++++++++++++++++------------
drivers/mfd/intel_quark_i2c_gpio.c | 2 +-
include/linux/platform_data/gpio-dwapb.h | 2 +-
3 files changed, 43 insertions(+), 27 deletions(-)
--
1.9.1
next reply other threads:[~2016-02-24 12:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 12:33 qiujiang [this message]
2016-02-24 12:33 ` [PATCH v3 1/2] gpio: designware: switch device node to fwnode qiujiang
2016-02-24 13:46 ` Andy Shevchenko
2016-02-25 11:58 ` Jiang Qiu
2016-02-25 13:43 ` Andy Shevchenko
2016-02-27 7:15 ` Jiang Qiu
2016-02-29 10:46 ` Andy Shevchenko
2016-02-24 12:33 ` [PATCH v3 2/2] gpio: designware: add gpio-signaled acpi events support for power button qiujiang
2016-02-24 13:49 ` Andy Shevchenko
2016-02-25 12:13 ` Jiang Qiu
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=1456317210-42742-1-git-send-email-qiujiang@huawei.com \
--to=qiujiang@huawei.com \
--cc=andy.shevchenko@gmail.com \
--cc=charles.chenxin@huawei.com \
--cc=gnurou@gmail.com \
--cc=haifeng.wei@huawei.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mika.westerberg@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
all inboxes | Powered by JetHome®