]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
arm64: Remove arm64_dma32_phys_limit and its uses
authorCatalin Marinas <catalin.marinas@arm.com>
Thu, 7 Jan 2021 14:40:08 +0000 (14:40 +0000)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 14 May 2021 07:50:46 +0000 (09:50 +0200)
commit2281df0b0226610e235f49ed75bf6ad57cb04762
treeb3be36772d35600453b332b3a89e2befe3bf3b30
parent00d9f429af039a76a301c1eb7b9e617e9caaf7d2
arm64: Remove arm64_dma32_phys_limit and its uses

commit d78050ee35440d7879ed94011c52994b8932e96e upstream.

With the introduction of a dynamic ZONE_DMA range based on DT or IORT
information, there's no need for CMA allocations from the wider
ZONE_DMA32 since on most platforms ZONE_DMA will cover the 32-bit
addressable range. Remove the arm64_dma32_phys_limit and set
arm64_dma_phys_limit to cover the smallest DMA range required on the
platform. CMA allocation and crashkernel reservation now go in the
dynamically sized ZONE_DMA, allowing correct functionality on RPi4.

Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Cc: Chen Zhou <chenzhou10@huawei.com>
Reviewed-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Tested-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de> # On RPi4B
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
arch/arm64/include/asm/processor.h
arch/arm64/mm/init.c