From: Xuebing Wang <xbing6@gmail.com>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: alsa-devel@alsa-project.org,
niranjan Patil <Niranjan.Patil@infocus.com>,
timur Tabi <timur@tabi.org>,
richard Jiang <Richard.Jiang@infocus.com>,
xiubo Li <Xiubo.Lee@gmail.com>
Subject: Re: About iMX6SL AUDMUX (port 7) and SSI3
Date: Wed, 25 Feb 2015 16:28:52 +0800 [thread overview]
Message-ID: <54ED87C4.4020105@gmail.com> (raw)
In-Reply-To: <20150220050127.GA2861@Asurada-CZ80>
Nicolin,
Thanks. As the mainline kernel supports I2S master mode, would you
please tell me which ASoC machine driver actually uses I2S master mode?
The reason I am asking is that I am using I2S master mode, I'd like to
reference that machine driver to configure audmux by function
imx_audmux_v2_configure_port().
Thanks.
On 02/20/2015 01:01 PM, Nicolin Chen wrote:
> On Thu, Feb 19, 2015 at 06:57:39PM +0800, Xuebing Wang wrote:
>
>> I am working on ASoC based sound driver for our iMX6SL based board.
>> There are 3 I2S peripherals on the board:
>> - iMX6SL pads AUD3 (as in AUD3_TXC), connect to peripheral Codec3
>> - iMX6SL pads AUD5 connect to Codec5
>> - iMX6SL pads Aud6, connect to Codec6
>>
>> Q1) Is internal SSI3 controller (ssi@02030000) actually *hard-wired*
>> to AUDMUX port 7?
> Yes. The first version of AUDMUX was only designed for two SSIs.
> Later version of i.MX SoC added an extra SSI so it had to connect
> to AUD7 which looks a bit weird.
>
>> Q2) Can I configure audmux as below?
>> - External AUD3 -> internal SSI3 (which is actually audmux port 7?)
>> - External AUD5 -> internal SSI2 (ssi@0202c000)
>> - External AUD6 -> internal SSI1 (ssi@02028000)
> I think you can.
>
> Nicolin
>
--
Xuebing
next prev parent reply other threads:[~2015-02-25 8:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 10:57 About iMX6SL AUDMUX (port 7) and SSI3 Xuebing Wang
2015-02-20 5:01 ` Nicolin Chen
2015-02-25 8:28 ` Xuebing Wang [this message]
2015-02-25 8:38 ` Nicolin Chen
2015-02-25 12:15 ` Xuebing Wang
2015-02-26 6:28 ` Nicolin Chen
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=54ED87C4.4020105@gmail.com \
--to=xbing6@gmail.com \
--cc=Niranjan.Patil@infocus.com \
--cc=Richard.Jiang@infocus.com \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=nicoleotsuka@gmail.com \
--cc=timur@tabi.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.