Hi Tom, On Sat, Jan 14, 2023 at 5:50 PM Tom Rini <[email protected]> wrote: > > The event framework is just that, a framework. Enabling it by itself > does nothing, so we shouldn't ask the user about it. Reword (and correct > typos) around this the option and help text. This also applies to > DM_EVENT, so reword as well. > > With this, it's time to address the larger problems. When functionality > uses events, typically via EVENT_SPY, the appropriate framework then > must be select'd and NOT imply'd. As the functionality will cease to > work (and so, platforms will fail to boot) this is non-optional and > where select is appropriate. Audit the current users of EVENT_SPY to > have a more fine-grained approach to select'ing the framework where > used. > > Cc: Simon Glass <[email protected]> > Reported-by: Oliver Graute <[email protected]> > Reported-by: Francesco Dolcini <[email protected]> > Fixes: 7fe32b3442f0 ("event: Convert arch_cpu_init_dm() to use events") > Fixes: 42fdcebf859f ("event: Convert misc_init_f() to use events") > Signed-off-by: Tom Rini <[email protected]>
Thanks for investigating and providing a proper fix: Reviewed-by: Fabio Estevam <[email protected]>
