Skip to contentSkip to conversation

Adding channels on multicodec soundcard

DISCUSSION Steven Wawryk 2 participants 4 messages Jan 15, 2016

lore
Share & tools
lore
#0 lore raw

Hi,

I'm trying to write an ALSA soundcard driver module for an embedded Zynq-based system with 4 Cirrus CS42448 codecs. Each codec has 6 analog output channels and I'd like the "soundcard" to have 24 channels (6 to each codec). I've been having trouble getting it to do this. The hw_params for the codec, card and "I2S" IP core drivers all get the same parameters, including number of channels.

When I define 4 snd_soc_dai_link's, each with 1 codec, then 4 "devices" are set up for the card and I can access 6 channels on 1 codec (1 "device") at a time. When I define 1 snd_soc_dai_link with 4 codecs then 1 "device" is set up and I can still only access 6 channels, but it appears to use all 4 codecs (somehow - I haven't yet worked out the channel allocation). I can't seem to get 24 channels to the card, splitting into 6 channels to each of the codecs.

Can anyone suggest how I should be going about this?

The linux kernel is 3.17 from PetaLinux (Xilinx).

Cheers,
Steve

#1 lore raw

I should have added that there is a pair (capture + playback) of serial "I2S" links (actually TDM) between the Zynq and *each* codec.

Quoted 18 lines · Steven Wawryk

Hi,

I'm trying to write an ALSA soundcard driver module for an embedded Zynq-based system with 4 Cirrus CS42448 codecs. Each codec has 6 analog output channels and I'd like the "soundcard" to have 24 channels (6 to each codec). I've been having trouble getting it to do this. The hw_params for the codec, card and "I2S" IP core drivers all get the same parameters, including number of channels.

When I define 4 snd_soc_dai_link's, each with 1 codec, then 4 "devices" are set up for the card and I can access 6 channels on 1 codec (1 "device") at a time. When I define 1 snd_soc_dai_link with 4 codecs then 1 "device" is set up and I can still only access 6 channels, but it appears to use all 4 codecs (somehow - I haven't yet worked out the channel allocation). I can't seem to get 24 channels to the card, splitting into 6 channels to each of the codecs.

Can anyone suggest how I should be going about this?

The linux kernel is 3.17 from PetaLinux (Xilinx).

Cheers,
Steve

_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

#2 lore raw
Quoted 26 lines · Steven Wawryk

I should have added that there is a pair (capture + playback) of serial "I2S" links (actually TDM) between the Zynq and *each* codec.

Quoted 19 lines · Steven Wawryk

Hi,

I'm trying to write an ALSA soundcard driver module for an embedded Zynq-based system with 4 Cirrus CS42448 codecs. Each codec has 6 analog output channels and I'd like the "soundcard" to have 24 channels (6 to each codec). I've been having trouble getting it to do this. The hw_params for the codec, card and "I2S" IP core drivers all get the same parameters, including number of channels.

When I define 4 snd_soc_dai_link's, each with 1 codec, then 4 "devices" are set up for the card and I can access 6 channels on 1 codec (1 "device") at a time. When I define 1 snd_soc_dai_link with 4 codecs then 1 "device" is set up and I can still only access 6 channels, but it appears to use all 4 codecs (somehow - I haven't yet worked out the channel allocation). I can't seem to get 24 channels to the card, splitting into 6 channels to each of the codecs.

Heh, I just composed, but didn't send an almost identical question -- in my case I want 2 or 3 freescale SSI ports to behave as one device, all in perfect synchrony. I'd love to hear the answer from somebody that really understands the code better than I.

To get multiple codecs on one DAI link gracefully, you need a set of patches, the last of which was roughly "[PATCH] ASoC: dapm: Don't add prefix to widget stream name", See arnaud/nicolin/liam helping me back
here: http://mailman.alsa-project.org/pipermail/alsa-devel/2015-September/097564.html.
The first time I see this patch is in 4.2. 3.17 might be a challenge.

I sure suspect that having multiple cpu-side ports on the link isn't supported.
Looking in soc.h
(http://lxr.free-electrons.com/source/include/sound/soc.h#L952), I see several places where there are arrays of codecs, but never an array of cpu-side ports inside one device.

So, I can share my work on how to get multiple codecs on a single TDM bus, but I'm not sure how to get multiple interfaces to appear as one device.

-Caleb

Quoted 17 lines
Quoted 11 lines

Can anyone suggest how I should be going about this?

The linux kernel is 3.17 from PetaLinux (Xilinx).

Cheers,
Steve

_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

#3 lore raw

Thanks Caleb,

Fortunately with 4 different (physical) TDM link pairs I don't have to get the codecs to play together gracefully on a single link. From what you've said it sounds like my first method with 4 snd_soc_dai_link's, representing 4 physical links is probably the better approach.

So I guess my question boils down to basically the same as yours - how to get multiple devices acting as, and routing through, a single device?

Steve

Quoted 70 lines · ccrome
Quoted 5 lines · Steven Wawryk

I should have added that there is a pair (capture + playback) of serial "I2S" links (actually TDM) between the Zynq and *each* codec.

Quoted 19 lines
Quoted 18 lines · Steven Wawryk

Hi,

I'm trying to write an ALSA soundcard driver module for an embedded Zynq-based system with 4 Cirrus CS42448 codecs. Each codec has 6 analog output channels and I'd like the "soundcard" to have 24 channels (6 to each codec). I've been having trouble getting it to do this. The hw_params for the codec, card and "I2S" IP core drivers all get the same parameters, including number of channels.

When I define 4 snd_soc_dai_link's, each with 1 codec, then 4 "devices" are set up for the card and I can access 6 channels on 1 codec (1 "device") at a time. When I define 1 snd_soc_dai_link with 4 codecs then 1 "device" is set up and I can still only access 6 channels, but it appears to use all 4 codecs (somehow - I haven't yet worked out the channel allocation). I can't seem to get 24 channels to the card, splitting into 6 channels to each of the codecs.

Heh, I just composed, but didn't send an almost identical question -- in my case I want 2 or 3 freescale SSI ports to behave as one device, all in perfect synchrony. I'd love to hear the answer from somebody that really understands the code better than I.

To get multiple codecs on one DAI link gracefully, you need a set of patches, the last of which was roughly "[PATCH] ASoC: dapm: Don't add prefix to widget stream name", See arnaud/nicolin/liam helping me back
here: http://mailman.alsa-project.org/pipermail/alsa-devel/2015-September/097564.html.
The first time I see this patch is in 4.2. 3.17 might be a challenge.

I sure suspect that having multiple cpu-side ports on the link isn't supported.
Looking in soc.h
(http://lxr.free-electrons.com/source/include/sound/soc.h#L952), I see several places where there are arrays of codecs, but never an array of cpu-side ports inside one device.

So, I can share my work on how to get multiple codecs on a single TDM bus, but I'm not sure how to get multiple interfaces to appear as one device.

-Caleb

Quoted 12 lines
Quoted 11 lines

Can anyone suggest how I should be going about this?

The linux kernel is 3.17 from PetaLinux (Xilinx).

Cheers,
Steve

_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Quoted 4 lines

_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

_______________________________________________
Alsa-devel mailing list
[email protected]
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel