From: Scott Wood <scottwood@freescale.com>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: clean up ssi.txt, add definition for fsl, ssi-asynchronous
Date: Thu, 05 Mar 2009 17:34:47 -0600 [thread overview]
Message-ID: <49B06197.8010007@freescale.com> (raw)
In-Reply-To: <1236295403-11954-1-git-send-email-timur@freescale.com>
Timur Tabi wrote:
> +- fsl,ssi-asynchronous:
> + If specific, the SSI is to be programmed in asynchronous
> + mode. In this mode, SRCK and STCK must be connected to the
> + same clock, and SRFS and STFS must also be connected to the
> + same clock. This allows playback and capture to use
> + different sample sizes.
s/specific/specified/
Does the above mean "SRCK, STCK, SRFS, and STFS must all be connected to
the same clock", or does it mean "SRCK must be connected to the same
clock as STCK, and SRFS must be connected to the same clock as STFS"?
-Scott
next prev parent reply other threads:[~2009-03-05 23:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 23:23 [PATCH] powerpc: clean up ssi.txt, add definition for fsl, ssi-asynchronous Timur Tabi
2009-03-05 23:34 ` Scott Wood [this message]
2009-03-06 1:44 ` Timur Tabi
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=49B06197.8010007@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).