From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Omair Mohammed Abdullah <omair.m.abdullah@linux.intel.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Question: PCM short and long sync formats
Date: Mon, 26 Mar 2012 14:33:05 +0100 [thread overview]
Message-ID: <20120326133305.GR3098@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F706F47.2090306@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 628 bytes --]
On Mon, Mar 26, 2012 at 06:59:43PM +0530, Omair Mohammed Abdullah wrote:
> On Monday 26 March 2012 05:38 PM, Mark Brown wrote:
> >Sorry, that's not really clarifying things. It looks like "long frame
> >sync" is just I2S but presumably there's some difference?
> Yes, in I2S mode, according to the spec I have, the frame sync leads
> the MSB of the data by 1 bit clock cycle. Whereas the 'long frame
> sync' mode starts with the MSB of the data.
This is probably left justified mode but I'm really not clear what
your question is here. Please ask a *specific* question, with reference
to what you find unclear in the code.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-03-26 13:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 10:21 Question: PCM short and long sync formats Omair Mohammed Abdullah
2012-03-21 11:51 ` Mark Brown
2012-03-26 9:06 ` Omair Mohammed Abdullah
2012-03-26 10:26 ` Mark Brown
2012-03-26 12:07 ` Omair Mohammed Abdullah
2012-03-26 12:08 ` Mark Brown
2012-03-26 13:29 ` Omair Mohammed Abdullah
2012-03-26 13:33 ` Mark Brown [this message]
2012-03-27 3:32 ` [PATCH] ASoC: Added PCM short and long frame " Omair Mohammed Abdullah
2012-03-27 3:34 ` Omair Mohammed Abdullah
2012-03-27 7:33 ` Lars-Peter Clausen
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=20120326133305.GR3098@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=omair.m.abdullah@linux.intel.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.