From: Takashi Iwai <tiwai@suse.de>
To: Frans Pop <elendil@planet.nl>
Cc: linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [regression] Sound not transferred to docking station after resume from StR
Date: Mon, 19 Apr 2010 13:59:36 +0200 [thread overview]
Message-ID: <s5h8w8jps9j.wl%tiwai@suse.de> (raw)
In-Reply-To: <201004191338.15750.elendil@planet.nl>
At Mon, 19 Apr 2010 13:38:14 +0200,
Frans Pop wrote:
>
> On Monday 19 April 2010, Takashi Iwai wrote:
> > Could you give alsa-info.sh on your machine, preferably before/after
> > suspend on both working (2.6.33) and non-working kernels?
>
> See files in attached tarball. Contents are:
> * system boot (docked)
> => alsa-info.txt_3[34]_docked
> * undock
> => alsa-info.txt_3[34]_undocked
> * suspend - dock (while suspended) - resume
> => alsa-info.txt_3[34]_after_resume_docked
> * undock - redock (this disables the internal speakers)
> => alsa-info.txt_34_after_resume_redocked
>
> > Also, you can try to copy sound/pci/hda/patch_analog.c from 2.6.33 to
> > 2.6.34 to check whether it works. There shouldn't be many changes in
> > that file.
>
> That fixes the problem.
Then my rough guess is
commit ea52bf260ecbb175339af3178c15788df21b7516
Author: Daniel T Chen <crimsun@ubuntu.com>
Date: Sun Dec 27 18:48:29 2009 -0500
ALSA: hda: Add powerdown for Analog Devices HDA codecs
Could you try to revert it?
thanks,
Takashi
next prev parent reply other threads:[~2010-04-19 11:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 19:31 [regression] Sound not transferred to docking station after resume from StR Frans Pop
2010-04-16 19:48 ` Frans Pop
2010-04-17 9:06 ` Frans Pop
2010-04-19 7:47 ` Takashi Iwai
2010-04-19 11:38 ` Frans Pop
2010-04-19 11:59 ` Takashi Iwai [this message]
2010-04-19 12:14 ` Takashi Iwai
2010-04-19 12:39 ` Frans Pop
2010-04-19 12:53 ` Takashi Iwai
2010-04-19 14:58 ` Frans Pop
2010-04-19 16:17 ` Takashi Iwai
2010-04-19 12:18 ` Frans Pop
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=s5h8w8jps9j.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
/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