linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacob Pan <jacob.jun.pan@linux.intel.com>
To: Vincent Gerris <vgerris@gmail.com>
Cc: Len Brown <lenb@kernel.org>, Hans de Goede <hdegoede@redhat.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Jochen Hein <jochen@jochen.org>,
	Linux PM <linux-pm@vger.kernel.org>,
	jacob.jun.pan@linux.intel.com
Subject: Re: [PATCH] intel_idle: work around errate VLP52 on Baytrail CPUs
Date: Wed, 28 Dec 2016 10:47:05 -0800	[thread overview]
Message-ID: <20161228104705.57b101d3@jacob-builder> (raw)
In-Reply-To: <CA+8K-gntePuqdij7SijqcT0RXPoKi163UPwoBnBCk04zBp0BvA@mail.gmail.com>

On Wed, 28 Dec 2016 13:56:25 +0100
Vincent Gerris <vgerris@gmail.com> wrote:

> > >> If the right strategy were to disable C6 for all of BYT, then the
> > >> right implementation
> > >> would be to delete those states from byt_cstates[], rather than
> > >> for a routine to mark
> > >> them as disabled.  Note that a user can not later enable a state
> > >> that is marked as disabled here, it is never registered with
> > >> cpuidle, and thus the effect is exactly the same as if the entry
> > >> were never in the table in the first place.  
> I don't fully grasp this, but if the errata causes this, wouldn't it
> be more transparent to mark it as such so disable it?
> Are we really sure the errata does not cause this? If so, is there a
> recommended way from intel on how to patch this?
I don't think the EOI errata is relevant to this issue. As Len pointed
out, it is impossible to enter C6 or run idle task during ISR.

However, this errata might be the cause of the issue you seen, as you
mentioned you encounter the issue while playing media with audio i
presume? While I am looking for a fix, could you try without audio see
if it still hangs?

"VLP70. LPE Audio Playback May Result in System Hang
Problem: Extended audio playback with the LPE (Low Power Engine) may
result in a system hang if the SOC concurrently enters C6 or deeper
sleep states. Implication: The system may hang when this erratum occurs.
Workaround: It is possible for the driver to contain a workaround for
this erratum."

  reply	other threads:[~2016-12-28 18:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-19 18:19 [PATCH] intel_idle: work around errate VLP52 on Baytrail CPUs Jochen Hein
2016-12-19 19:43 ` Rafael J. Wysocki
     [not found]   ` <CA+8K-g=fXN9TWWxkV1AEEjXJLhwJEQ2PB434gKQ9Z7bL=yf+zA@mail.gmail.com>
2016-12-27 17:24     ` Vincent Gerris
2016-12-27 20:37       ` Len Brown
2016-12-27 20:44         ` Jochen Hein
2016-12-27 21:27           ` Len Brown
2016-12-28 12:56             ` Vincent Gerris
2016-12-28 18:47               ` Jacob Pan [this message]
2017-01-11 23:14               ` Len Brown
2017-01-11 23:22                 ` Jacob Pan

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=20161228104705.57b101d3@jacob-builder \
    --to=jacob.jun.pan@linux.intel.com \
    --cc=hdegoede@redhat.com \
    --cc=jochen@jochen.org \
    --cc=lenb@kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=vgerris@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).