All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Julien Bramary <julien.bramary@blueyonder.co.uk>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Trigger Callback
Date: Tue, 01 Aug 2006 15:55:19 -0400	[thread overview]
Message-ID: <1154462119.14540.73.camel@mindpipe> (raw)
In-Reply-To: <44CFB014.2050704@blueyonder.co.uk>

On Tue, 2006-08-01 at 20:48 +0100, Julien Bramary wrote:
> I'm an Alsa beginner and I'm trying to write an alsa driver for an embedded dac on ARM.
> 
> >From Iwai's doc:
> 
> /* trigger callback */
> static int snd_mychip_pcm_trigger(struct snd_pcm_substream *substream, int cmd)
> {
>     switch (cmd) {
>     case SNDRV_PCM_TRIGGER_START:
>             // do something to start the PCM engine
>             break;
>     case SNDRV_PCM_TRIGGER_STOP:
>             // do something to stop the PCM engine
>             break;
>     default:
>             return -EINVAL;
>     }
> }
> 
> My question here is,
> What are we supposed to do to start the PCM engine?
> Because, I'm currently doing nothing, and yet it starts anyway...
> I'd like to understand to have more control.

"PCM engine" refers to the hardware's PCM engine, not ALSA's.  It's 100%
device dependent - you need to consult the docs for your sound device to
determine how to start the PCM.

Lee


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2006-08-01 19:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-01 19:48 Trigger Callback Julien Bramary
2006-08-01 19:55 ` Lee Revell [this message]
2006-08-01 20:14   ` Julien Bramary
2006-08-02 11:29     ` Takashi Iwai
2006-08-02 12:16       ` Julien Bramary

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=1154462119.14540.73.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=julien.bramary@blueyonder.co.uk \
    /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.