diff options
author | Grygorii Strashko <grygorii.strashko@ti.com> | 2015-07-31 15:46:18 +0100 |
---|---|---|
committer | Will Deacon <will.deacon@arm.com> | 2015-08-03 15:38:19 +0100 |
commit | 37cf524f9360f9165d67459b7bf795c01824df98 (patch) | |
tree | b70dcfb41e49ee66fe20f02edbe3c15bf6186f3d /arch/arm/kernel/Makefile | |
parent | 514f161abcda065914f7ea8954c815eee98074a5 (diff) | |
download | linux-37cf524f9360f9165d67459b7bf795c01824df98.tar.bz2 |
ARM: psci: boot_secondary: replace __pa with virt_to_idmap
On some PAE systems (e.g. TI Keystone), memory is above the 32-bit
addressable limit, and the interconnect provides an aliased view of
parts of physical memory in the 32-bit addressable space. This alias
is strictly for boot time usage, and is not otherwise usable because
of coherency limitations.
In this case, virt_to_phys(secondary_startup) would return the
physical address of the secondary CPU boot entry point, but on such
systems, this would be above the 4GB limit.
A separate function, virt_to_idmap(), has been provided to return a
usable physical address for functions in the identity mapping, and
this must be used in preference to virt_to_phys() or __pa() to find
the physical entry point for functions in the identity mapping range.
For other systems, virt_to_idmap() and virt_to_phys() return identical
physical addresses.
Acked-by: Santosh Shilimkar <ssantosh@kernel.org>
Acked-by: Nicolas Pitre <nico@linaro.org>
Tested-by Vitaly Andrianov <vitalya@ti.com>
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
[Mark: apply rmk's suggested rewording]
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Cc: Russell King <rmk+kernel@arm.linux.org.uk>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Diffstat (limited to 'arch/arm/kernel/Makefile')
0 files changed, 0 insertions, 0 deletions