Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "D. Sen" <dsen@homemail.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: intel8x0: changing characteristics after an APM suspend-resume cycle
Date: Fri, 14 Feb 2003 12:35:59 +0100	[thread overview]
Message-ID: <s5h65rnjdr4.wl@alsa2.suse.de> (raw)
In-Reply-To: <3E4B0622.8070500@homemail.com>

At Thu, 13 Feb 2003 13:42:42 +1100,
D. Sen <dsen@homemail.com> wrote:
> 
> Hi Takashi,
> 
> I am wondering if you had a chance to look at the 'resume' procedure. 
> Its really frustrating having to shutdown all the audio applications (I 
> have lots) and restarting them after the resume.

sorry, i haven't changed the code yet since i have no time left for
investigating this problem.

can you do the following small test?

- playback a 44100 (or 48000) hz file
- suspend/resume
- playback the same file again.
- if the playback is too fast, playback a file with different sample
  rate once.
- playback the file above again.


also, please get the dump of /proc/asound/card0/ac97#0regs
before and after suspend/resume (and after playback, too), and compare
whether the values are different.


thanks,

Takashi


-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en

  parent reply	other threads:[~2003-02-14 11:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07 20:40 intel8x0: changing characteristics after an APM suspend-resume cycle D. Sen
2003-01-08 12:03 ` Takashi Iwai
2003-01-08 13:46   ` D. Sen
2003-01-08 16:38     ` Takashi Iwai
2003-02-09  5:38       ` D. Sen
     [not found]       ` <3E4B0622.8070500@homemail.com>
2003-02-14 11:35         ` Takashi Iwai [this message]
2003-01-08 14:25   ` D. Sen

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=s5h65rnjdr4.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=dsen@homemail.com \
    /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