Searched hist:"7 bc90e01c3f66c137e7e761f574bbf883087d590" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/arch/x86/platform/efi/ |
| H A D | efi.c | diff 7bc90e01c3f66c137e7e761f574bbf883087d590 Fri Sep 28 19:56:08 CDT 2012 Josh Triplett <josh@joshtriplett.org> efi: Add a function to look up existing IO memory mappings
The EFI initialization creates virtual mappings for EFI boot services
memory, so if a driver wants to access EFI boot services memory, it
cannot call ioremap itself; doing so will trip the WARN about mapping
RAM twice. Thus, a driver accessing EFI boot services memory must do so
via the existing mapping already created during EFI intiialization.
Since the EFI code already maintains a memory map for that memory, add a
function efi_lookup_mapped_addr to look up mappings in that memory map.
Signed-off-by: Josh Triplett <josh@joshtriplett.org>
Link: http://lkml.kernel.org/r/0eb48ae012797912874919110660ad420b90268b.1348876882.git.josh@joshtriplett.org
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
|
| /openbmc/linux/include/linux/ |
| H A D | efi.h | diff 7bc90e01c3f66c137e7e761f574bbf883087d590 Fri Sep 28 19:56:08 CDT 2012 Josh Triplett <josh@joshtriplett.org> efi: Add a function to look up existing IO memory mappings
The EFI initialization creates virtual mappings for EFI boot services
memory, so if a driver wants to access EFI boot services memory, it
cannot call ioremap itself; doing so will trip the WARN about mapping
RAM twice. Thus, a driver accessing EFI boot services memory must do so
via the existing mapping already created during EFI intiialization.
Since the EFI code already maintains a memory map for that memory, add a
function efi_lookup_mapped_addr to look up mappings in that memory map.
Signed-off-by: Josh Triplett <josh@joshtriplett.org>
Link: http://lkml.kernel.org/r/0eb48ae012797912874919110660ad420b90268b.1348876882.git.josh@joshtriplett.org
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
|