linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: clean up ssi.txt, add definition for fsl, ssi-asynchronous
Date: Thu, 5 Mar 2009 19:44:50 -0600	[thread overview]
Message-ID: <ed82fe3e0903051744u1454b842pd1a0c90c016aa9c2@mail.gmail.com> (raw)
In-Reply-To: <49B06197.8010007@freescale.com>

On Thu, Mar 5, 2009 at 5:34 PM, Scott Wood <scottwood@freescale.com> wrote:

> 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"?

The latter.  I'll reword it.

-- 
Timur Tabi
Linux kernel developer at Freescale

      reply	other threads:[~2009-03-06  1:44 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
2009-03-06  1:44   ` Timur Tabi [this message]

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=ed82fe3e0903051744u1454b842pd1a0c90c016aa9c2@mail.gmail.com \
    --to=timur@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@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).