public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Reinhard Meyer <u-boot@emk-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Struct SoC access
Date: Sat, 14 Aug 2010 21:40:06 +0200	[thread overview]
Message-ID: <4C66F116.7030109@emk-elektronik.de> (raw)
In-Reply-To: <AANLkTinxw-OZaU+EZ4TtyO1JeYKa0gw4j=6Uy8OLPhCc@mail.gmail.com>

Dear Mike Frysinger,
> On Sat, Aug 14, 2010 at 3:30 PM, Reinhard Meyer wrote:
>> #define DBU_ADDR 0xsomething (in a SoC header file)
>>
>> dbu_t *dbu = (dbu_t *)DBU_ADDR; (in a function)
> 
> needs to be volatile ...
> -mike
Why? The elements are used as parameters to readl/writel functions:
status = readl(&dbu->sr);

I am quite sure we are NOT supposed to directly access hardware:
status = dbu->sr;

Best Regards,
Reinhard

  reply	other threads:[~2010-08-14 19:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-14  9:07 [U-Boot] Make preparatory patches that initially have no effect? Reinhard Meyer
2010-08-14 14:30 ` Wolfgang Denk
2010-08-14 17:05   ` Reinhard Meyer
2010-08-14 18:46     ` Wolfgang Denk
2010-08-14 19:30       ` [U-Boot] Struct SoC access (was:Make preparatory patches that initially have no effect?) Reinhard Meyer
2010-08-14 19:36         ` Mike Frysinger
2010-08-14 19:40           ` Reinhard Meyer [this message]
2010-08-14 20:48             ` [U-Boot] Struct SoC access Mike Frysinger
2010-08-14 19:41         ` [U-Boot] Struct SoC access (was:Make preparatory patches that initially have no effect?) Wolfgang Denk
2010-08-14 19:58           ` [U-Boot] Struct SoC access Reinhard Meyer
2010-08-14 20:47             ` Reinhard Meyer
2010-08-14 21:49               ` Wolfgang Denk
2010-08-14 21:47             ` Wolfgang Denk
2010-08-14 22:15               ` Reinhard Meyer
2010-08-16 20:21                 ` Scott Wood
2010-08-17  6:58                   ` Reinhard Meyer

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=4C66F116.7030109@emk-elektronik.de \
    --to=u-boot@emk-elektronik.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox