From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org
Subject: Re: Diagnosing ACPI trouble related to pinctr_cherryview on 4.4.x
Date: Wed, 23 Mar 2016 13:25:32 +0200 [thread overview]
Message-ID: <20160323112532.GK2099@lahna.fi.intel.com> (raw)
In-Reply-To: <CACPiFC+_TpiFFm+hYJd1tX4AnadxSj_KKOtDALjSj0_c8Qa2pA@mail.gmail.com>
On Tue, Mar 22, 2016 at 01:53:13PM -0400, Martin Langhoff wrote:
> On Tue, Mar 22, 2016 at 1:36 PM, Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
> > # CONFIG_X86_INTEL_LPSS is not set
>
> adding intel_lpss,intel_lpss_acpi,intel_lpss_pci to blacklisted
> modules in kernel command line did not change things for the better.
intel_lpss_* is actually different thing than setting
CONFIG_X86_INTEL_LPSS=n
which I suggest you try as well (you can't blacklist that).
next prev parent reply other threads:[~2016-03-23 11:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACPiFCKv=QJ0t5e=9Wm4cC4Spynx-tVCiabL7AcbcOkp_w47fQ@mail.gmail.com>
2016-03-22 15:22 ` Diagnosing ACPI trouble related to pinctr_cherryview on 4.4.x Mika Westerberg
2016-03-22 15:41 ` Martin Langhoff
2016-03-22 15:49 ` Mika Westerberg
2016-03-22 15:51 ` Mika Westerberg
2016-03-22 15:59 ` Martin Langhoff
2016-03-22 16:22 ` Mika Westerberg
2016-03-22 16:59 ` Martin Langhoff
2016-03-22 17:36 ` Andy Shevchenko
2016-03-22 17:53 ` Martin Langhoff
2016-03-22 20:32 ` Martin Langhoff
2016-03-23 11:13 ` Mika Westerberg
2016-03-23 13:25 ` Martin Langhoff
2016-03-23 11:25 ` Mika Westerberg [this message]
2016-03-23 13:26 ` Martin Langhoff
2016-03-28 20:57 ` Martin Langhoff
2016-03-29 9:15 ` Mika Westerberg
2016-03-31 9:24 ` Mika Westerberg
2016-03-30 10:33 ` Andy Shevchenko
2016-03-22 15:58 ` Andy Shevchenko
2016-03-22 15:18 Martin Langhoff
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=20160323112532.GK2099@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=martin.langhoff@gmail.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 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.