public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: alsa-devel@alsa-project.org
Cc: Russell King <linux@arm.linux.org.uk>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.de>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [RFC] sound: ASoC: multiple DAIs/codecs on single audio stream
Date: Tue, 16 Apr 2013 19:45:08 +0200	[thread overview]
Message-ID: <516D8E24.9020308@gmail.com> (raw)

Hi,

I am rewriting Marvell Kirkwood/Dove audio driver and I am having
a hard time to match the controllers features to ASoC API.

The controller has a dma controller for one playback buffer. It can
play the stream to both I2S and SPDIF interfaces with independent mute.

Now, for example, I have a board with i2s codec and spdif tx diode
connected to the above controller:

DMA (platform) -+-> I2S (dai) ----> I2S_Codec (codec)
                 |
                 +-> SPDIF (dai) --> SPDIF_TX (codec)

Is there any way in the current ASoC API to have the above setup?

I tried to attach two codecs to a single DAI and that will already
create two playback streams with two buffers. I guess it will also
happen if I have two DAIs connected to the same platform driver?

For an API for SoC audio, shouldn't there be some relation between
platform, DAI, and codec, e.g.:
- a platform represents a single audio stream buffer
- a platform can be attached to one or more DAIs,
- a DAI can be attached to one codec only

Regards,
   Sebastian

             reply	other threads:[~2013-04-16 17:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16 17:45 Sebastian Hesselbarth [this message]
2013-04-17 14:13 ` [RFC] sound: ASoC: multiple DAIs/codecs on single audio stream Mark Brown

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=516D8E24.9020308@gmail.com \
    --to=sebastian.hesselbarth@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=perex@perex.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox