From: Dong Aisheng <b29396@freescale.com>
To: George Stefan <stefan.george87@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Fabio Estevam <festevam@gmail.com>,
Lauri Hintsala <lauri.hintsala@bluegiga.com>
Subject: Re: SAIF configuration on imx28
Date: Thu, 23 Aug 2012 15:46:17 +0800 [thread overview]
Message-ID: <20120823074617.GI10057@shlinux2.ap.freescale.net> (raw)
In-Reply-To: <CAACwSTLLKCKj8rOfvqVZ5zCBTCUaFEJMEeA3oNBgnQRHFtciKQ@mail.gmail.com>
On Thu, Aug 23, 2012 at 03:13:11PM +0800, George Stefan wrote:
> 2012/8/23 Dong Aisheng <b29396@freescale.com>
>
> On Thu, Aug 23, 2012 at 02:41:30PM +0800, George Stefan wrote:
> ...
> > /*set the saif clk mux, saif0/saif1 both use saif0 clk*/
> > __raw_writel(BF_DIGCTL_CTRL_SAIF_CLKMUX_SEL(0x0), \
> Should this be 0x2 if both saif0 and saif1 are using saif0 clk?
> > IO_ADDRESS(DIGCTL_PHYS_ADDR) + HW_DIGCTL_CTRL);
> > Using this configuration i am not able to receive IRQs from DMA and
> i
> > think the reason
> > is that SAIF is not receiving the CLK.
> > What do you think?
> > Thanks,
> > George.
>
> Regards
> Dong Aisheng
>
> Yes, it should be 0x2 if they are using saif0 clk. but it they are using
> the CLK from an external device
> which is master, i think that they should use an independent clock.
> "In slave clocking mode, the SAIF configures the BITCLK and LRCLK pins as
> inputs, and
> the off-chip codec is responsible for driving both clocks to the
> SAIF"(imx28 reference manual)
> 0x0 - DIRECT - SAIF0 clock pins selected for SAIF0 input clocks, and SAIF1
> clock pins selected for
> SAIF1 input clocks.
> Am i interpreting this in the wrong way?
Your understand is right if all are working on slave mode.
But be noted that the current driver in mainline only supports master mode,
mainly due to playback can not work on slave mode(see spec) while capture can.
If all are in slave mode, that means the playback may not work.
You should make sure if your requirements really wants that.
And if you want to run in slave mode, you need change the mainline driver
to support it.
Regards
Dong Aisheng
next prev parent reply other threads:[~2012-08-23 8:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 11:24 SAIF configuration on imx28 George Stefan
2012-08-21 11:56 ` Fabio Estevam
2012-08-21 12:39 ` George Stefan
2012-08-22 8:25 ` George Stefan
2012-08-22 21:30 ` Fabio Estevam
2012-08-23 6:41 ` George Stefan
2012-08-23 6:48 ` Dong Aisheng
2012-08-23 7:13 ` George Stefan
2012-08-23 7:46 ` Dong Aisheng [this message]
2012-08-23 9:15 ` George Stefan
2012-08-23 12:54 ` George Stefan
2012-08-23 12:59 ` Fabio Estevam
2012-08-23 13:09 ` George Stefan
2012-08-23 13:15 ` Fabio Estevam
2012-08-23 14:50 ` George Stefan
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=20120823074617.GI10057@shlinux2.ap.freescale.net \
--to=b29396@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=festevam@gmail.com \
--cc=lauri.hintsala@bluegiga.com \
--cc=stefan.george87@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 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.