From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: David Cohen <david.a.cohen@linux.intel.com>
Cc: Felipe Balbi <balbi@ti.com>,
Linus Walleij <linus.walleij@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
stable <stable@vger.kernel.org>,
mathias.nyman@linux.intel.com
Subject: Re: [PATCH] pinctrl: baytrail: show output gpio state correctly on Intel Baytrail
Date: Mon, 3 Nov 2014 11:24:02 +0200 [thread overview]
Message-ID: <20141103092402.GA1304@lahna.fi.intel.com> (raw)
In-Reply-To: <20141031184509.GA2224@psi-dev26.jf.intel.com>
On Fri, Oct 31, 2014 at 11:45:09AM -0700, David Cohen wrote:
> > I think adding the module exit + allowing this driver to be a module
> > would be a good approach. Then we don't need to force generic x86 kernel
> > binaries to always have this driver. Unless Mathias or Mika knows a
> > constraint to force this driver to be builtin only.
>
> It helps if I CC them when asking for feedback :)
>
> Mathias, Mika, do you know any constraint that forces pinctrl-baytrail
> to be bool?
The only constraint that has been keeping this driver as bool is that
some machines like, Asus T100, uses ACPI GPIO operation regions for
toggling GPIOs to get things like sensor hub powered on. The GPIO
operation region code does not yet handle -EPROBE_DEFER so only way to
ensure that the operation region is there is to have the driver compiled
in to the kernel.
next prev parent reply other threads:[~2014-11-03 9:24 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1412355319-18946-1-git-send-email-david.a.cohen@linux.intel.com>
2014-10-13 18:23 ` [PATCH] pinctrl: baytrail: show output gpio state correctly on Intel Baytrail David Cohen
2014-10-13 19:14 ` Felipe Balbi
2014-10-13 19:24 ` David Cohen
2014-10-13 19:26 ` Felipe Balbi
2014-10-13 19:36 ` Felipe Balbi
2014-10-13 20:19 ` David Cohen
2014-10-28 10:15 ` Linus Walleij
2014-10-28 14:42 ` Felipe Balbi
2014-10-31 8:12 ` Linus Walleij
2014-10-31 13:20 ` Felipe Balbi
2014-10-31 16:23 ` David Cohen
2014-10-31 18:45 ` David Cohen
2014-11-03 9:24 ` Mika Westerberg [this message]
2014-11-03 15:00 ` Felipe Balbi
2014-11-03 15:27 ` Mika Westerberg
2014-11-03 15:35 ` Felipe Balbi
2014-11-03 15:42 ` Mika Westerberg
2014-11-03 15:50 ` Felipe Balbi
2014-11-03 18:42 ` Mika Westerberg
2014-11-03 20:40 ` Felipe Balbi
2014-11-04 7:51 ` Mika Westerberg
2014-11-04 14:44 ` Felipe Balbi
2014-11-03 22:19 ` David Cohen
2014-11-04 7:59 ` Mika Westerberg
2014-11-04 18:05 ` David Cohen
2014-11-04 18:57 ` Mika Westerberg
2014-11-04 19:11 ` David Cohen
2014-11-04 19:34 ` Mika Westerberg
2014-11-04 21:51 ` David Cohen
2014-11-05 8:40 ` Mika Westerberg
2014-11-14 9:40 ` Linus Walleij
2014-11-14 9:39 ` Linus Walleij
2014-11-14 9:53 ` Mika Westerberg
2014-11-14 23:19 ` Rafael J. Wysocki
2014-11-14 9:30 ` Linus Walleij
2014-11-03 15:33 ` Linus Walleij
2014-10-13 20:16 ` David Cohen
2014-10-14 17:54 ` [PATCH v2] " David Cohen
2014-10-14 18:19 ` Felipe Balbi
2014-10-28 10:17 ` 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=20141103092402.GA1304@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=balbi@ti.com \
--cc=david.a.cohen@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=stable@vger.kernel.org \
/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).