All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] p1022ds: fix switching of DIU/LBC signals
Date: Wed, 1 Dec 2010 17:28:28 -0600	[thread overview]
Message-ID: <4CF6DA1C.3080004@freescale.com> (raw)
In-Reply-To: <20101201170018.62ab7921@udp111988uds.am.freescale.net>

Scott Wood wrote:
>> You told me that since I'm doing a read following a write to uncached memory,
>> > that I don't need a sync.
> No, I was talking about a write followed by a read, to the same location.

That's what I said. Read following write == write followed by read.

> out_8 should be fixed to behave like the other accessors.

Ok, but I'm not using any of the I/O accessors, so this doesn't affect me.

I just need to make sure that the read is executed after the write, and that the
read completes before I continue.  So I should I put an isync between the write
and the read, and a sync after the read?

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2010-12-01 23:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01  0:36 [U-Boot] [PATCH] p1022ds: fix switching of DIU/LBC signals Timur Tabi
2010-12-01  1:50 ` Scott Wood
2010-12-01 13:01   ` Kumar Gala
2010-12-01 13:51     ` Liu Dave-R63238
2010-12-01 14:12       ` Tabi Timur-B04825
2010-12-01 14:38         ` Liu Dave-R63238
2010-12-01 22:45   ` Timur Tabi
2010-12-01 23:00     ` Scott Wood
2010-12-01 23:28       ` Timur Tabi [this message]
2010-12-01 23:54         ` Scott Wood
2010-12-02 17:45           ` 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=4CF6DA1C.3080004@freescale.com \
    --to=timur@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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.