From: Takashi Iwai <tiwai@suse.de>
To: Guilhem Tardy <guilhem_tardy@yahoo.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: pcm_lib.c & pcm_memory.c
Date: Wed, 24 Jul 2002 16:13:56 +0200 [thread overview]
Message-ID: <s5hlm81nrh7.wl@alsa2.suse.de> (raw)
In-Reply-To: <20020724135330.42595.qmail@web11503.mail.yahoo.com>
At Wed, 24 Jul 2002 06:53:30 -0700 (PDT),
Guilhem Tardy wrote:
>
> - Takashi Iwai <tiwai@suse.de> wrote:
> > > Where should captured audio data be copied into runtime->dma_area? Is it up
> > > to the driver or do capture_copy() and capture_silence() functions take the
> > > same role as for playback?
> >
> > yes. if copy and silence callbacks are defined, then it's up to the
> > driver.
>
> OK, then I know how to solve my problem, but it would have been nice to avoid
> copy and silence callbacks, and just get from the substream or runtime
> structure the hw offset where the next period is expected to be written to.
sorry, i don't understand your question.
regardless of the existence of copy callbacks, the hw_ptr is updated
automatically. it has nothing to do with the behavior of copy/silence.
copy and silence callbacks are called to replace on behalf of
copy_from/to_user().
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-07-24 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-22 18:35 pcm_lib.c & pcm_memory.c Guilhem Tardy
2002-07-23 9:32 ` Takashi Iwai
[not found] ` <20020724135330.42595.qmail@web11503.mail.yahoo.com>
2002-07-24 14:13 ` Takashi Iwai [this message]
2002-07-24 14:27 ` Guilhem Tardy
2002-07-25 19:27 ` Guilhem Tardy
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=s5hlm81nrh7.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=guilhem_tardy@yahoo.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 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.