From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 4/4] ARM: Xilinx: Adding Xilinx board support
Date: Tue, 3 May 2011 09:52:20 +0100 [thread overview]
Message-ID: <20110503085220.GL28001@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <201105030958.14698.arnd@arndb.de>
On Tue, May 03, 2011 at 09:58:14AM +0200, Arnd Bergmann wrote:
> On Tuesday 03 May 2011 01:01:18 Russell King - ARM Linux wrote:
> > It is preferable to use the same mapping, as it ensures that you're not
> > going to create incompatible aliases.
>
> Is aliasing a problem for MMIO mappings? I would think that you can
> ioremap registers anywhere and as often as you want because they are
> never cacheable.
Provided the type and sharability is identical then there is no problem.
I wasn't referring to multiple ioremap()s of the same region - that
should be fine as the same attributes will be used. If you mix ioremap()
and iotable_init() then you _could_ have problems if you don't use
MT_DEVICE in the iotable.
What I'm basically saying is that mixing the methods of creating these
mappings makes it much easier to get tripped up over these issues.
next prev parent reply other threads:[~2011-05-03 8:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <90477150.2231869.1304372815517.JavaMail.root@sz0140a.emeryville.ca.mail.comcast.net>
2011-05-02 21:50 ` [RFC PATCH 4/4] ARM: Xilinx: Adding Xilinx board support johnlinn at comcast.net
2011-05-02 23:01 ` Russell King - ARM Linux
2011-05-02 23:36 ` Grant Likely
2011-05-03 7:58 ` Arnd Bergmann
2011-05-03 8:52 ` Russell King - ARM Linux [this message]
2011-05-03 10:35 ` Arnd Bergmann
[not found] <1518608384.2203937.1304349657551.JavaMail.root@sz0140a.emeryville.ca.mail.comcast.net>
2011-05-02 21:27 ` johnlinn at comcast.net
2011-05-02 21:36 ` Arnd Bergmann
2011-05-02 5:07 [RFC PATCH 0/4] ARM: Basic Xilinx Support Grant Likely
2011-05-02 5:08 ` [RFC PATCH 4/4] ARM: Xilinx: Adding Xilinx board support Grant Likely
2011-05-02 7:06 ` Michal Simek
2011-05-02 8:39 ` Arnd Bergmann
2011-05-02 13:29 ` Rob Herring
2011-05-02 15:52 ` Arnd Bergmann
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=20110503085220.GL28001@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).