Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Ian McKellar <yakk@yakk.net>, perex@suse.cz, alsa-devel@alsa-project.org
Subject: Re: Sleep fix for iBook 800 sound
Date: Wed, 07 Apr 2004 11:35:55 +0200	[thread overview]
Message-ID: <s5hsmfg9ll0.wl@alsa2.suse.de> (raw)
In-Reply-To: <1081319710.1401.46.camel@gaston>

Hi,

At Wed, 07 Apr 2004 16:35:11 +1000,
Benjamin Herrenschmidt wrote:
> 
> On Wed, 2004-04-07 at 16:25, Ian McKellar wrote:
> > So, 
> > 
> > I have an iBook 800Mhz and since I've moved to alsa and linux 2.6 I've
> > had issues with sound oopsing in sleep, kind of like this:
> 
> Is sound working at all ? I suspect you didn't have the i2c-keywest
> module insmod'ed. There is indeed a problem in all our i2c based
> sound drivers where we don't always check that the i2c client was
> instanciated before doing some things...
> 
> Takashi, how is this patch ?

yes, the patch is fine, but i guess it won't fix Ian's mixer problem
after resume.  the real problem is that i2c.client is reset to NULL in
sleep_notify callback.

i just took a quick look at dmasound code again, but the code path
looks almost same, i.e.

	sleep_notify_callback(PBOOK_WAKE)
	-> leave_sleep callback
	-> resume mixer values

maybe dmasound resumes the mixer setting in somewhere else, too?


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

           reply	other threads:[~2004-04-07  9:39 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1081319710.1401.46.camel@gaston>]

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=s5hsmfg9ll0.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=benh@kernel.crashing.org \
    --cc=perex@suse.cz \
    --cc=yakk@yakk.net \
    /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