[PATCHv2 0/2] arm64: fdt: fix membock add/cap ordering

[Pingfan Liu]

In fact, V2 tackles this issue at efi_init() for both arm64 and risc-v.

Since in Zhen Lei's series "[PATCH v17 00/10] support reserving
crashkernel above 4G on arm64 kdump", [8/10] is self-standing and
meaningful. I abstract and utilize it.

I make a small change in it in order to use
early_init_dt_check_for_usable_mem_range() outside of/fdt.
(Cc: Zhen, please let me know if it is not fine for you.)

So finally these two patches can be applied as candidates for
Fixes: b261dba2fdb2 ("arm64: kdump: Remove custom linux,usable-memory-range handling")

[1]: https://lore.kernel.org/all/20211210065533.2023-9-thunder.leizhen@huawei.com/

v1 -> v2:
  Adopt Rob's suggestion to call
early_init_dt_check_for_usable_mem_range() from efi_init()

Cc: Rob Herring <robh+dt at kernel.org>
Cc: Zhen Lei <thunder.leizhen at huawei.com>
Cc: Catalin Marinas <catalin.marinas at arm.com>
Cc: Will Deacon <will at kernel.org>
Cc: Andrew Morton <akpm at linux-foundation.org>
Cc: Mike Rapoport <rppt at kernel.org>
Cc: Geert Uytterhoeven <geert+renesas at glider.be>
Cc: Frank Rowand <frowand.list at gmail.com>
Cc: Ard Biesheuvel <ardb at kernel.org>
Cc: Nick Terrell <terrelln at fb.com>
Cc: linux-arm-kernel at lists.infradead.org
To: devicetree at vger.kernel.org
To: linux-efi at vger.kernel.org


Pingfan Liu (1):
  efi: apply memblock cap after memblock_add()

Zhen Lei (1):
  of: fdt: Aggregate the processing of "linux,usable-memory-range"

 drivers/firmware/efi/efi-init.c |  7 +++++++
 drivers/of/fdt.c                | 18 +++++++++++++-----
 include/linux/of_fdt.h          |  1 +
 3 files changed, 21 insertions(+), 5 deletions(-)

-- 
2.31.1