From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Antoine Tenart <antoine.tenart@free-electrons.com>
Cc: ptyser@xes-inc.com, lee.jones@linaro.org,
linus.walleij@linaro.org, gnurou@gmail.com,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
Mathias Nyman <mathias.nyman@linux.intel.com>
Subject: Re: [PATCH 0/3] gpio: Intel Baytrail support
Date: Mon, 25 Jan 2016 13:49:03 +0200 [thread overview]
Message-ID: <20160125114903.GE1790@lahna.fi.intel.com> (raw)
In-Reply-To: <1453566729-30220-1-git-send-email-antoine.tenart@free-electrons.com>
On Sat, Jan 23, 2016 at 05:32:06PM +0100, Antoine Tenart wrote:
> This series introduces the GPIO Intel Baytrail support, using both the
> lpc ich and the gpio ich drivers.
>
> Antoine Tenart (3):
> gpio: gpio-ich: add support for Intel Baytrail
Intel Baytrail support has been in mainline kernel for quite some time
already. The driver is drivers/pintctrl/intel/pinctrl-baytrail.c.
Also the ICH GPIO block is not compatible to Baytrail which is why there
is a separate driver in the first place. Have you tested this series on
Baytrail?
> mfd: lpc_ich: use a correct mask for the GPIO base address
> mfd: lpc_ich: add GPIO support for Baytrail
All Baytrails I've seen expose the GPIO device via ACPI namespace so
there should be no need for the above two patches.
prev parent reply other threads:[~2016-01-25 11:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 16:32 [PATCH 0/3] gpio: Intel Baytrail support Antoine Tenart
2016-01-23 16:32 ` [PATCH 1/3] gpio: gpio-ich: add support for Intel Baytrail Antoine Tenart
2016-01-25 12:43 ` Lee Jones
2016-01-23 16:32 ` [PATCH 2/3] mfd: lpc_ich: use a correct mask for the GPIO base address Antoine Tenart
2016-01-25 12:44 ` Lee Jones
2016-01-25 16:07 ` Peter Tyser
2016-02-11 17:12 ` Lee Jones
2016-01-23 16:32 ` [PATCH 3/3] mfd: lpc_ich: add GPIO support for Baytrail Antoine Tenart
2016-01-25 12:45 ` Lee Jones
2016-01-28 10:34 ` Linus Walleij
2016-01-28 15:48 ` Mika Westerberg
2016-01-25 11:49 ` Mika Westerberg [this message]
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=20160125114903.GE1790@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=antoine.tenart@free-electrons.com \
--cc=gnurou@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=ptyser@xes-inc.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).