From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] ARM: Xilinx: base header files and assembly macros
Date: Tue, 8 Feb 2011 14:30:32 +0000 [thread overview]
Message-ID: <20110208143032.GA27521@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <735942c6-d2d5-4ef0-96e7-37a477507abc@VA3EHSMHS023.ehs.local>
On Tue, Feb 08, 2011 at 07:08:14AM -0700, John Linn wrote:
> > -----Original Message-----
> > From: Russell King - ARM Linux [mailto:linux at arm.linux.org.uk]
> > Sent: Tuesday, February 08, 2011 1:27 AM
> > To: John Linn
> > Cc: linux-arm-kernel at lists.infradead.org; catalin.marinas at arm.com;
> glikely at secretlab.ca
> > Subject: Re: [PATCH 4/4] ARM: Xilinx: base header files and assembly
> macros
> >
> > On Mon, Feb 07, 2011 at 05:14:13PM -0700, John Linn wrote:
> > > I'm assuming you meant to change all addresses of devices (#defines)
> to
> > > use the IOMEM.
> > >
> > > I did that and it's ok. You also have to cast them to ints when
> putting
> > > the addresses into
> > > the resource for a platform device.
> >
> > Hang on. The reason I mentioned it was because you were passing some
> > of these into readl() et.al. readl() takes the mapped cookie, not the
> > physical address.
> >
> > Physical addresses should be integer like, virtual addresses should be
> > pointer like.
>
> Thanks for clarifying.
>
> It seems like it's better to leave the #defines without IOMEM, then use
> IOMEM where a variable,
> such as the address of the timer, is initialized with the #define.
>
> I see what you mean with regard to readl taking the cookie but yet
> physical addresses are also needed.
readl does not take physical addresses. Ever.
I can't work out what's going on here at the moment, and until I do I don't
see any justification to merging this as long as there is confusion between
what is a physical address and what isn't.
next prev parent reply other threads:[~2011-02-08 14:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1296922124-23379-1-git-send-email-john.linn@xilinx.com>
2011-02-05 16:08 ` [PATCH 1/4] ARM: Xilinx: Adding Xilinx platform infrastructure support John Linn
2011-02-05 16:16 ` Russell King - ARM Linux
2011-02-05 16:20 ` [PATCH 1/4] ARM: Xilinx: Adding Xilinx platform infrastructuresupport John Linn
[not found] ` <1296922124-23379-2-git-send-email-john.linn@xilinx.com>
2011-02-05 16:08 ` [PATCH 2/4] ARM: Xilinx: Adding Xilinx board support John Linn
2011-02-05 16:18 ` Russell King - ARM Linux
2011-02-05 16:21 ` John Linn
2011-02-05 17:25 ` John Linn
2011-02-07 15:44 ` John Linn
2011-02-07 20:54 ` Russell King - ARM Linux
2011-02-07 20:55 ` John Linn
[not found] ` <1296922124-23379-3-git-send-email-john.linn@xilinx.com>
2011-02-05 16:08 ` [PATCH 3/4] ARM: Xilinx: Adding timer support to the platform John Linn
2011-02-05 16:36 ` Russell King - ARM Linux
2011-02-05 17:12 ` John Linn
2011-02-08 14:35 ` Russell King - ARM Linux
2011-02-08 15:06 ` John Linn
2011-02-08 15:25 ` Arnd Bergmann
2011-02-08 17:11 ` John Linn
2011-02-08 17:53 ` John Linn
2011-02-08 18:24 ` Arnd Bergmann
2011-02-08 18:31 ` Grant Likely
[not found] ` <1296922124-23379-4-git-send-email-john.linn@xilinx.com>
2011-02-05 16:08 ` [PATCH 4/4] ARM: Xilinx: base header files and assembly macros John Linn
2011-02-05 16:43 ` Russell King - ARM Linux
2011-02-05 17:19 ` John Linn
2011-02-08 0:14 ` John Linn
2011-02-08 8:27 ` Russell King - ARM Linux
2011-02-08 14:08 ` John Linn
2011-02-08 14:30 ` Russell King - ARM Linux [this message]
[not found] <1296922637-24662-1-git-send-email-john.linn@xilinx.com>
[not found] ` <1296922637-24662-2-git-send-email-john.linn@xilinx.com>
[not found] ` <1296922637-24662-3-git-send-email-john.linn@xilinx.com>
[not found] ` <1296922637-24662-4-git-send-email-john.linn@xilinx.com>
2011-02-05 16:17 ` John Linn
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=20110208143032.GA27521@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).