of: Support more than one crash kernel regions for kexec -s
authorZhen Lei <thunder.leizhen@huawei.com>
Fri, 6 May 2022 11:44:01 +0000 (19:44 +0800)
committerCatalin Marinas <catalin.marinas@arm.com>
Sat, 7 May 2022 18:57:35 +0000 (19:57 +0100)
commit8af6b91f58341325bf74ecb0389ddc0039091d84
tree7b500461acf7623cf39030f2ff4dec02eb5cdf01
parentfb319e77a0e70b9ccfef87827d34b10d6bc2ccce
of: Support more than one crash kernel regions for kexec -s

When "crashkernel=X,high" is used, there may be two crash regions:
high=crashk_res and low=crashk_low_res. But now the syscall
kexec_file_load() only add crashk_res into "linux,usable-memory-range",
this may cause the second kernel to have no available dma memory.

Fix it like kexec-tools does for option -c, add both 'high' and 'low'
regions into the dtb.

Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
Acked-by: Rob Herring <robh@kernel.org>
Acked-by: Baoquan He <bhe@redhat.com>
Link: https://lore.kernel.org/r/20220506114402.365-6-thunder.leizhen@huawei.com
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
drivers/of/kexec.c