From: Takashi Iwai <tiwai@suse.de>
To: tomasz motylewski <T.Motylewski@bfad.de>
Cc: twoller@crystal.cirrus.com, pcaudio@crystal.cirrus.com,
alsa-devel@lists.sourceforge.net, peter wachtendorf <pew@bfad.de>,
arip@bfad.de
Subject: Re: Linux driver for cs4281 with TWO cs4299 codecs?
Date: Mon, 27 May 2002 18:49:50 +0200 [thread overview]
Message-ID: <s5hhektedsh.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0205271816120.8370-100000@mailserver.intern.bfad.de>
At Mon, 27 May 2002 18:37:09 +0200 (CEST),
tomasz motylewski wrote:
>
> Now I have got all alsa9 utilites on the system and the driver does something.
>
> I can see for example PCM (2 channels) and PCM 1 (2 channels) in alsamixer.
>
> I can also record like: arecord -c 4 -t raw -f S16_LE aaa.raw
> and I get:
> od -i aaa.raw | more
> 0000000 -10 -6 0 0 1 3 0 0
> 0000020 -8 -8 0 0 -7 -7 0 0
> 0000040 -7 -6 0 0 -6 -2 0 0
> 0000060 -10 -9 0 0 -9 -8 0 0
>
> But here is a problem - I would expect to see some noise in both codecs - I
> have configured and unmuted them BOTH to max volume.
>
> In fact I have tried also -c 3 and -c 5 and always only the first 2 channels
> are non-zero.
>
> arecord -l
> card 0: card0 [Cirrus Logic CS4281], device 0: CS4281 [CS4281]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
>
> How can I record data from the secondary codec?
the patch i made was only for enabling the 2nd codec.
it does nothing actually about playback/capture using the 2nd codec
yet, so it's normal that you receive the result above.
the multi-channel was _emulated_ in alsa-lib.
i've not read the spec of cs4281 precisely, but there must be setting
to specify which codec is used for playback/capture.
sorry, i have no time atm for digging more about this.
do you have clue about this?
anyway, what we need to do on the driver are:
- increase the number of channels for pcm playback/capture, or create
the second pcm stream for 2nd codec.
- set up the codec in prepare(), hw_params() or open() callback.
disable in close() if necessary.
please check other hardwares with double codecs.
>
> BTW. I have done:
...
>
> I believe this is a nice way to give the actual codec ID (0 is always the
> primary codec).
yes. but the exactly same hack was already on cvs at last week ;)
Takashi
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
next prev parent reply other threads:[~2002-05-27 16:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 15:59 Linux driver for cs4281 with TWO cs4299 codecs? tomasz motylewski
2002-05-22 18:11 ` Takashi Iwai
2002-05-22 18:33 ` tomasz motylewski
2002-05-22 21:15 ` tomasz motylewski
2002-05-23 8:40 ` Takashi Iwai
2002-05-23 10:27 ` tomasz motylewski
2002-05-27 16:37 ` tomasz motylewski
2002-05-27 16:49 ` Takashi Iwai [this message]
2002-05-28 20:10 ` does CS4281 have enough SRC for 4 input + 4 output channels? tomasz motylewski
2002-05-29 16:53 ` cs4281 with TWO cs4299 codecs - something works tomasz motylewski
2002-06-08 16:46 ` cs4281 - only 2 periods supported? tomasz motylewski
2002-06-10 13:54 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2002-05-22 18:27 Linux driver for cs4281 with TWO cs4299 codecs? Woller, Thomas
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=s5hhektedsh.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=T.Motylewski@bfad.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=arip@bfad.de \
--cc=pcaudio@crystal.cirrus.com \
--cc=pew@bfad.de \
--cc=twoller@crystal.cirrus.com \
/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