[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210115114544.1830068-2-qperret@google.com>
Date: Fri, 15 Jan 2021 11:45:43 +0000
From: Quentin Perret <qperret@...gle.com>
To: robh+dt@...nel.org, frowand.list@...il.com
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
drinkcat@...omium.org, swboyd@...omium.org, f.fainelli@...il.com,
karahmed@...zon.de, kernel-team@...roid.com
Subject: [PATCH 1/2] fdt: Properly handle "no-map" field in the memory region
From: KarimAllah Ahmed <karahmed@...zon.de>
Mark the memory region with NOMAP flag instead of completely removing it
from the memory blocks. That makes the FDT handling consistent with the EFI
memory map handling.
Cc: Rob Herring <robh+dt@...nel.org>
Cc: Frank Rowand <frowand.list@...il.com>
Cc: devicetree@...r.kernel.org
Cc: linux-kernel@...r.kernel.org
Signed-off-by: KarimAllah Ahmed <karahmed@...zon.de>
Signed-off-by: Quentin Perret <qperret@...gle.com>
---
drivers/of/fdt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
index feb0f2d67fc5..427b534d60d2 100644
--- a/drivers/of/fdt.c
+++ b/drivers/of/fdt.c
@@ -1147,7 +1147,7 @@ int __init __weak early_init_dt_reserve_memory_arch(phys_addr_t base,
phys_addr_t size, bool nomap)
{
if (nomap)
- return memblock_remove(base, size);
+ return memblock_mark_nomap(base, size);
return memblock_reserve(base, size);
}
--
2.30.0.284.gd98b1dd5eaa7-goog
Powered by blists - more mailing lists