All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@nokia.com>
To: ext Arun KS <arunks@mistralsolutions.com>
Cc: "linux-omap@vger.kernel.org List" <linux-omap@vger.kernel.org>,
	alsa-devel@vger.kernel.org, felipe.balbi@nokia.com
Subject: Re: [PATCH 3/5] [RFC] ALSA ASOC Adds DSP DAI format support for platform driver
Date: Tue, 30 Sep 2008 16:11:38 +0300	[thread overview]
Message-ID: <20080930161138.41de23b3.jarkko.nikula@nokia.com> (raw)
In-Reply-To: <dfeb90390809292341l2264ff52m80830952b38ea25f@mail.gmail.com>

On Tue, 30 Sep 2008 12:11:45 +0530
"ext Arun KS" <arunks@mistralsolutions.com> wrote:

> > I think this is not enough. The word clock length equals to one BCLK
> > cycle in DSP mode. Not n channel bit BCLK cycles like in I2S.
> >
> 
> In DSP Mode, Frame sync is followed by two data words.
> I tested this patch and its working. Am i missing something ?
> 
I meant length of FS/LRC[IN | OUT] signal itself. E.g. see figures 3-7
and 3-8 in AIC23 data manual:

http://www.ti.com/lit/gpn/tlv320aic23

Now omap-mcbsp.c sets this FS length to 16 BCLK periods in
omap_mcbsp_dai_hw_params. Currently code is pretty much tailored for
16-bit stereo I2S so probably some McBSP configuration bits are better
set in another function than currently :-)


Jarkko

  parent reply	other threads:[~2008-09-30 13:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-29  9:50 [PATCH 3/5] [RFC] ALSA ASOC Adds DSP DAI format support for platform driver Arun KS
2008-09-29 11:06 ` Mark Brown
2008-09-29 11:15 ` Jarkko Nikula
2008-09-29 12:54   ` Arun KS
2008-09-29 12:54   ` Arun KS
2008-09-30  6:41   ` Arun KS
2008-09-30 13:11     ` Jarkko Nikula
2008-09-30 13:11     ` Jarkko Nikula [this message]
2008-09-30  6:41   ` Arun KS
2008-09-29 11:15 ` Jarkko Nikula
  -- strict thread matches above, loose matches on Subject: below --
2008-09-29  9:50 Arun KS

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=20080930161138.41de23b3.jarkko.nikula@nokia.com \
    --to=jarkko.nikula@nokia.com \
    --cc=alsa-devel@vger.kernel.org \
    --cc=arunks@mistralsolutions.com \
    --cc=felipe.balbi@nokia.com \
    --cc=linux-omap@vger.kernel.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.