From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Alan Cox <alan@linux.intel.com>,
Ning Li <ning.li@intel.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] gpio: Add support for Intel Cherryview/Braswell GPIO controller
Date: Mon, 22 Sep 2014 14:19:41 +0300 [thread overview]
Message-ID: <20140922111941.GS1786@lahna.fi.intel.com> (raw)
In-Reply-To: <1410790185-31101-2-git-send-email-mika.westerberg@linux.intel.com>
On Mon, Sep 15, 2014 at 05:09:45PM +0300, Mika Westerberg wrote:
> From: Ning Li <ning.li@intel.com>
>
> This driver supports the GPIO controllers found in newer Intel SoCs like
> Cherryview and Braswell.
>
> Signed-off-by: Ning Li <ning.li@intel.com>
> Signed-off-by: Alan Cox <alan@linux.intel.com>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> ---
> drivers/gpio/Kconfig | 8 +
> drivers/gpio/Makefile | 1 +
> drivers/gpio/gpio-cherryview.c | 947 +++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 956 insertions(+)
> create mode 100644 drivers/gpio/gpio-cherryview.c
Hi GPIO maintainers,
Just checking if there is any comments to this driver?
If the ARCH_NR_GPIOS patch is not accepted as is (or we are even getting
rid of the limit), could you consider taking this driver patch to the
GPIO tree separately?
next prev parent reply other threads:[~2014-09-22 11:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 14:09 [PATCH v2 1/2] gpio: Increase ARCH_NR_GPIOs to 512 Mika Westerberg
2014-09-15 14:09 ` [PATCH v2 2/2] gpio: Add support for Intel Cherryview/Braswell GPIO controller Mika Westerberg
2014-09-22 11:19 ` Mika Westerberg [this message]
2014-09-24 9:10 ` Linus Walleij
2014-09-24 9:12 ` Linus Walleij
2014-09-24 9:29 ` Mika Westerberg
2014-09-15 16:50 ` [PATCH v2 1/2] gpio: Increase ARCH_NR_GPIOs to 512 Arnd Bergmann
2014-09-16 9:34 ` Mika Westerberg
2014-09-23 15:23 ` 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=20140922111941.GS1786@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=arnd@arndb.de \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ning.li@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