From: Jean Delvare <jdelvare@suse.de>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: Takashi Iwai <tiwai@suse.de>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org
Subject: Re: Can't pinctrl-baytrail be a module?
Date: Tue, 2 Aug 2016 10:38:01 +0200 [thread overview]
Message-ID: <20160802103801.765b8202@endymion> (raw)
In-Reply-To: <s5hh9hef5j2.wl-tiwai@suse.de>
On Fri, 12 Feb 2016 13:59:45 +0100, Takashi Iwai wrote:
> On Thu, 11 Feb 2016 14:44:28 +0100,
> Mathias Nyman wrote:
> >
> > On 11.02.2016 15:08, Takashi Iwai wrote:
> > > On Thu, 11 Feb 2016 13:56:45 +0100,
> > > Mika Westerberg wrote:
> > >>
> > >> +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 noticed it right after I send my mail, too, sorry :)
> > >
> > >> 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.
> > >
> > > I know of pinctrl-cherryview is needed before others like shdci, but
> > > for Baytrail-T, it's more than that?
> > >
> >
> > If I remember correctly the reason was that the gpio driver was supposed
> > to work with Hardware reduced ACPI events (in ACPI 5).
> > Basically ACPI telling operating system it wants an ACPI event handler run
> > when a certain gpio interrupt is triggered, and the HW reduced ACPI expects the OS gpio driver to do it.
>
> OK, so this is an implicit dependency. If this is the only issue, it
> sounds like the driver can be a module.
>
> > I haven't followed up on this at all. Can't say if we have any HW reduced baytrail variants out there.
> >
> > For Lynxpoint there was also some issue that pnpacpi reserved the IO resources before a modular gpio driver could get it,
> > I think it was fixed, might be that baytrail would face same issue.
>
> Could you give any pointer, if you remember?
Mathias, any progress on this?
Thanks,
--
Jean Delvare
SUSE L3 Support
prev parent reply other threads:[~2016-08-02 8:38 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
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 [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=20160802103801.765b8202@endymion \
--to=jdelvare@suse.de \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mika.westerberg@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 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).