diff options
| author |   Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com> | 2018-12-13 11:17:31 +0530 |
|---|---|---|
| committer |   Michael Ellerman <mpe@ellerman.id.au> | 2018-12-21 11:32:49 +1100 |
| commit | 08fb726df13778a54592aaa1deea6a154637c868 (patch) | |
| tree | 97bd41545866508119afff9ec6a1b82390ce2593 /arch/powerpc/platforms/powernv/opal.c | |
| parent | powerpc/4xx: Delete an unnecessary return statement in two functions (diff) | |
| download | linux-dev-08fb726df13778a54592aaa1deea6a154637c868.tar.xz linux-dev-08fb726df13778a54592aaa1deea6a154637c868.zip | |
powerpc/powernv: Move opal_power_control_init() call in opal_init().
opal_power_control_init() depends on opal message notifier to be
initialized, which is done in opal_init()->opal_message_init(). But both
these initialization are called through machine initcalls and it all
depends on in which order they being called. So far these are called in
correct order (may be we got lucky) and never saw any issue. But it is
clearer to control initialization order explicitly by moving
opal_power_control_init() into opal_init().
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'arch/powerpc/platforms/powernv/opal.c')
| -rw-r--r-- | arch/powerpc/platforms/powernv/opal.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/arch/powerpc/platforms/powernv/opal.c b/arch/powerpc/platforms/powernv/opal.c index beed86f4224b..f6dfc0534969 100644 --- a/arch/powerpc/platforms/powernv/opal.c +++ b/arch/powerpc/platforms/powernv/opal.c @@ -960,6 +960,9 @@ static int __init opal_init(void) /* Initialise OPAL sensor groups */ opal_sensor_groups_init(); + /* Initialise OPAL Power control interface */ + opal_power_control_init(); + return 0; } machine_subsys_initcall(powernv, opal_init); |