All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-gpio@vger.kernel.org, Jean Delvare <jdelvare@suse.de>,
	Mathias Nyman <mathias.nyman@linux.intel.com>
Subject: Re: Can't pinctrl-baytrail be a module?
Date: Thu, 11 Feb 2016 14:56:45 +0200	[thread overview]
Message-ID: <20160211125645.GU16826@lahna.fi.intel.com> (raw)
In-Reply-To: <s5hwpqbh0v7.wl-tiwai@suse.de>

+Jean and Mathias

On Thu, Feb 11, 2016 at 01:45:16PM +0100, Takashi Iwai wrote:
> Hi,
> 
> while discussing whether to enable pinctrl drivers on openSUSE distro 
> kernels, I wonder why pinctrl-baytrail is built-in only.  Basically
> the forced built-in is the only reason against the enablement in
> distro kernels.
> 
> The other Intel pinctrl drivers seem to be tristate.
> Any missing piece there?

Jean sent a patch against this couple of hours ago. I explained to him
that there is some ACPI GPIO magic happening on Baytrail-T based
machines such as Asus T100 where the GPIO driver is needed early at
boot, or something along those lines. I've CC'd Mathias Nyman the
original author who hopefully remembers this better.

  reply	other threads:[~2016-02-11 12:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11 12:45 Can't pinctrl-baytrail be a module? Takashi Iwai
2016-02-11 12:56 ` Mika Westerberg [this message]
2016-02-11 13:08   ` Takashi Iwai
2016-02-11 13:44     ` Mathias Nyman
2016-02-12 12:59       ` Takashi Iwai
2016-08-02  8:38         ` Jean Delvare

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=20160211125645.GU16826@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@linux.intel.com \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.