From: linux@horizon.com
To: joern@wohnheim.fh-wedel.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: Being more anal about iospace accesses..
Date: 15 Sep 2004 18:25:36 -0000 [thread overview]
Message-ID: <20040915182536.20820.qmail@science.horizon.com> (raw)
> Nice.
>
> But it still leaves me confused. Before I had this code:
>
> struct regs {
> uint32_t status;
> ...
> }
>
> ...
>
> struct regs *regs = ioremap(...);
> uint32_t status = regs->status;
> ...
>
> So now I should do it like this:
>
> #define REG_STATUS 0
>
> ...
>
> void __iomem *regs = ioremap(...);
> uint32_t status = readl(regs + REG_STATUS);
> ...
>
> But wait, that only works when long is 32bit wide. Plus I could be
> stupid enough and "#define REG_STATUS 64" while the register space is
> just 64 bytes long. It solves the confusion about address spaces,
> agreed, but overall I'm more confused now. Hope it's just temporary.
No, you should do:
struct regs {
uint32_t status;
...
}
...
struct regs __iomem *regs = ioremap(...);
uint32_t status = ioread32(®s->status);
next reply other threads:[~2004-09-15 18:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 18:25 linux [this message]
[not found] <Pine.LNX.4.58.0409081543320.5912@ppc970.osdl.org>
[not found] ` <Pine.LNX.4.58.0409150737260.2333@ppc970.osdl.org>
2004-09-15 16:30 ` Linus Torvalds
2004-09-15 16:54 ` Jörn Engel
2004-09-15 17:07 ` Linus Torvalds
2004-09-15 17:32 ` Jörn Engel
2004-09-15 17:57 ` Linus Torvalds
2004-09-15 18:06 ` Linus Torvalds
2004-09-15 19:34 ` Greg KH
2004-09-15 19:53 ` Linus Torvalds
2004-09-15 20:06 ` Greg KH
2004-09-16 14:58 ` Horst von Brand
2004-09-15 17:45 ` Nikita Danilov
2004-09-15 18:09 ` Linus Torvalds
2004-09-15 18:40 ` Chris Wedgwood
2004-09-15 17:07 ` Jeff Garzik
2004-09-15 17:16 ` Roland Dreier
2004-09-15 17:39 ` Linus Torvalds
2004-09-15 20:07 ` Russell King
2004-09-15 17:36 ` Horst von Brand
2004-09-15 17:40 ` Brian Gerst
2004-09-15 16:56 ` Dave Jones
2004-09-15 17:19 ` Roger Luethi
2004-09-15 17:23 ` Richard B. Johnson
2004-09-15 22:21 ` Deepak Saxena
2004-09-15 22:46 ` Linus Torvalds
2004-09-15 23:09 ` Deepak Saxena
2004-09-16 12:51 ` Geert Uytterhoeven
2004-09-16 22:10 ` Deepak Saxena
2004-09-15 22:29 ` Roland Dreier
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=20040915182536.20820.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®