mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-12-14 15:23:07 +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:7fe32b3442("event: Convert arch_cpu_init_dm() to use events") Fixes:42fdcebf85("event: Convert misc_init_f() to use events") Fixes:c5ef202557("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>
71 lines
1.5 KiB
Text
71 lines
1.5 KiB
Text
# SPDX-License-Identifier: GPL-2.0
|
|
#
|
|
# From Coreboot src/northbridge/intel/sandybridge/Kconfig
|
|
#
|
|
# Copyright (C) 2010 Google Inc.
|
|
#
|
|
|
|
config NORTHBRIDGE_INTEL_IVYBRIDGE
|
|
bool
|
|
select CACHE_MRC_BIN if HAVE_MRC
|
|
select DM_EVENT
|
|
imply HAVE_INTEL_ME
|
|
imply ENABLE_MRC_CACHE
|
|
imply AHCI_PCI
|
|
imply ICH_SPI
|
|
imply INTEL_ICH6_GPIO
|
|
imply PINCTRL_ICH6
|
|
imply SCSI
|
|
imply SCSI_AHCI
|
|
imply SPI_FLASH
|
|
imply USB
|
|
imply USB_EHCI_HCD
|
|
imply USB_XHCI_HCD
|
|
imply VIDEO_VESA
|
|
imply SOUND_IVYBRIDGE
|
|
|
|
if NORTHBRIDGE_INTEL_IVYBRIDGE
|
|
|
|
config DCACHE_RAM_BASE
|
|
default 0xff7e0000
|
|
|
|
config DCACHE_RAM_SIZE
|
|
default 0x20000
|
|
|
|
config DCACHE_RAM_MRC_VAR_SIZE
|
|
default 0x4000
|
|
|
|
config CPU_SPECIFIC_OPTIONS
|
|
def_bool y
|
|
select SMM_TSEG
|
|
select X86_RAMTEST
|
|
|
|
config SMM_TSEG_SIZE
|
|
hex
|
|
default 0x800000
|
|
|
|
config ENABLE_VMX
|
|
bool "Enable VMX for virtualization"
|
|
help
|
|
Virtual Machine Extensions are provided in many x86 CPUs. These
|
|
provide various facilities for allowing a host OS to provide an
|
|
environment where potentially several guest OSes have only
|
|
limited access to the underlying hardware. This is achieved
|
|
without resorting to software trapping and/or instruction set
|
|
emulation (which would be very slow).
|
|
|
|
Intel's implementation of this is called VT-x. This option enables
|
|
VT-x this so that the OS that is booted by U-Boot can make use of
|
|
these facilities. If this option is not enabled, then the host OS
|
|
will be unable to support virtualisation, or it will run very
|
|
slowly.
|
|
|
|
config FSP_ADDR
|
|
hex
|
|
default 0xfff80000
|
|
|
|
config FSP_BROKEN_HOB
|
|
bool
|
|
default y
|
|
|
|
endif
|