xiaomi-sm8450/android_kernel_xiaomi_sm8450
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

powerpc/powernv: Reorder OPAL subsystem initialisation

Browse Source 
Most of the OPAL subsystems are always compiled in for PowerNV and
many of them need to be initialised before or after other OPAL
subsystems. Rather than trying to control this ordering through
machine initcalls it is clearer and easier to control initialisation
order with explicit calls in opal_init.

Signed-off-by: Alistair Popple <alistair@popple.id.au>
Cc: Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
This commit is contained in:
Alistair Popple
2015-05-15 14:06:36 +10:00
committed by Michael Ellerman
parent 5703d2f4a1
commit 96e023e753
6 changed files with 19 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
arch/powerpc/platforms/powernv/opal-async.c
View File

@@ -151,7 +151,7 @@ static struct notifier_block opal_async_comp_nb = {
.priority = 0,
};
static int __init opal_async_comp_init(void)
int __init opal_async_comp_init(void)
{
struct device_node *opal_node;
const __be32 *async;
@@ -205,4 +205,3 @@ out_opal_node:
out:
return err;
}
machine_subsys_initcall(powernv, opal_async_comp_init);