All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Yang, Libin" <libin.yang@intel.com>,
	"hui.wang@canonical.com" <hui.wang@canonical.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"Lu, Han" <han.lu@intel.com>,
	"Lin, Mengdong" <mengdong.lin@intel.com>
Subject: Re: [PATCH v2] ALSA: hda - Fix Skylake codec timeout
Date: Thu, 16 Jul 2015 17:37:41 +0200	[thread overview]
Message-ID: <55A7CFC5.8040707@canonical.com> (raw)
In-Reply-To: <s5hvbdki0aa.wl-tiwai@suse.de>



On 2015-07-16 17:34, Takashi Iwai wrote:
> On Thu, 16 Jul 2015 17:31:33 +0200,
> David Henningsson wrote:
>>
>>
>>
>> On 2015-07-16 17:14, Yang, Libin wrote:
>>>> -----Original Message-----
>>>> From: David Henningsson [mailto:david.henningsson@canonical.com]
>>>> Sent: Thursday, July 16, 2015 4:39 PM
>>>> To: tiwai@suse.de; hui.wang@canonical.com; alsa-devel@alsa-
>>>> project.org; Yang, Libin; Lin, Mengdong
>>>> Cc: David Henningsson
>>>> Subject: [PATCH v2] ALSA: hda - Fix Skylake codec timeout
>>>>
>>>> When the controller is powered up but the HDMI codec is powered
>>>> down
>>>> on Skylake, the power well is turned off. When the codec is then
>>>> powered up again, we need to poke the codec a little extra to make
>>>> sure it wakes up. Otherwise we'll get sad "no response from codec"
>>>> messages and broken audio.
>>>
>>> Thanks for finding this issue.
>>>
>>> Could you please give us you test case? We didn't meet such issue
>>> before. I would like do a full test on it.
>>
>> The test case is:
>>
>>    - Install Ubuntu 15.04.
>>    - Upgrade to kernel 4.1.
>>    - Boot the new kernel.
>>
>> Note: I believe Hui tested with 4.1 and got this error. In my case I
>> have been running a hybrid kernel: Ubuntu 15.04, kernel 3.19.0-23.24
>> (which has a backported i915 driver), and then the alsa-daily DKMS on
>> top of that.
>>
>> I can email you off-list with details about the machine I tested it on,
>> if you like.
>
> Did you hotplug the device or is it booted while plugged?
> I had an unstable communication at hotplug / unplug on SKL at the last
> time, too.  But the boot with the DP plugged worked well even on an
> old SKL box.

For this bug, there was no HDMI monitor connected at all, but I believe 
it does not matter. On power up, the power well is enabled and then 
disabled. When the power well is enabled again without this extra wakeup 
poke (probably due to PulseAudio probing), this error happens.

-- 
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic

  reply	other threads:[~2015-07-16 15:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16  8:39 [PATCH v2] ALSA: hda - Fix Skylake codec timeout David Henningsson
2015-07-16 15:14 ` Yang, Libin
2015-07-16 15:31   ` David Henningsson
2015-07-16 15:34     ` Takashi Iwai
2015-07-16 15:37       ` David Henningsson [this message]
2015-07-16 15:53         ` Takashi Iwai
2015-07-17  2:28           ` Yang, Libin
2015-07-17 13:01             ` Takashi Iwai
2015-07-20  7:14               ` Yang, Libin
2015-07-20  7:34                 ` Takashi Iwai
2015-07-17  0:57     ` Hui Wang

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=55A7CFC5.8040707@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=han.lu@intel.com \
    --cc=hui.wang@canonical.com \
    --cc=libin.yang@intel.com \
    --cc=mengdong.lin@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 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.