All of lore.kernel.org
 help / color / mirror / Atom feed
From: Omair Mohammed Abdullah <omair.m.abdullah@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Question: PCM short and long sync formats
Date: Mon, 26 Mar 2012 14:36:53 +0530	[thread overview]
Message-ID: <4F7031AD.3090202@linux.intel.com> (raw)
In-Reply-To: <20120321115146.GC3226@opensource.wolfsonmicro.com>

On Wednesday 21 March 2012 05:21 PM, Mark Brown wrote:
> On Wed, Mar 21, 2012 at 03:51:36PM +0530, Omair Mohammed Abdullah wrote:
>
>> I was looking for PCM short frame sync and PCM long frame sync, but
>> they are not present in soc-dai.h (FORMAT_MASK). Is there a way to
>> derive them from other formats or should I just add them?
>
> What do you mean when you say "PCM short frame sync" and "PCM long
> frame sync"?

Sorry for the late reply, I was away.

What I mean by short/long frame sync is: the frame sync lasts for 1 
bit/1 word wide.

Eg.: For short frame sync, we get a frame sync signal for 1 clock before 
the first bit on the RX/TX.

It is different from I2S mode where the frame sync is inverted and the 
transition starts 1 clock before the bits and lasts till bit 1.

  reply	other threads:[~2012-03-26  9:04 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 [this message]
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
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=4F7031AD.3090202@linux.intel.com \
    --to=omair.m.abdullah@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.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.