All of lore.kernel.org
 help / color / mirror / Atom feed
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,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: Diagnosing ACPI trouble related to pinctr_cherryview on 4.4.x
Date: Tue, 22 Mar 2016 17:22:18 +0200	[thread overview]
Message-ID: <20160322152218.GA2099@lahna.fi.intel.com> (raw)
In-Reply-To: <CACPiFCKv=QJ0t5e=9Wm4cC4Spynx-tVCiabL7AcbcOkp_w47fQ@mail.gmail.com>

On Tue, Mar 22, 2016 at 11:09:51AM -0400, Martin Langhoff wrote:
>    Hi pinctrl_cherryview maintainers.
>    I unsuspectingly bought a laptop for a family member which hits trouble
>    with pinctrl_cherryview; it only boots with the module blacklisted or
>    acpi=off .
>    System is (trying) to run Fedora 23 -- made more difficult by recent
>    Fedora kernels having the module built-in.
>    Are there any useful debugging steps I can follow to narrow this down?
>    Already tried the acpi diagnostics steps (acpi=ht, etc) to no avail.
>    thank you!

I think this is a known issue.

Please disable dw_dmac from your .config (or blacklist the module):

  CONFIG_DW_DMAC_CORE=n
  CONFIG_DW_DMAC=n

You can also enable pinctrl-cherryview.c.

Andy (Cc'd) is working a fix for this DMA hang issue.

       reply	other threads:[~2016-03-22 15:22 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 ` Mika Westerberg [this message]
2016-03-22 15:41   ` Diagnosing ACPI trouble related to pinctr_cherryview on 4.4.x 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
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=20160322152218.GA2099@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.