diff options
author | Rasmus Villemoes <[email protected]> | 2020-02-13 12:43:42 +0100 |
---|---|---|
committer | Greg Kroah-Hartman <[email protected]> | 2020-02-13 12:03:26 -0800 |
commit | 4508cf76b1ecdf20a456b6b161acbe78f3b23358 (patch) | |
tree | fbdfcac831b9acfa2911ab9886173893c70ccb9a /tools/perf/util/trace-event-scripting.c | |
parent | 679aac5ead2f18d223554a52b543e1195e181811 (diff) |
serial: cpm_uart: call cpm_muram_init before registering console
Christophe reports that powerpc 8xx silently fails to 5.6-rc1. It turns
out I was wrong about nobody relying on the lazy initialization of the
cpm/qe muram in commit b6231ea2b3c6 (soc: fsl: qe: drop broken lazy
call of cpm_muram_init()).
Rather than reinstating the somewhat dubious lazy call (initializing a
currently held spinlock, and implicitly doing a GFP_KERNEL under that
spinlock), make sure that cpm_muram_init() is called early enough - I
thought the calls from the subsys_initcalls were good enough, but when
used by console drivers, that's obviously not the
case. cpm_muram_init() is safe to call twice (there's an early return
if it is already initialized), so keep the call from cpm_init() - in
case SERIAL_CPM_CONSOLE=n.
Fixes: b6231ea2b3c6 (soc: fsl: qe: drop broken lazy call of cpm_muram_init())
Reported-by: Christophe Leroy <[email protected]>
Signed-off-by: Rasmus Villemoes <[email protected]>
Tested-by: Christophe Leroy <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/util/trace-event-scripting.c')
0 files changed, 0 insertions, 0 deletions