From: David Henningsson <david.henningsson@canonical.com>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>, alsa-devel@alsa-project.org
Subject: Re: About 'SNDRV_PCM_CLASS_MULTI' for devices with multi-channels
Date: Wed, 19 Feb 2014 20:40:43 +0100 [thread overview]
Message-ID: <530508BB.6060802@canonical.com> (raw)
In-Reply-To: <5304C64D.3090400@sakamocchi.jp>
On 02/19/2014 03:57 PM, Takashi Sakamoto wrote:
> Hi all,
>
> I have two questions about the usage of this macro.
>
> Should I use this macro for new drivers which I'm working for?'
> http://mailman.alsa-project.org/pipermail/alsa-devel/2014-January/071820.html
>
>
> My drivers support some firewire devices, which is desinged for
> studio-use and have many channels. Its combination of channels are not
> designed for surround sound like 5.1ch.
>
> Just judging from its name, 'SNDRV_PCM_CLASS_MULTI', I should use this.
> But there are no drivers which use this macro in current tree, against
> my expectation that some drivers (ICE1712-pro, RME9652, 6fire usb and so
> on) should use this macro.
>
> Are there any reasons?
I've never heard of it before. I had a quick look in alsa-lib and
couldn't find any difference in handling between CLASS_GENERIC and
CLASS_MULTI.
It's probably something historic that nobody uses any more. Maybe people
who have been along longer knows what it is.
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
next parent reply other threads:[~2014-02-19 19:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5304C64D.3090400@sakamocchi.jp>
2014-02-19 19:40 ` David Henningsson [this message]
2014-02-20 2:28 ` About 'SNDRV_PCM_CLASS_MULTI' for devices with multi-channels Takashi Sakamoto
2014-02-20 8:02 ` Takashi Iwai
2014-02-20 14:25 ` Takashi Sakamoto
2014-02-19 17:17 Takashi Sakamoto
-- strict thread matches above, loose matches on Subject: below --
2014-02-19 16:59 Takashi Sakamoto
2014-02-19 16:41 Takashi Sakamoto
2014-02-19 16:21 Takashi Sakamoto
2014-02-19 15:31 Takashi Sakamoto
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=530508BB.6060802@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=o-takashi@sakamocchi.jp \
/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.