From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
David Henningsson <david.henningsson@canonical.com>
Subject: Re: About 'SNDRV_PCM_CLASS_MULTI' for devices with multi-channels
Date: Thu, 20 Feb 2014 23:25:31 +0900 [thread overview]
Message-ID: <5306105B.9020905@sakamocchi.jp> (raw)
In-Reply-To: <s5h38jexldh.wl%tiwai@suse.de>
> Right. And the likely reason is that such a differentiation doesn't
> help much.
I thought usage of this macro can tell applications that the PCM
channels are not for surround sound.
But for this purpose, card configuration is better. Applications can get
to know by seeking 'surround' PCM devices such like 'surround51'.
> You can still use your device for driving 5.1 surround :)
It's not my intention. I'm considering about the way to prevent
applications from using the devices for surround sound.
I don't prepare for card configuration. So devices which my drivers
support have no 'surround' PCM devices.
> So, I rather would like to keep them RIP. Maybe worth to remove it
> now.
Yes.
In the same reason, 'SND_PCM_SUBCLASS_MULTI_MIX' should be removed. As a
result, 'SND_PCM_SUBCLASS_XXX', 'struct snd_pcm_info.dev_subclass' are
also needless...
Thanks
Takashi Sakamoto
o-takashi@sakamocchi.jp
next prev parent reply other threads:[~2014-02-20 14:25 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 ` About 'SNDRV_PCM_CLASS_MULTI' for devices with multi-channels David Henningsson
2014-02-20 2:28 ` Takashi Sakamoto
2014-02-20 8:02 ` Takashi Iwai
2014-02-20 14:25 ` Takashi Sakamoto [this message]
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=5306105B.9020905@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--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