[PATCH] of: fdt: mark unflattened tree as detached

From: Michal Suchanek
Date: Mon Aug 17 2015 - 02:37:42 EST


The tree returned from of_fdt_unflatten_tree cannot be attached to the
live tree because it is not marked as detached so mark it as such. The
dt resolver checks the flag and refuses to process the tree otherwise.

Signed-off-by: Michal Suchanek <hramrach@xxxxxxxxx>
---
drivers/of/fdt.c | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
index 0749656..32523e6 100644
--- a/drivers/of/fdt.c
+++ b/drivers/of/fdt.c
@@ -383,7 +383,8 @@ static void * unflatten_dt_node(const void *blob,
*/
static void __unflatten_device_tree(const void *blob,
struct device_node **mynodes,
- void * (*dt_alloc)(u64 size, u64 align))
+ void * (*dt_alloc)(u64 size, u64 align),
+ bool detached)
{
unsigned long size;
int start;
@@ -427,6 +428,10 @@ static void __unflatten_device_tree(const void *blob,
if (be32_to_cpup(mem + size) != 0xdeadbeef)
pr_warning("End of tree marker overwritten: %08x\n",
be32_to_cpup(mem + size));
+ if (detached) {
+ of_node_set_flag(*mynodes, OF_DETACHED);
+ pr_debug("unflattened tree is detached\n");
+ }

pr_debug(" <- unflatten_device_tree()\n");
}
@@ -447,7 +452,7 @@ static void *kernel_tree_alloc(u64 size, u64 align)
void of_fdt_unflatten_tree(const unsigned long *blob,
struct device_node **mynodes)
{
- __unflatten_device_tree(blob, mynodes, &kernel_tree_alloc);
+ __unflatten_device_tree(blob, mynodes, &kernel_tree_alloc, true);
}
EXPORT_SYMBOL_GPL(of_fdt_unflatten_tree);

@@ -1099,7 +1104,8 @@ bool __init early_init_dt_scan(void *params)
void __init unflatten_device_tree(void)
{
__unflatten_device_tree(initial_boot_params, &of_root,
- early_init_dt_alloc_memory_arch);
+ early_init_dt_alloc_memory_arch,
+ false);

/* Get pointer to "/chosen" and "/aliases" nodes for use everywhere */
of_alias_scan(early_init_dt_alloc_memory_arch);
--
2.1.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/