From: Clemens Ladisch <clemens@ladisch.de>
To: Prasant J <pj0585@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Non-Interleaved access method?
Date: Thu, 18 Oct 2012 16:34:06 +0200 [thread overview]
Message-ID: <5080135E.4020600@ladisch.de> (raw)
In-Reply-To: <CAA2DH4uV6qzzJzpbZx6-MXnH4SBD11uqDkaxHnOTesvCXabM4A@mail.gmail.com>
Prasant J wrote:
> When the application set the access method to non-interleaved, that
> means that the ALSA application will deliver the non-interleaved
> buffers to alsa subsystem & the alsa subsystem will interleave the
> data before sending out the data to the hardware.
Yes.
> Or non-interleaved means that the data will be sent out in
> non-interleaved manner itself?
Only if the hardware supports it. (Very few chips do.)
Regards,
Clemens
prev parent reply other threads:[~2012-10-18 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 12:16 Non-Interleaved access method? Prasant J
2012-10-18 14:34 ` Clemens Ladisch [this message]
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=5080135E.4020600@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=pj0585@gmail.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.