summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorSantosh Shilimkar <santosh.shilimkar@ti.com>2013-08-01 04:12:01 +0200
committerRussell King <rmk+kernel@arm.linux.org.uk>2013-10-31 15:49:29 +0100
commit26ba47b18318abe7dadbe9294a611c0e932651d8 (patch)
treeab542f22462c683920457069bf95893252f42538 /drivers
parentARM: 7797/1: mmc: Use dma_max_pfn(dev) helper for bounce_limit calculations (diff)
downloadlinux-26ba47b18318abe7dadbe9294a611c0e932651d8.tar.xz
linux-26ba47b18318abe7dadbe9294a611c0e932651d8.zip
ARM: 7805/1: mm: change max*pfn to include the physical offset of memory
Most of the kernel code assumes that max*pfn is maximum pfns because the physical start of memory is expected to be PFN0. Since this assumption is not true on ARM architectures, the meaning of max*pfn is number of memory pages. This is done to keep drivers happy which are making use of of these variable to calculate the dma bounce limit using dma_mask. Now since we have a architecture override possibility for DMAable maximum pfns, lets make meaning of max*pfns as maximum pnfs on ARM as well. Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Will Deacon <will.deacon@arm.com> Cc: Nicolas Pitre <nicolas.pitre@linaro.org> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions