diff options
author | Wesley W. Terpstra <wesley@sifive.com> | 2018-06-21 15:37:37 +0200 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-07-07 17:54:29 +0200 |
commit | 319b11ef5719a2f0ae65ce5f665f263a5e7a06c3 (patch) | |
tree | 2d1f721fc2c73cb27526fc56f0d9fb4e17589daa /drivers/base | |
parent | ea614629c69c2c0258ef6414b017c998e3cc61a7 (diff) | |
download | linux-stable-319b11ef5719a2f0ae65ce5f665f263a5e7a06c3.tar.gz linux-stable-319b11ef5719a2f0ae65ce5f665f263a5e7a06c3.tar.bz2 linux-stable-319b11ef5719a2f0ae65ce5f665f263a5e7a06c3.zip |
base: fix order of OF initialization
This fixes: [ 0.010000] cpu cpu0: Error -2 creating of_node link
... which you get for every CPU on all architectures that use
CONFIG_GENERIC_CPU_DEVICES.
In that case, driver_init() calls cpu_dev_init() before calling
of_core_init(). Then we get the callchain:
cpu_dev_init()
-> cpu_dev_register_generic()
-> register_cpu(cpu, i)
-> device_register(&cpu->dev)
-> device_add(dev)
-> device_add_class_symlinks(dev)
... in device_add_class_symlinks, we we dev->of_node, and call
sysfs_create_link(), which fails because we haven't called
of_core_init() to register the sysfs devicetree directory yet.
Signed-off-by: Wesley W. Terpstra <wesley@sifive.com>
[hch: updated the changelog based on review feedback]
Signed-off-by: Christoph Hellwig <hch@lst.de>
Acked-by: Mark Rutland <mark.rutland@arm.com>
Acked-by: Frank Rowand <frowand.list@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/base')
-rw-r--r-- | drivers/base/init.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/base/init.c b/drivers/base/init.c index dd85b05a6a16..908e6520e804 100644 --- a/drivers/base/init.c +++ b/drivers/base/init.c @@ -30,9 +30,9 @@ void __init driver_init(void) /* These are also core pieces, but must come after the * core core pieces. */ + of_core_init(); platform_bus_init(); cpu_dev_init(); memory_dev_init(); container_dev_init(); - of_core_init(); } |