From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] arm64: allow ioremap_cache() to use existing RAM mappings
Date: Tue, 29 Oct 2013 16:41:42 +0000 [thread overview]
Message-ID: <20131029164142.GF3472@arm.com> (raw)
In-Reply-To: <1382626457.1768.80.camel@deneb.redhat.com>
On Thu, Oct 24, 2013 at 03:54:17PM +0100, Mark Salter wrote:
> Some drivers (ACPI notably) use ioremap_cache() to map an area which could
> either be outside of kernel RAM or in an already mapped reserved area of
> RAM. To avoid aliases with different caching attributes, ioremap() does
> not allow RAM to be remapped. But for ioremap_cache(), the existing kernel
> mapping may be used.
>
> Signed-off-by: Mark Salter <msalter@redhat.com>
Looks good. Thanks.
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Salter <msalter@redhat.com>
Cc: Will Deacon <Will.Deacon@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] arm64: allow ioremap_cache() to use existing RAM mappings
Date: Tue, 29 Oct 2013 16:41:42 +0000 [thread overview]
Message-ID: <20131029164142.GF3472@arm.com> (raw)
In-Reply-To: <1382626457.1768.80.camel@deneb.redhat.com>
On Thu, Oct 24, 2013 at 03:54:17PM +0100, Mark Salter wrote:
> Some drivers (ACPI notably) use ioremap_cache() to map an area which could
> either be outside of kernel RAM or in an already mapped reserved area of
> RAM. To avoid aliases with different caching attributes, ioremap() does
> not allow RAM to be remapped. But for ioremap_cache(), the existing kernel
> mapping may be used.
>
> Signed-off-by: Mark Salter <msalter@redhat.com>
Looks good. Thanks.
--
Catalin
next prev parent reply other threads:[~2013-10-29 16:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 13:36 [PATCH] arm64: allow ioremap_cache() to use existing RAM mappings Mark Salter
2013-10-21 13:36 ` Mark Salter
2013-10-23 9:18 ` Catalin Marinas
2013-10-23 9:18 ` Catalin Marinas
2013-10-23 13:46 ` Mark Salter
2013-10-23 13:46 ` Mark Salter
2013-10-23 14:37 ` Catalin Marinas
2013-10-23 14:37 ` Catalin Marinas
2013-10-24 14:54 ` [PATCH v2] " Mark Salter
2013-10-24 14:54 ` Mark Salter
2013-10-29 16:41 ` Catalin Marinas [this message]
2013-10-29 16:41 ` Catalin Marinas
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=20131029164142.GF3472@arm.com \
--to=catalin.marinas@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.