All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] TI: Davinci: NAND Driver Cleanup
Date: Tue, 16 Mar 2010 14:49:28 -0500	[thread overview]
Message-ID: <4B9FE0C8.8030808@freescale.com> (raw)
In-Reply-To: <8FFAA0BFC4E5374B8F85F65FE1F2BFA58B677263@dlee02.ent.ti.com>

Chemparathy, Cyril wrote:
> Please correct me if I am wrong here, but my understanding is that
> the raw variants are for native-endian access, while the non-raw ones
> could potentially force little-endian conversions for PCI.

The non-raw ones also provide ordering on some architectures, though I 
don't think this matters on ARM.  Unfortunately there doesn't seem to be 
an arch-neutral way to unbundle these.

> If so, since these on-chip registers must always be accessed native-endian, I felt that the raw accessors would be appropriate.

OK.

-Scott

  reply	other threads:[~2010-03-16 19:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-14 21:14 [U-Boot] [PATCH] TI: Davinci: NAND Driver Cleanup s-paulraj at ti.com
2010-03-15 17:27 ` Scott Wood
2010-03-16 18:24   ` Chemparathy, Cyril
2010-03-16 19:49     ` Scott Wood [this message]
2010-03-16 12:39 ` Nick Thompson
2010-03-16 18:05   ` Chemparathy, Cyril

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=4B9FE0C8.8030808@freescale.com \
    --to=scottwood@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.