[PATCH] ARM: allow, but warn, when issuing ioremap() on RAM
hemantp at ti.com
Sun Oct 10 10:23:51 EDT 2010
Russell King - ARM Linux wrote on Saturday, October 09, 2010 10:15 PM:
> On Sat, Oct 09, 2010 at 07:07:01PM +0300, Felipe Contreras wrote:
>> On Sat, Oct 9, 2010 at 4:52 PM, Russell King - ARM Linux
>> <linux at arm.linux.org.uk> wrote:
>>> On Thu, Oct 07, 2010 at 12:44:22PM +0300, Felipe Contreras wrote:
>>>> For issues related to this:
>>> This one nicely shows some of the problems which can occur with the
>>> memory type attributes - and this is not attributable to ioremap().
>>> ioremap() is used to map devices. It creates device memory type mappings.
>>> If what you're mapping doesn't support device memory type mappings, then
>>> accesses via an ioremap()'d region isn't going to work - as this guy is
>>> That's not because ioremap() is doing something wrong. It's doing what
>>> it's meant to do. The use is wrong, and is completely unrelated to the
>>> issue you've raised.
>> Ok, I was confused by Catalin's comment which does point to ioremap() on
>> normal RAM: http://article.gmane.org/gmane.linux.ports.arm.kernel/84504
> Me too - it doesn't appear to relate to the specified problem. You
> don't want to map RAM as device nor strongly ordered, and we still
> don't know what this "MMR" is.
Just to add, the issue I faced was a different issue and more to do with
specific access requirement for particular memory mapped region and what memory
types could be used for defining mappings of the region (or passed as ioremap
parameter). To summarize, I needed to use type=MT_STRONGLY_ORDERED to make access
to the peripheral registers work, which, unfortunately is not available in the
(BTW, I had referred MMR as memory mapped registers of the concerned peripheral.)
More information about the linux-arm-kernel