All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Wawryk <stevenw@acres.com.au>
To: alsa-devel@alsa-project.org
Subject: Re: Adding channels on multicodec soundcard
Date: Fri, 15 Jan 2016 16:54:25 +1030	[thread overview]
Message-ID: <56989099.3050404@acres.com.au> (raw)
In-Reply-To: <5698894D.2030002@acres.com.au>


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


On 15/01/16 16:23, Steven Wawryk wrote:
>
> 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
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2016-01-15  6:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15  5:53 Adding channels on multicodec soundcard Steven Wawryk
2016-01-15  6:24 ` Steven Wawryk [this message]
2016-01-15  7:14   ` ccrome
2016-01-15  8:29     ` Steven Wawryk

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=56989099.3050404@acres.com.au \
    --to=stevenw@acres.com.au \
    --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.