From: Johannes Weiner <hannes@saeurebad.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: Mathieu Chouquet-Stringer <mchouque@free.fr>,
Jaroslav Kysela <perex@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: Longstanding bug in ac97/intel8x0 resume/init
Date: Tue, 01 Jul 2008 17:12:02 +0200 [thread overview]
Message-ID: <87fxqt4p19.fsf@skyscraper.fehenstaub.lan> (raw)
In-Reply-To: <s5h1w2dek7p.wl%tiwai@suse.de> (Takashi Iwai's message of "Tue, 01 Jul 2008 16:46:02 +0200")
Hi,
Takashi Iwai <tiwai@suse.de> writes:
> At Tue, 01 Jul 2008 16:37:42 +0200,
> Johannes Weiner wrote:
>>
>> Hi,
>>
>> Takashi Iwai <tiwai@suse.de> writes:
>>
>> > At 30 Jun 2008 20:58:03 +0200,
>> > Mathieu Chouquet-Stringer wrote:
>> >>
>> >> Hey there,
>> >>
>> >> hannes@saeurebad.de (Johannes Weiner) writes:
>> >> > Johannes Weiner <hannes@saeurebad.de> writes:
>> >> > > my laptop has muted sound after resuming the soundcard (by
>> >> > > s2ram/hibernation). The problem seems to be that the cached register
>> >> > > values are not written back to the device properly.
>> >>
>> >> I've got the same exact issue on a Thinkpad T30:
>> >>
>> >> 0 [I82801CAICH3 ]: ICH - Intel 82801CA-ICH3
>> >> Intel 82801CA-ICH3 with AD1881A at irq 5
>> >>
>> >> 00:1f.5 Multimedia audio controller: Intel Corporation 82801CA/CAM AC'97 Audio Controller (rev 02)
>> >
>> > Does this happen for both hibernation and S2RAM?
>> > And, resetting the mixer repairs the mute state, right?
>> > If yes, the problem appears independently from the codec chip. Hmm...
>>
>> Yes, happens in both cases here.
>>
>> The alsamixer shows the state of the channels before the suspension(!).
>
> Yes. The driver returns the cached values.
Okay.
>> If I change the channel state, the sound works again. No complete reset
>> needed at all, I just have to increase/decrease the value a bit (for
>> each affected channel).
>
> Just touching one mixer element?
What means `element' here? I have to touch MASTER and PCM in order to
get some output again, at least ;)
>> >From my experiments with the code, I figured that the cached register
>> values are not written back properly on resume. The cache is in the
>> correct state but the hardware is not. This also explains the behaviour
>> when changing the channels with alsamixer; the register cache is touched
>> and written back (and this time, the value really gets through to the
>> hardware).
>
> Right.
>
> snd_ac97_resume() has a check whether the write to MASTER register
> succeeds, but its timeout is 100ms. Could you check whether this
> check passes at resume or failed? I remember that some device
> actually passed the test but didn't update the real hardware state.
> If it failed on yours, we may simply extend the timeout, or make it
> pending somehow. If the hardware fools us, however, it'd be toucher.
By experimentation I found that the writeback works with a two seconds
delay before writeback. I can't remember if it was before or after the
check. Another approach was to hammer down the value by writing and
reading back in a loop until the hardware responded with the correct
value.
I will redo the tests later and report back to you what helped.
Hannes
next prev parent reply other threads:[~2008-07-01 15:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 23:31 Longstanding bug in ac97/intel8x0 resume/init Johannes Weiner
2008-06-29 10:35 ` Johannes Weiner
2008-06-30 18:58 ` Mathieu Chouquet-Stringer
2008-07-01 13:43 ` Takashi Iwai
2008-07-01 14:37 ` Johannes Weiner
2008-07-01 14:46 ` Takashi Iwai
2008-07-01 15:12 ` Johannes Weiner [this message]
2008-07-01 15:16 ` Takashi Iwai
2008-07-06 23:17 ` Johannes Weiner
2008-07-09 18:39 ` Takashi Iwai
2008-07-01 13:42 ` Takashi Iwai
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=87fxqt4p19.fsf@skyscraper.fehenstaub.lan \
--to=hannes@saeurebad.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mchouque@free.fr \
--cc=perex@suse.cz \
--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.