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 20:15:25 +0800 [thread overview]
Message-ID: <54EDBCDD.7040108@gmail.com> (raw)
In-Reply-To: <20150225083837.GA6436@Asurada>
On 02/25/2015 04:38 PM, Nicolin Chen wrote:
> On Wed, Feb 25, 2015 at 04:28:52PM +0800, Xuebing Wang wrote:
>> Thanks. As the mainline kernel supports I2S master mode, would you please
>> tell me which ASoC machine driver actually uses I2S master mode?
> fsl-asoc-card.c
Nicolin,
Thanks. I am trying routing aud3 to internal ssi2. Thus in my case:
int_port = 2, ext_port = 3, right? Of course, there are int_port-- and
ext_port --.
As I am using I2S master mode (ssi2 generates both bit clock and frame
sync, thus (dai_fmt & MASK) == SND_SOC_DAIFMT_CBM_CFM. According to
iMX6SL reference manual, should TFSEL (bits 30..27) of int_ptcr be
IMX_AUDMUX_V2_PTCR_TFSEL(int_port) (note: int_port vs ext_port), rather
than the current IMX_AUDMUX_V2_PTCR_TFSEL(ext_port) in file fsl-asoc-card.c?
Thanks again.
>> 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().
> That driver is a general purpose driver for several CODECs supports.
> If you plan to get your machine driver upstream, you can try that
> one directly; Otherwise, you can extract the audmux configuration
> part for your own use.
>
> Nicolin
>
>
--
Xuebing
next prev parent reply other threads:[~2015-02-25 12:15 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
2015-02-25 8:38 ` Nicolin Chen
2015-02-25 12:15 ` Xuebing Wang [this message]
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=54EDBCDD.7040108@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox