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 16:45:57 -0600	[thread overview]
Message-ID: <4CF6D025.4010802@freescale.com> (raw)
In-Reply-To: <20101130195010.4fbdd9c6@udp111988uds.am.freescale.net>

Wood Scott-B07421 wrote:
> 
> Careful with the barriers.
> 
> You've got a raw readback, which means it's not going to wait for
> completion with the twi/isync hack.

You told me that since I'm doing a read following a write to uncached memory,
that I don't need a sync.

And what twi/isync hack are you talking about?  The one in in_8?

> 
> Ordinarily that would be OK, since you only need ordering between the
> readb and the first access in set_mux_to_diu().  Unfortunately, that
> first access is an 8-bit access, which for some strange reason does
> sync differently than 16/32-bit accesses.  The latter do sync+write,
> but 8-bit does write+eieio.  So there's no barrier between the read
> and the write.

Wait, I don't understand.  Where are you getting this from?  What do you mean by
16-bit accesses does sync+write vs. write+eieio?  Where is the sync/eieio coming
from?

As for why I don't use in_8, etc, it's because I'm trying to optimize this code.
 Unlike Dave's code, this stuff needs to be as fast as possible.  Although, I
wonder if an extra sync will make a difference considering the overhead of
switching the muxes.

-- 
Timur Tabi
Linux kernel developer at Freescale

  parent reply	other threads:[~2010-12-01 22:45 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 [this message]
2010-12-01 23:00     ` Scott Wood
2010-12-01 23:28       ` Timur Tabi
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=4CF6D025.4010802@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.