public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [BUG] ali5451 not resumed properly under 2.6.7 ( fine under 2.6.6 )
Date: Thu, 24 Jun 2004 11:23:33 +0200	[thread overview]
Message-ID: <s5hisdhia22.wl@alsa2.suse.de> (raw)
In-Reply-To: <200406231004.27689.fedor@karpelevitch.net>

At Wed, 23 Jun 2004 10:04:17 -0700,
Fedor Karpelevitch wrote:
> 
> Hi,
> 
> I upgraded to 2.6.7 recently and noticed that my ali5451 souncard 
> stopped behaving properly after resuming. 
> 
> Basically after resume it produces no sound even though everything 
> pretends that the card is working properly (mixer "changes" volume 
> etc...). 
> I found that executing something like 'alsactl -F power A5451 D1' 
> makes it produce sound again although the volume is noticably lower 
> than it should be.
> 
> 2.6.6 works just fine.
> 
> I looked at the diff for ali5451.c and noticed that in ali_suspend a 
> call to snd_pcm_suspend_all(chip->pcm) was added, but in ali_resume 
> no call to resume pcm was added. Could that be the cause of the 
> problem?

No, the resume is done either in pcm_oss.c or by calling the resume
ioctl explicitly from ALSA-native apps later on.

> I will try adding that call and see if that fixes the problem.

There is no function such as snd_pcm_resume_pcm().

Maybe you can remove the calls of snd_pcm_suspend_all(),
snd_ac97_suspend() in suspend callback, and snd_ac97_resume() in
resume callback.


--
Takashi Iwai <tiwai@suse.de>		ALSA Developer - www.alsa-project.org

  reply	other threads:[~2004-06-24  9:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23 17:04 [BUG] ali5451 not resumed properly under 2.6.7 ( fine under 2.6.6 ) Fedor Karpelevitch
2004-06-24  9:23 ` Takashi Iwai [this message]
2004-06-24 20:34   ` Fedor Karpelevitch

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=s5hisdhia22.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=linux-kernel@vger.kernel.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