All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Schuring <aelschuring@hotmail.com>
To: alsa-devel@alsa-project.org
Subject: RFC: ice1712 virtual devices
Date: Thu, 29 Oct 2009 18:48:46 +0100	[thread overview]
Message-ID: <4AE9D57E.5090105@hotmail.com> (raw)

Hello list,

This is basically a resend of
http://thread.gmane.org/gmane.linux.alsa.devel/59481/focus=59672 , which
 fixed the front: device of ice1712 cards to accept two-channel input.
Currently, the front: device is exposed through the route plugin, which
requires all clients to mmap all 10 channels, even though the front
device is supposed to be a stereo device.

This patch changes the front: device definition such that it matches the
definition of iec958 in the same file. Additionally, I'm tempted to
remove the surround* definitions because the chip does not really offer
surround-style multichannel: it basically just offers multiple stereo
channels, and does not provide any channel mapping beyond stereo.

Finally, I'm also experimenting with the dshare plugin to allow
applications to access the iec958: and front: devices simultaneously.
Can anyone point me to a working example for this? From reading the
alsa-lib documentation, it is not clear to me how I should nest the
different plugins.


Many thanks,
Arno Schuring


--

diff --git a/src/conf/cards/ICE1712.conf b/src/conf/cards/ICE1712.conf
index 01e50d2..d7acb81 100644
--- a/src/conf/cards/ICE1712.conf
+++ b/src/conf/cards/ICE1712.conf
@@ -32,12 +32,28 @@ ICE1712.pcm.front.0 {
        @args.CARD {
                type string
        }
-       type route
-       ttable.0.0 1
-       ttable.1.1 1
-       slave.pcm {
-               type hw
-               card $CARD
+       type asym
+       playback.pcm {
+               type route
+               ttable.0.0 1
+               ttable.1.1 1
+               slave.pcm {
+                       type hw
+                       card $CARD
+               }
+               slave.format S32_LE
+               slave.channels 10
+       }
+       capture.pcm {
+               type route
+               ttable.0.0 1
+               ttable.1.1 1
+               slave.pcm {
+                       type hw
+                       card $CARD
+               }
+               slave.format S32_LE
+               slave.channels 12
        }
 }

             reply	other threads:[~2009-10-29 17:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-29 17:48 Arno Schuring [this message]
2009-10-30  0:36 ` RFC: ice1712 virtual devices Raymond Yau
2009-10-30  9:23 ` Alan Horstmann
2009-10-30 11:29   ` Arno Schuring
2009-11-08 10:38   ` Takashi Iwai
2009-11-08 21:13     ` Alan Horstmann
2009-11-16 19:32       ` Arno Schuring
2009-11-21  2:53         ` Raymond Yau

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=4AE9D57E.5090105@hotmail.com \
    --to=aelschuring@hotmail.com \
    --cc=alsa-devel@alsa-project.org \
    /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.