diff options
| author | Tom Rini <trini@konsulko.com> | 2023-01-16 15:46:49 -0500 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2023-01-18 12:46:13 -0500 |
| commit | 448e2b6327d0498d58506d6f4e4b2a325ab7cca0 (patch) | |
| tree | 2ed6c4e6ba1106d7f68e6a6d3424f76593bb3e2e /drivers/core | |
| parent | e8272cbd59afdc1617e8c0288ebd663fd743d4b5 (diff) | |
| download | u-boot-448e2b6327d0498d58506d6f4e4b2a325ab7cca0.tar.gz u-boot-448e2b6327d0498d58506d6f4e4b2a325ab7cca0.tar.bz2 u-boot-448e2b6327d0498d58506d6f4e4b2a325ab7cca0.zip | |
event: Correct dependencies on the EVENT framework
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 and EVENT_DYNAMIC. Only EVENT_DEBUG and CMD_EVENT should be
visible to the user to select, when EVENT is selected.
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. Also ensure the current users of event_register and also select
EVENT_DYNAMIC.
Cc: AKASHI Takahiro <takahiro.akashi@linaro.org>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>
Reported-by: Oliver Graute <Oliver.Graute@kococonnector.com>
Reported-by: Francesco Dolcini <francesco.dolcini@toradex.com>
Fixes: 7fe32b3442f0 ("event: Convert arch_cpu_init_dm() to use events")
Fixes: 42fdcebf859f ("event: Convert misc_init_f() to use events")
Fixes: c5ef2025579e ("dm: fix DM_EVENT dependencies")
Signed-off-by: Tom Rini <trini@konsulko.com>
Tested-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Fabio Estevam <festevam@denx.de>
Diffstat (limited to 'drivers/core')
| -rw-r--r-- | drivers/core/Kconfig | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/drivers/core/Kconfig b/drivers/core/Kconfig index 8fde77c23e..6fc8854b57 100644 --- a/drivers/core/Kconfig +++ b/drivers/core/Kconfig @@ -109,13 +109,14 @@ config DM_DEVICE_REMOVE causes USB host controllers to not be stopped when booting the OS. config DM_EVENT - bool "Support events with driver model" - depends on DM && EVENT - default y if SANDBOX + bool + depends on DM + select EVENT help This enables support for generating events related to driver model operations, such as prbing or removing a device. Subsystems can - register a 'spy' function that is called when the event occurs. + register a 'spy' function that is called when the event occurs. Such + subsystems must select this option. config SPL_DM_DEVICE_REMOVE bool "Support device removal in SPL" |