The unflattened devicetree structure is available to be used not long after the page tables have been set up on most architectures, and is available even before that on other architectures. Hence, move the call to fdt_init_reserved_mem() to after unflatten_device_tree() is called so that the reserved memory nodes can be accessed using the unflattened device tree APIs. Using the unflattened devicetree APIs is more efficient than using the flattened devicetree APIs. Signed-off-by: Oreoluwa Babatunde <quic_obabatun@xxxxxxxxxxx> --- arch/microblaze/kernel/setup.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/microblaze/kernel/setup.c b/arch/microblaze/kernel/setup.c index 631faa4613ec..d999ad774a44 100644 --- a/arch/microblaze/kernel/setup.c +++ b/arch/microblaze/kernel/setup.c @@ -55,12 +55,12 @@ void __init setup_arch(char **cmdline_p) setup_memory(); - fdt_init_reserved_mem(); - console_verbose(); unflatten_device_tree(); + fdt_init_reserved_mem(); + setup_cpuinfo(); microblaze_cache_init(); -- 2.17.1
