From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: alsa-devel@alsa-project.org
Subject: need help for PCM constraint/rules
Date: Sun, 24 Mar 2013 22:58:46 +0900 [thread overview]
Message-ID: <514F0696.1030109@sakamocchi.jp> (raw)
Dear developers,
I'm a newbile for this project and working for kernel land driver for
Fireworks with ALSA framework.
I need your help for constraint/rule of PCM component.
Related source is:
https://github.com/takaswie/snd-firewire-improve/blob/master/fireworks/fireworks_pcm.c
My device (AudioFirePre8) changes its channels according to sampling
rate. For example:
32.0 - 48.0kHz : 16ch: efw->channels_sets[0]
88.2 - 96.0kHz : 12ch: efw->channels_sets[1]
176.4 - 192.0kHz : 10ch: efw->channels_sets[2] (but not available)
The other devices such as AudioFire12 has the same number of channels
(12ch)in each sampling rate.
I managed to write this rule refering to rme9652.c but I cannot achieve
my purpose. It's my glad to get some help about this.
Regards
Takashi Sakamoto
o-takashi@sakamocchi.jp
========
Fireworks is Echo Audio's series of Firewire Audio interface.
http://echoaudio.com/products/audiofire-pre8
It utilizes IEC 61883-1 and -6 in its implementation and familiar with
current snd-firewire-lib.ko.
FFADO also produce driver for it. It's a user-land implementation.
http://www.ffado.org/
My aim is writing kernel-land driver for it with ALSA framework.
Takashi Sakamoto
o-takashi@sakamocchi.jp
next reply other threads:[~2013-03-24 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 13:58 Takashi Sakamoto [this message]
2013-03-24 19:12 ` need help for PCM constraint/rules Clemens Ladisch
2013-03-26 16:58 ` Takashi Sakamoto
2013-03-26 18:24 ` Clemens Ladisch
2013-03-27 12:11 ` 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=514F0696.1030109@sakamocchi.jp \
--to=o-takashi@sakamocchi.jp \
--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.