Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Liam Girdwood <lrg@ti.com>
To: "jonsmirl@gmail.com" <jonsmirl@gmail.com>
Cc: alsa-devel mailing list <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: SOC that needs L/R data in separate buffers
Date: Wed, 28 Nov 2012 10:13:50 +0000	[thread overview]
Message-ID: <50B5E3DE.8000109@ti.com> (raw)
In-Reply-To: <CAKON4OzLvNUNsWXoaBMy+BFT-dhv2sAW6ytPXpTWkKEjoS+w0w@mail.gmail.com>

On 28/11/12 04:13, jonsmirl@gmail.com wrote:
> Is there a format in ALSA for hardware that wants the L/R stereo data
> in two different buffers and not inter-leaved? Hardware has two DMA
> channels into separate FIFOs for L/R.
>

asound.h lists all the supported data formats and we have 
SNDRV_PCM_ACCESS_RW_NONINTERLEAVED for non interleaved hardware.

Regards

Liam

      reply	other threads:[~2012-11-28 10:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-28  4:13 SOC that needs L/R data in separate buffers jonsmirl
2012-11-28 10:13 ` Liam Girdwood [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=50B5E3DE.8000109@ti.com \
    --to=lrg@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=jonsmirl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox