From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Jean Delvare <jdelvare@suse.de>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Mathias Nyman <mathias.nyman@intel.com>
Subject: Re: [PATCH] pinctrl: intel: Turn Baytrail support to tristate
Date: Tue, 16 Feb 2016 10:53:46 +0200 [thread overview]
Message-ID: <20160216085346.GA1742@lahna.fi.intel.com> (raw)
In-Reply-To: <CACRpkdaBBeZbbZGduHOJKuqQmCdyXaMatFt97Bjxsbfdf6V3Rw@mail.gmail.com>
On Tue, Feb 16, 2016 at 12:13:36AM +0100, Linus Walleij wrote:
> On Thu, Feb 11, 2016 at 12:23 PM, Mika Westerberg
> <mika.westerberg@linux.intel.com> wrote:
> > On Thu, Feb 11, 2016 at 12:05:51PM +0100, Jean Delvare wrote:
> >> The pinctrl-baytrail driver builds just fine as a module so give
> >> users this option.
> >
> > IIRC the reason why this is built-in is that there are all kind of ACPI
> > GPIO magic happening behind the scenes on Baytrail-T based machines
> > (such as Asus T100) and it does not work without the GPIO driver. Some
> > of the stuff is done pretty early too.
>
> Hm I wonder if that could be the case for the AMD driver that just
> got tristated too...
If they use ACPI GPIO events and operation regions early at boot then it
can be the case.
next prev parent reply other threads:[~2016-02-16 8:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 11:05 [PATCH] pinctrl: intel: Turn Baytrail support to tristate Jean Delvare
2016-02-11 11:23 ` Mika Westerberg
2016-02-15 23:13 ` Linus Walleij
2016-02-16 8:53 ` Mika Westerberg [this message]
2016-02-16 9:15 ` Jean Delvare
2016-02-16 9:49 ` Mika Westerberg
2016-02-16 10:25 ` Jean Delvare
2016-02-16 10:34 ` Mika Westerberg
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=20160216085346.GA1742@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=jdelvare@suse.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mathias.nyman@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;
as well as URLs for NNTP newsgroup(s).