From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: No snd_pcm_resume_all() ?
Date: Tue, 18 Apr 2006 12:12:47 +1000 [thread overview]
Message-ID: <1145326367.4705.37.camel@localhost.localdomain> (raw)
In-Reply-To: <1145324168.16138.126.camel@mindpipe>
On Mon, 2006-04-17 at 21:36 -0400, Lee Revell wrote:
> On Tue, 2006-04-18 at 11:27 +1000, Benjamin Herrenschmidt wrote:
> > How are apps supposed to know about system suspend/resume ? There is
> > no proper way to do so that works accross architectures and
> > suspend/resume methods so far ... I yet have to see a single audio app
> > that knows about it ... (tried various KDE based things like Amarok,
> > mpg123, xine, ... )
>
> They don't specifically have to know about suspend and resume - from the
> application point of view it just looks like an underrun - poll() or
> write() will return an error code so the app checks the state with
> snd_pcm_state() and recovers if it is SND_PCM_STATE_XRUN or
> SND_PCM_STATE_SUSPENDED.
>
> Are any of these native ALSA apps, or do they all go through artsd which
> uses the OSS emulation layer?
>
> Does it work OK with aplay?
I'm not sure what they use at this point, I'll check later. I think I
didn't enabled artsd and amarok is using xine engine so it's probably
using alsa directly though.
Ben.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next prev parent reply other threads:[~2006-04-18 2:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 0:58 No snd_pcm_resume_all() ? Benjamin Herrenschmidt
2006-04-18 1:20 ` Lee Revell
2006-04-18 1:27 ` Benjamin Herrenschmidt
2006-04-18 1:36 ` Lee Revell
2006-04-18 1:45 ` Lee Revell
2006-04-18 2:13 ` Benjamin Herrenschmidt
2006-04-18 2:12 ` Benjamin Herrenschmidt [this message]
2006-04-18 13:12 ` Takashi Iwai
2006-04-18 17:55 ` Johannes Berg
2006-04-18 18:05 ` Takashi Iwai
2006-04-18 18:06 ` Johannes Berg
2006-04-18 18:10 ` Takashi Iwai
2006-04-18 18:12 ` Johannes Berg
2006-04-18 18:25 ` Takashi Iwai
2006-04-18 18:40 ` Johannes Berg
2006-04-18 18:54 ` Takashi Iwai
2006-04-18 19:27 ` Jaroslav Kysela
2006-04-18 20:59 ` Benjamin Herrenschmidt
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=1145326367.4705.37.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=alsa-devel@alsa-project.org \
--cc=johannes@sipsolutions.net \
--cc=rlrevell@joe-job.com \
--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.