From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: 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.8.x
Date: Thu, 9 Feb 2017 11:10:26 +0200 [thread overview]
Message-ID: <20170209091026.GV19313@lahna.fi.intel.com> (raw)
In-Reply-To: <CACPiFCJUDRX4nm4aR0SuL-YKY5SE4YMap2RNq7QUKKFo6FAYpg@mail.gmail.com>
On Wed, Feb 08, 2017 at 02:27:58PM -0500, Martin Langhoff wrote:
> Hi Mika,
>
> this is... interesting. I've recompiled Fedora's v4.10-rc7 with
> pinctrl-cherryview=m. Now all it needs to boot is 'noacpi'.
> Blacklisting pinctrl-cherryview makes no difference.
>
> Diffing the config made no sense, as you're using a minimal config and
> I'm using distro config. The diff was awful.
>
> I'll capture dmesg and compare.
>
> Is there anything we can do to make pinctrl-cherryview better behaved
> when built in? I mainly want this laptop to work well with the distro
> kernel :-)
Hey, please don't blame pinctrl-cherryview until you actually know that
it causes the problem.
Also adding random parameters like "noacpi" to the command line is not
going to help at all in debugging this. So please do not alter the
command line. It only makes things worse.
Now, please send me your distro config (privately) and I'll try that
here if I can reproduce the problem.
prev parent reply other threads:[~2017-02-09 9:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 14:37 Diagnosing ACPI trouble related to pinctr_cherryview on 4.8.x Martin Langhoff
2017-02-07 14:52 ` Mika Westerberg
2017-02-07 15:13 ` Martin Langhoff
2017-02-07 15:29 ` Martin Langhoff
2017-02-07 15:48 ` Mika Westerberg
2017-02-07 16:11 ` Martin Langhoff
2017-02-07 16:30 ` Mika Westerberg
2017-02-08 19:27 ` Martin Langhoff
2017-02-09 9:10 ` Mika Westerberg [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=20170209091026.GV19313@lahna.fi.intel.com \
--to=mika.westerberg@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 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).