mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-11-24 21:54:01 +00:00
448e2b6327
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: |
||
---|---|---|
.. | ||
android_ab.c | ||
boot_fit.c | ||
bootdev-uclass.c | ||
bootflow.c | ||
bootflow_internal.h | ||
bootflow_menu.c | ||
bootm.c | ||
bootm_os.c | ||
bootmeth-uclass.c | ||
bootmeth_distro.c | ||
bootmeth_efi.c | ||
bootmeth_efi_mgr.c | ||
bootmeth_pxe.c | ||
bootmeth_sandbox.c | ||
bootmeth_script.c | ||
bootretry.c | ||
bootstd-uclass.c | ||
common_fit.c | ||
expo.c | ||
fdt_region.c | ||
image-android-dt.c | ||
image-android.c | ||
image-board.c | ||
image-cipher.c | ||
image-fdt.c | ||
image-fit-sig.c | ||
image-fit.c | ||
image-host.c | ||
image-pre-load.c | ||
image-sig.c | ||
image.c | ||
Kconfig | ||
Makefile | ||
pxe_utils.c | ||
scene.c | ||
scene_internal.h | ||
scene_menu.c | ||
vbe.c | ||
vbe_request.c | ||
vbe_simple.c | ||
vbe_simple.h | ||
vbe_simple_fw.c | ||
vbe_simple_os.c |