Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Shawn Embedded <programassem@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Support two wm8962 codec in i.mx6 board.
Date: Mon, 16 Mar 2015 17:55:04 -0700	[thread overview]
Message-ID: <20150317005503.GA5480@Asurada-GSX> (raw)
In-Reply-To: <CAOaGyfUHS90nKcSxpQZm7X3Lgwtb_9V4xLzyObhd5v=diGHJLw@mail.gmail.com>

Hi Shawn,

On Mon, Mar 16, 2015 at 03:30:49PM +0800, Shawn Embedded wrote:

>     Now there is a wm8962 on the i.mx6 board, running well, and we
> want to add an extra wm8962 to the board, connected to i.mx6 on
> another SSI port through a different i.mx6's AUDMUX port. The two
> wm8962 will work independently completely, at the same time possiblly.

I'm not sure if your requirement is to create another dai-link. But
have you tried to simply add a new device node for the new dai-link?

Supposing two WM8962 chips on one board, there should be two WM8962
nodes hanging to the I2C node with different I2C slave addresses.

So you may need two different dai-link nodes for each of the WM8962
i2c nodes as well. And, of course, you need to specify different SSIs
and different AUDMUX ports for two dai-link nodes.

Then you will get two sound card in the system.

Nicolin

  reply	other threads:[~2015-03-17  0:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16  7:30 Support two wm8962 codec in i.mx6 board Shawn Embedded
2015-03-17  0:55 ` Nicolin Chen [this message]
2015-03-17  1:51   ` Shawn Embedded
2015-03-17 18:00     ` Nicolin Chen
2015-03-18  1:12       ` Shawn Embedded
2015-03-18  1:33         ` Nicolin Chen
2015-03-18  4:48           ` Shawn Embedded
2015-03-18  4:58             ` Nicolin Chen
2015-03-18  5:10               ` Shawn Embedded

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=20150317005503.GA5480@Asurada-GSX \
    --to=nicoleotsuka@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=programassem@gmail.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