public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fedor Karpelevitch <fedor@karpelevitch.net>
To: linux-kernel@vger.kernel.org
Cc: matt_wu@acersoftech.com.cn
Subject: [BUG] ali5451 not resumed properly under 2.6.7 ( fine under 2.6.6 )
Date: Wed, 23 Jun 2004 10:04:17 -0700	[thread overview]
Message-ID: <200406231004.27689.fedor@karpelevitch.net> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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?

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


here is that part of the diff:



+static int ali_suspend(snd_card_t *card, unsigned int state)
 {
+       ali_t *chip = snd_magic_cast(ali_t, card->pm_private_data, 
return -EINVAL);
        ali_image_t *im;
        int i, j;
 
        im = chip->image;
        if (! im)
- -               return;
+               return 0;
+
+       snd_pcm_suspend_all(chip->pcm);
+       snd_ac97_suspend(chip->ac97);
 
        spin_lock_irq(&chip->reg_lock);
        
@@ -1940,16 +1943,18 @@
        outl(0xffffffff, ALI_REG(chip, ALI_STOP));
 
        spin_unlock_irq(&chip->reg_lock);
+       return 0;
 }
 
- -static void ali_resume(ali_t *chip)
+static int ali_resume(snd_card_t *card, unsigned int state)
 {
+       ali_t *chip = snd_magic_cast(ali_t, card->pm_private_data, 
return -EINVAL);
        ali_image_t *im;
        int i, j;
 
        im = chip->image;
        if (! im)
- -               return;
+               return 0;
 
        pci_enable_device(chip->pci);
 
@@ -1967,27 +1972,15 @@
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA2bgYw4m50RG4juoRAqTqAJ4+oHXRvOjz6NZLUS82oxIh+d7SIACgl65l
hCtld2qftBglwS0V0gYNHAw=
=ZLy7
-----END PGP SIGNATURE-----

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23 17:04 Fedor Karpelevitch [this message]
2004-06-24  9:23 ` [BUG] ali5451 not resumed properly under 2.6.7 ( fine under 2.6.6 ) Takashi Iwai
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=200406231004.27689.fedor@karpelevitch.net \
    --to=fedor@karpelevitch.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt_wu@acersoftech.com.cn \
    /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