All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Eric Bénard" <eric@eukrea.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: imx-ssi.c & SND_SOC_DAIFMT_I2S
Date: Wed, 26 May 2010 12:37:53 +0200	[thread overview]
Message-ID: <20100526103753.GQ17272@pengutronix.de> (raw)
In-Reply-To: <4BFCEB10.6000205@eukrea.com>

Hi Eric,

On Wed, May 26, 2010 at 11:34:08AM +0200, Eric Bénard wrote:
> Hi Sascha,
>
> while trying to get a TI TLV320AIC23B codec configured as I2S master to  
> work with an i.MX27 using the latest git kernel, I noticed there may be  
> a problem in the slave I2S setting in imx-ssi.c
>
> Please find two captures of the I2S bus signals :
> - http://eukrea.com/tmp/initial_i2s.png : this is not an I2S signal,  
> both left & right are sent while Frame Sync is high (so I only get mono  
> output)
> - http://eukrea.com/tmp/i2s_slave.png : when I set I2S_MODE to 0x2 in  
> SCR register (scr |= SSI_SCR_NET | 0x40; at line 101 of imx-ssi.c), thus  
> setting the SSI in "I2S slave mode", I get a real I2S signal as shown on  
> this capture.
>
> I understand the actual I2S configuration may work with the Freescale's  
> PMIC but this chipset may not be fully I2S compliant and I think that  
> the actual setting prevent real I2S codecs from being used with the i.MX.
>
> Am I wrong here ?
> Shouldn't we use the I2S slave mode of the SSI instead of what is done  
> actually ?

I just had a look at the oscilloscope. For me it seems to make no
difference whether I use I2S mode or what is done in current driver.
Both look like your second picture.
So we can change it if there are no other objections.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2010-05-26 10:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26  9:34 imx-ssi.c & SND_SOC_DAIFMT_I2S Eric Bénard
2010-05-26 10:37 ` Sascha Hauer [this message]
2010-05-26 12:41   ` Eric Bénard
2010-05-27  0:56 ` Mark Brown
2010-05-27  1:15   ` Eric Bénard
2010-05-27  1:54     ` Mark Brown
2010-06-23 10:15     ` imx-ssi.c &amp; SND_SOC_DAIFMT_I2S anilkumar
2010-06-23 10:28       ` Eric Bénard

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=20100526103753.GQ17272@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=eric@eukrea.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.