2022-10-21 00:22:39 +00:00
|
|
|
CONFIG_TEXT_BASE=0
|
nand: Add sandbox driver
Add a sandbox NAND flash driver to facilitate testing. This driver supports
any number of devices, each using a single chip-select. The OOB data is
stored in-band, with the separation enforced through the API.
For now, create two devices to test with. The first is a very small device
with basic ECC. The second is an 8G device (chosen to be larger than 32
bits). It uses ONFI, with the values copied from the datasheet. It also
doesn't need too strong ECC, which speeds things up.
Although the nand subsystem determines the parameters of a chip based on
the ID, the driver itself requires devicetree properties for each
parameter. We do not derive parameters from the ID because parsing the ID
is non-trivial. We do not just use the parameters that the nand subsystem
has calculated since that is something we should be testing. An exception
is made for the ECC layout, since that is difficult to encode in the device
tree and is not a property of the device itself.
Despite using file I/O to access the backing data, we do not support using
external files. In my experience, these are unnecessary for testing since
tests can generally be written to write their expected data beforehand.
Additionally, we would need to store the "programmed" information somewhere
(complicating the format and the programming process) or try to detect
whether block are erased at runtime (degrading probe speeds).
Information about whether each page has been programmed is stored in an
in-memory buffer. To simplify the implementation, we only support a single
program per erase. While this is accurate for many larger flashes, some
smaller flashes (512 byte) support multiple programs and/or subpage
programs. Support for this could be added later as I believe some
filesystems expect this.
To test ECC, we support error-injection. Surprisingly, only ECC bytes in
the OOB area are protected, even though all bytes are equally susceptible
to error. Because of this, we take care to only corrupt ECC bytes.
Similarly, because ECC covers "steps" and not the whole page, we must take
care to corrupt data in the same way.
Signed-off-by: Sean Anderson <seanga2@gmail.com>
2023-11-04 20:37:52 +00:00
|
|
|
CONFIG_SYS_MALLOC_LEN=0x6000000
|
2019-04-29 19:54:04 +00:00
|
|
|
CONFIG_NR_DRAM_BANKS=1
|
2020-08-10 19:31:07 +00:00
|
|
|
CONFIG_ENV_SIZE=0x2000
|
2021-06-28 14:17:29 +00:00
|
|
|
CONFIG_DEFAULT_DEVICE_TREE="sandbox64"
|
2023-02-17 14:58:06 +00:00
|
|
|
CONFIG_DM_RESET=y
|
2019-09-23 15:47:37 +00:00
|
|
|
CONFIG_PRE_CON_BUF_ADDR=0x100000
|
2022-04-08 17:36:51 +00:00
|
|
|
CONFIG_SYS_LOAD_ADDR=0x0
|
2023-05-01 15:50:26 +00:00
|
|
|
CONFIG_PCI=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_SANDBOX64=y
|
2020-11-27 10:49:29 +00:00
|
|
|
CONFIG_DEBUG_UART=y
|
2022-04-01 14:33:18 +00:00
|
|
|
CONFIG_SYS_MEMTEST_START=0x00100000
|
|
|
|
|
CONFIG_SYS_MEMTEST_END=0x00101000
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_FIT=y
|
|
|
|
|
CONFIG_FIT_SIGNATURE=y
|
|
|
|
|
CONFIG_FIT_VERBOSE=y
|
2023-08-23 00:17:12 +00:00
|
|
|
CONFIG_LEGACY_IMAGE_FORMAT=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_BOOTSTAGE=y
|
|
|
|
|
CONFIG_BOOTSTAGE_REPORT=y
|
|
|
|
|
CONFIG_BOOTSTAGE_FDT=y
|
|
|
|
|
CONFIG_BOOTSTAGE_STASH=y
|
|
|
|
|
CONFIG_BOOTSTAGE_STASH_SIZE=0x4096
|
|
|
|
|
CONFIG_CONSOLE_RECORD=y
|
2023-08-13 01:17:54 +00:00
|
|
|
CONFIG_CONSOLE_RECORD_OUT_SIZE=0x6000
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_PRE_CONSOLE_BUFFER=y
|
2018-03-28 12:38:17 +00:00
|
|
|
CONFIG_DISPLAY_BOARDINFO_LATE=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_CMD_CPU=y
|
|
|
|
|
CONFIG_CMD_LICENSE=y
|
|
|
|
|
CONFIG_CMD_BOOTZ=y
|
2020-03-14 11:27:02 +00:00
|
|
|
CONFIG_CMD_BOOTEFI_HELLO=y
|
2018-02-12 07:05:57 +00:00
|
|
|
# CONFIG_CMD_ELF is not set
|
|
|
|
|
CONFIG_CMD_ASKENV=y
|
|
|
|
|
CONFIG_CMD_GREPENV=y
|
2020-07-28 09:51:27 +00:00
|
|
|
CONFIG_CMD_ERASEENV=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_CMD_ENV_CALLBACK=y
|
|
|
|
|
CONFIG_CMD_ENV_FLAGS=y
|
2020-04-14 02:51:52 +00:00
|
|
|
CONFIG_CMD_NVEDIT_EFI=y
|
2020-06-19 12:03:36 +00:00
|
|
|
CONFIG_CMD_NVEDIT_INFO=y
|
2020-07-28 09:51:23 +00:00
|
|
|
CONFIG_CMD_NVEDIT_LOAD=y
|
|
|
|
|
CONFIG_CMD_NVEDIT_SELECT=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_LOOPW=y
|
|
|
|
|
CONFIG_CMD_MD5SUM=y
|
|
|
|
|
CONFIG_CMD_MEMINFO=y
|
|
|
|
|
CONFIG_CMD_MX_CYCLIC=y
|
2020-02-28 18:28:38 +00:00
|
|
|
CONFIG_CMD_MEMTEST=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_CMD_DEMO=y
|
|
|
|
|
CONFIG_CMD_GPIO=y
|
|
|
|
|
CONFIG_CMD_GPT=y
|
|
|
|
|
CONFIG_CMD_GPT_RENAME=y
|
|
|
|
|
CONFIG_CMD_IDE=y
|
|
|
|
|
CONFIG_CMD_I2C=y
|
2022-05-11 09:55:40 +00:00
|
|
|
CONFIG_CMD_LOADM=y
|
nand: Add sandbox driver
Add a sandbox NAND flash driver to facilitate testing. This driver supports
any number of devices, each using a single chip-select. The OOB data is
stored in-band, with the separation enforced through the API.
For now, create two devices to test with. The first is a very small device
with basic ECC. The second is an 8G device (chosen to be larger than 32
bits). It uses ONFI, with the values copied from the datasheet. It also
doesn't need too strong ECC, which speeds things up.
Although the nand subsystem determines the parameters of a chip based on
the ID, the driver itself requires devicetree properties for each
parameter. We do not derive parameters from the ID because parsing the ID
is non-trivial. We do not just use the parameters that the nand subsystem
has calculated since that is something we should be testing. An exception
is made for the ECC layout, since that is difficult to encode in the device
tree and is not a property of the device itself.
Despite using file I/O to access the backing data, we do not support using
external files. In my experience, these are unnecessary for testing since
tests can generally be written to write their expected data beforehand.
Additionally, we would need to store the "programmed" information somewhere
(complicating the format and the programming process) or try to detect
whether block are erased at runtime (degrading probe speeds).
Information about whether each page has been programmed is stored in an
in-memory buffer. To simplify the implementation, we only support a single
program per erase. While this is accurate for many larger flashes, some
smaller flashes (512 byte) support multiple programs and/or subpage
programs. Support for this could be added later as I believe some
filesystems expect this.
To test ECC, we support error-injection. Surprisingly, only ECC bytes in
the OOB area are protected, even though all bytes are equally susceptible
to error. Because of this, we take care to only corrupt ECC bytes.
Similarly, because ECC covers "steps" and not the whole page, we must take
care to corrupt data in the same way.
Signed-off-by: Sean Anderson <seanga2@gmail.com>
2023-11-04 20:37:52 +00:00
|
|
|
CONFIG_CMD_MTD=y
|
2018-09-27 07:19:31 +00:00
|
|
|
CONFIG_CMD_OSD=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_CMD_PCI=y
|
|
|
|
|
CONFIG_CMD_READ=y
|
|
|
|
|
CONFIG_CMD_REMOTEPROC=y
|
|
|
|
|
CONFIG_CMD_SPI=y
|
2022-10-18 08:47:25 +00:00
|
|
|
CONFIG_CMD_TEMPERATURE=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_CMD_USB=y
|
2023-10-18 14:02:32 +00:00
|
|
|
CONFIG_CMD_RKMTD=y
|
sandbox: add SIGALRM-based watchdog device
In order to test that U-Boot actually maintains the watchdog device(s)
during long-running busy-loops, such as those where we wait for the
user to stop autoboot, we need a watchdog device that actually does
something during those loops; we cannot test that behaviour via the DM
test framework.
So introduce a relatively simple watchdog device which is simply based
on calling the host OS' alarm() function; that has the nice property
that a new call to alarm() simply sets a new deadline, and alarm(0)
cancels any existing alarm. These properties are precisely what we
need to implement start/reset/stop. We install our own handler so that
we get a known message printed if and when the watchdog fires, and by
just invoking that handler directly, we get expire_now for free.
The actual calls to the various OS functions (alarm, signal, raise)
need to be done in os.c, and since the driver code cannot get access
to the values of SIGALRM or SIG_DFL (that would require including a
host header, and that's only os.c which can do that), we cannot simply
do trivial wrappers for signal() and raise(), but instead create
specialized functions just for use by this driver.
Apart from enabling this driver for sandbox{,64}_defconfig, also
enable the wdt command which was useful for hand-testing this new
driver (especially with running u-boot under strace).
Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
2022-09-27 09:54:04 +00:00
|
|
|
CONFIG_CMD_WDT=y
|
2023-03-02 08:12:24 +00:00
|
|
|
CONFIG_CMD_WRITE=y
|
2022-11-07 16:58:57 +00:00
|
|
|
CONFIG_CMD_CAT=y
|
2023-10-02 17:58:20 +00:00
|
|
|
CONFIG_CMD_XXD=y
|
2020-06-16 23:06:17 +00:00
|
|
|
CONFIG_BOOTP_DNS2=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_CMD_TFTPPUT=y
|
|
|
|
|
CONFIG_CMD_TFTPSRV=y
|
|
|
|
|
CONFIG_CMD_RARP=y
|
|
|
|
|
CONFIG_CMD_CDP=y
|
|
|
|
|
CONFIG_CMD_SNTP=y
|
|
|
|
|
CONFIG_CMD_DNS=y
|
|
|
|
|
CONFIG_CMD_LINK_LOCAL=y
|
2023-04-22 00:08:22 +00:00
|
|
|
CONFIG_IPV6_ROUTER_DISCOVERY=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_CMD_ETHSW=y
|
|
|
|
|
CONFIG_CMD_BMP=y
|
2020-03-14 11:27:02 +00:00
|
|
|
CONFIG_CMD_EFIDEBUG=y
|
2020-07-06 20:01:19 +00:00
|
|
|
CONFIG_CMD_RTC=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_CMD_TIME=y
|
2022-08-18 19:44:04 +00:00
|
|
|
CONFIG_CMD_PAUSE=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_CMD_TIMER=y
|
|
|
|
|
CONFIG_CMD_SOUND=y
|
|
|
|
|
CONFIG_CMD_QFW=y
|
2020-10-29 14:48:01 +00:00
|
|
|
CONFIG_CMD_PSTORE=y
|
|
|
|
|
CONFIG_CMD_PSTORE_MEM_ADDR=0x3000000
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_CMD_BOOTSTAGE=y
|
|
|
|
|
CONFIG_CMD_PMIC=y
|
|
|
|
|
CONFIG_CMD_REGULATOR=y
|
2019-09-24 09:32:28 +00:00
|
|
|
CONFIG_CMD_AES=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_CMD_TPM=y
|
|
|
|
|
CONFIG_CMD_TPM_TEST=y
|
|
|
|
|
CONFIG_CMD_BTRFS=y
|
|
|
|
|
CONFIG_CMD_CBFS=y
|
|
|
|
|
CONFIG_CMD_CRAMFS=y
|
|
|
|
|
CONFIG_CMD_EXT4_WRITE=y
|
|
|
|
|
CONFIG_CMD_MTDPARTS=y
|
|
|
|
|
CONFIG_MAC_PARTITION=y
|
|
|
|
|
CONFIG_AMIGA_PARTITION=y
|
|
|
|
|
CONFIG_OF_CONTROL=y
|
|
|
|
|
CONFIG_OF_LIVE=y
|
2020-07-28 09:51:22 +00:00
|
|
|
CONFIG_ENV_IS_NOWHERE=y
|
|
|
|
|
CONFIG_ENV_IS_IN_EXT4=y
|
|
|
|
|
CONFIG_ENV_EXT4_INTERFACE="host"
|
|
|
|
|
CONFIG_ENV_EXT4_DEVICE_AND_PART="0:0"
|
2021-04-21 09:06:55 +00:00
|
|
|
CONFIG_ENV_IMPORT_FDT=y
|
2020-08-10 19:31:07 +00:00
|
|
|
CONFIG_BOOTP_SEND_HOSTNAME=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_NETCONSOLE=y
|
2019-06-11 02:51:14 +00:00
|
|
|
CONFIG_IP_DEFRAG=y
|
2021-12-18 18:27:51 +00:00
|
|
|
CONFIG_BOOTP_SERVERIP=y
|
2022-12-29 18:44:21 +00:00
|
|
|
CONFIG_IPV6=y
|
2021-01-12 12:55:25 +00:00
|
|
|
CONFIG_DM_DMA=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_REGMAP=y
|
|
|
|
|
CONFIG_SYSCON=y
|
|
|
|
|
CONFIG_DEBUG_DEVRES=y
|
|
|
|
|
CONFIG_ADC=y
|
|
|
|
|
CONFIG_ADC_SANDBOX=y
|
2019-12-07 04:41:57 +00:00
|
|
|
CONFIG_AXI=y
|
|
|
|
|
CONFIG_AXI_SANDBOX=y
|
2022-01-22 12:53:24 +00:00
|
|
|
CONFIG_SYS_IDE_MAXBUS=1
|
|
|
|
|
CONFIG_SYS_ATA_BASE_ADDR=0x100
|
|
|
|
|
CONFIG_SYS_ATA_STRIDE=4
|
|
|
|
|
CONFIG_SYS_ATA_DATA_OFFSET=0
|
|
|
|
|
CONFIG_SYS_ATA_REG_OFFSET=1
|
|
|
|
|
CONFIG_SYS_ATA_ALT_OFFSET=2
|
|
|
|
|
CONFIG_SYS_ATA_IDE0_OFFSET=0
|
2020-07-24 16:19:49 +00:00
|
|
|
CONFIG_BUTTON=y
|
2023-08-13 03:05:52 +00:00
|
|
|
CONFIG_BUTTON_ADC=y
|
2020-07-24 16:19:49 +00:00
|
|
|
CONFIG_BUTTON_GPIO=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_CLK=y
|
2023-08-13 19:50:29 +00:00
|
|
|
CONFIG_CLK_COMPOSITE_CCF=y
|
2021-06-11 04:16:17 +00:00
|
|
|
CONFIG_CLK_K210=y
|
|
|
|
|
CONFIG_CLK_K210_SET_RATE=y
|
2023-08-13 19:50:29 +00:00
|
|
|
CONFIG_SANDBOX_CLK_CCF=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_CPU=y
|
|
|
|
|
CONFIG_DM_DEMO=y
|
|
|
|
|
CONFIG_DM_DEMO_SIMPLE=y
|
|
|
|
|
CONFIG_DM_DEMO_SHAPE=y
|
2021-01-29 18:56:04 +00:00
|
|
|
CONFIG_DFU_SF=y
|
2021-02-05 14:38:54 +00:00
|
|
|
CONFIG_FASTBOOT_FLASH=y
|
|
|
|
|
CONFIG_FASTBOOT_FLASH_MMC_DEV=0
|
2023-10-02 14:35:27 +00:00
|
|
|
CONFIG_ARM_FFA_TRANSPORT=y
|
2020-05-22 09:08:58 +00:00
|
|
|
CONFIG_GPIO_HOG=y
|
2020-07-08 08:24:00 +00:00
|
|
|
CONFIG_DM_GPIO_LOOKUP_LABEL=y
|
2022-08-04 14:27:17 +00:00
|
|
|
CONFIG_QCOM_PMIC_GPIO=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_SANDBOX_GPIO=y
|
|
|
|
|
CONFIG_I2C_CROS_EC_TUNNEL=y
|
|
|
|
|
CONFIG_I2C_CROS_EC_LDO=y
|
|
|
|
|
CONFIG_DM_I2C_GPIO=y
|
|
|
|
|
CONFIG_I2C_MUX=y
|
|
|
|
|
CONFIG_I2C_ARB_GPIO_CHALLENGE=y
|
|
|
|
|
CONFIG_CROS_EC_KEYB=y
|
|
|
|
|
CONFIG_I8042_KEYB=y
|
2021-10-23 14:58:02 +00:00
|
|
|
CONFIG_IOMMU=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_LED=y
|
|
|
|
|
CONFIG_LED_BLINK=y
|
|
|
|
|
CONFIG_LED_GPIO=y
|
|
|
|
|
CONFIG_DM_MAILBOX=y
|
|
|
|
|
CONFIG_SANDBOX_MBOX=y
|
|
|
|
|
CONFIG_MISC=y
|
2022-05-05 17:11:40 +00:00
|
|
|
CONFIG_NVMEM=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_CROS_EC=y
|
|
|
|
|
CONFIG_CROS_EC_I2C=y
|
|
|
|
|
CONFIG_CROS_EC_LPC=y
|
|
|
|
|
CONFIG_CROS_EC_SANDBOX=y
|
|
|
|
|
CONFIG_CROS_EC_SPI=y
|
2020-01-22 18:38:00 +00:00
|
|
|
CONFIG_P2SB=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_PWRSEQ=y
|
|
|
|
|
CONFIG_I2C_EEPROM=y
|
|
|
|
|
CONFIG_MMC_SANDBOX=y
|
2019-10-03 17:50:15 +00:00
|
|
|
CONFIG_MTD=y
|
nand: Add sandbox driver
Add a sandbox NAND flash driver to facilitate testing. This driver supports
any number of devices, each using a single chip-select. The OOB data is
stored in-band, with the separation enforced through the API.
For now, create two devices to test with. The first is a very small device
with basic ECC. The second is an 8G device (chosen to be larger than 32
bits). It uses ONFI, with the values copied from the datasheet. It also
doesn't need too strong ECC, which speeds things up.
Although the nand subsystem determines the parameters of a chip based on
the ID, the driver itself requires devicetree properties for each
parameter. We do not derive parameters from the ID because parsing the ID
is non-trivial. We do not just use the parameters that the nand subsystem
has calculated since that is something we should be testing. An exception
is made for the ECC layout, since that is difficult to encode in the device
tree and is not a property of the device itself.
Despite using file I/O to access the backing data, we do not support using
external files. In my experience, these are unnecessary for testing since
tests can generally be written to write their expected data beforehand.
Additionally, we would need to store the "programmed" information somewhere
(complicating the format and the programming process) or try to detect
whether block are erased at runtime (degrading probe speeds).
Information about whether each page has been programmed is stored in an
in-memory buffer. To simplify the implementation, we only support a single
program per erase. While this is accurate for many larger flashes, some
smaller flashes (512 byte) support multiple programs and/or subpage
programs. Support for this could be added later as I believe some
filesystems expect this.
To test ECC, we support error-injection. Surprisingly, only ECC bytes in
the OOB area are protected, even though all bytes are equally susceptible
to error. Because of this, we take care to only corrupt ECC bytes.
Similarly, because ECC covers "steps" and not the whole page, we must take
care to corrupt data in the same way.
Signed-off-by: Sean Anderson <seanga2@gmail.com>
2023-11-04 20:37:52 +00:00
|
|
|
CONFIG_DM_MTD=y
|
|
|
|
|
CONFIG_MTD_RAW_NAND=y
|
|
|
|
|
CONFIG_SYS_MAX_NAND_DEVICE=8
|
|
|
|
|
CONFIG_SYS_NAND_USE_FLASH_BBT=y
|
|
|
|
|
CONFIG_NAND_SANDBOX=y
|
|
|
|
|
CONFIG_SYS_NAND_ONFI_DETECTION=y
|
|
|
|
|
CONFIG_SYS_NAND_PAGE_SIZE=0x200
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_SPI_FLASH_SANDBOX=y
|
2023-08-13 00:15:53 +00:00
|
|
|
CONFIG_BOOTDEV_SPI_FLASH=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_SPI_FLASH_ATMEL=y
|
|
|
|
|
CONFIG_SPI_FLASH_EON=y
|
|
|
|
|
CONFIG_SPI_FLASH_GIGADEVICE=y
|
|
|
|
|
CONFIG_SPI_FLASH_MACRONIX=y
|
|
|
|
|
CONFIG_SPI_FLASH_SPANSION=y
|
|
|
|
|
CONFIG_SPI_FLASH_STMICRO=y
|
|
|
|
|
CONFIG_SPI_FLASH_SST=y
|
|
|
|
|
CONFIG_SPI_FLASH_WINBOND=y
|
2023-05-01 15:50:26 +00:00
|
|
|
CONFIG_NVMXIP_QSPI=y
|
2022-01-22 19:38:11 +00:00
|
|
|
CONFIG_NVME_PCI=y
|
2023-08-13 19:51:50 +00:00
|
|
|
CONFIG_PCI_REGION_MULTI_ENTRY=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_PCI_SANDBOX=y
|
|
|
|
|
CONFIG_PHY=y
|
|
|
|
|
CONFIG_PHY_SANDBOX=y
|
|
|
|
|
CONFIG_PINCTRL=y
|
|
|
|
|
CONFIG_PINCONF=y
|
|
|
|
|
CONFIG_PINCTRL_SANDBOX=y
|
2023-08-13 03:32:09 +00:00
|
|
|
CONFIG_PINCTRL_SINGLE=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_POWER_DOMAIN=y
|
|
|
|
|
CONFIG_SANDBOX_POWER_DOMAIN=y
|
|
|
|
|
CONFIG_DM_PMIC=y
|
|
|
|
|
CONFIG_PMIC_ACT8846=y
|
|
|
|
|
CONFIG_DM_PMIC_PFUZE100=y
|
|
|
|
|
CONFIG_DM_PMIC_MAX77686=y
|
2023-08-13 02:57:01 +00:00
|
|
|
CONFIG_DM_PMIC_MC34708=y
|
2022-08-04 14:27:17 +00:00
|
|
|
CONFIG_PMIC_QCOM=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_PMIC_RK8XX=y
|
|
|
|
|
CONFIG_PMIC_S2MPS11=y
|
|
|
|
|
CONFIG_DM_PMIC_SANDBOX=y
|
|
|
|
|
CONFIG_PMIC_S5M8767=y
|
|
|
|
|
CONFIG_PMIC_TPS65090=y
|
|
|
|
|
CONFIG_DM_REGULATOR=y
|
|
|
|
|
CONFIG_REGULATOR_ACT8846=y
|
|
|
|
|
CONFIG_DM_REGULATOR_PFUZE100=y
|
|
|
|
|
CONFIG_DM_REGULATOR_MAX77686=y
|
|
|
|
|
CONFIG_DM_REGULATOR_FIXED=y
|
|
|
|
|
CONFIG_REGULATOR_RK8XX=y
|
|
|
|
|
CONFIG_REGULATOR_S5M8767=y
|
|
|
|
|
CONFIG_DM_REGULATOR_SANDBOX=y
|
|
|
|
|
CONFIG_REGULATOR_TPS65090=y
|
|
|
|
|
CONFIG_DM_PWM=y
|
2021-05-19 16:33:31 +00:00
|
|
|
CONFIG_PWM_CROS_EC=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_PWM_SANDBOX=y
|
|
|
|
|
CONFIG_RAM=y
|
|
|
|
|
CONFIG_REMOTEPROC_SANDBOX=y
|
|
|
|
|
CONFIG_SANDBOX_RESET=y
|
|
|
|
|
CONFIG_DM_RTC=y
|
2019-05-28 23:29:58 +00:00
|
|
|
CONFIG_RTC_RV8803=y
|
2022-09-21 14:21:44 +00:00
|
|
|
CONFIG_SCSI=y
|
2022-09-21 14:21:46 +00:00
|
|
|
CONFIG_DM_SCSI=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_SANDBOX_SERIAL=y
|
2018-08-08 01:40:14 +00:00
|
|
|
CONFIG_SMEM=y
|
|
|
|
|
CONFIG_SANDBOX_SMEM=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_SOUND=y
|
|
|
|
|
CONFIG_SOUND_SANDBOX=y
|
2020-07-28 12:46:52 +00:00
|
|
|
CONFIG_SOC_DEVICE=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_SANDBOX_SPI=y
|
|
|
|
|
CONFIG_SPMI=y
|
|
|
|
|
CONFIG_SPMI_SANDBOX=y
|
2020-11-05 13:32:05 +00:00
|
|
|
CONFIG_SYSINFO=y
|
|
|
|
|
CONFIG_SYSINFO_SANDBOX=y
|
2021-04-20 14:50:58 +00:00
|
|
|
CONFIG_SYSINFO_GPIO=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_SYSRESET=y
|
2022-10-18 08:47:25 +00:00
|
|
|
CONFIG_DM_THERMAL=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_TIMER=y
|
|
|
|
|
CONFIG_TIMER_EARLY=y
|
|
|
|
|
CONFIG_SANDBOX_TIMER=y
|
|
|
|
|
CONFIG_USB=y
|
2023-09-01 09:49:49 +00:00
|
|
|
CONFIG_DM_USB_GADGET=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_USB_EMUL=y
|
|
|
|
|
CONFIG_USB_KEYBOARD=y
|
2022-10-18 13:46:31 +00:00
|
|
|
CONFIG_VIDEO=y
|
2023-08-13 05:15:06 +00:00
|
|
|
CONFIG_VIDEO_FONT_SUN12X22=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_CONSOLE_ROTATION=y
|
|
|
|
|
CONFIG_CONSOLE_TRUETYPE=y
|
|
|
|
|
CONFIG_CONSOLE_TRUETYPE_CANTORAONE=y
|
2021-11-08 03:59:43 +00:00
|
|
|
CONFIG_I2C_EDID=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_VIDEO_SANDBOX_SDL=y
|
2018-09-27 07:19:31 +00:00
|
|
|
CONFIG_OSD=y
|
|
|
|
|
CONFIG_SANDBOX_OSD=y
|
2023-08-13 05:15:05 +00:00
|
|
|
CONFIG_BMP_16BPP=y
|
|
|
|
|
CONFIG_BMP_24BPP=y
|
2021-08-19 09:57:00 +00:00
|
|
|
# CONFIG_WATCHDOG_AUTOSTART is not set
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_WDT=y
|
2021-08-19 09:57:05 +00:00
|
|
|
CONFIG_WDT_GPIO=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_WDT_SANDBOX=y
|
sandbox: add SIGALRM-based watchdog device
In order to test that U-Boot actually maintains the watchdog device(s)
during long-running busy-loops, such as those where we wait for the
user to stop autoboot, we need a watchdog device that actually does
something during those loops; we cannot test that behaviour via the DM
test framework.
So introduce a relatively simple watchdog device which is simply based
on calling the host OS' alarm() function; that has the nice property
that a new call to alarm() simply sets a new deadline, and alarm(0)
cancels any existing alarm. These properties are precisely what we
need to implement start/reset/stop. We install our own handler so that
we get a known message printed if and when the watchdog fires, and by
just invoking that handler directly, we get expire_now for free.
The actual calls to the various OS functions (alarm, signal, raise)
need to be done in os.c, and since the driver code cannot get access
to the values of SIGALRM or SIG_DFL (that would require including a
host header, and that's only os.c which can do that), we cannot simply
do trivial wrappers for signal() and raise(), but instead create
specialized functions just for use by this driver.
Apart from enabling this driver for sandbox{,64}_defconfig, also
enable the wdt command which was useful for hand-testing this new
driver (especially with running u-boot under strace).
Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
2022-09-27 09:54:04 +00:00
|
|
|
CONFIG_WDT_ALARM_SANDBOX=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_FS_CBFS=y
|
|
|
|
|
CONFIG_FS_CRAMFS=y
|
|
|
|
|
CONFIG_CMD_DHRYSTONE=y
|
|
|
|
|
CONFIG_TPM=y
|
|
|
|
|
CONFIG_LZ4=y
|
|
|
|
|
CONFIG_ERRNO_STR=y
|
2021-01-29 18:56:04 +00:00
|
|
|
CONFIG_EFI_RUNTIME_UPDATE_CAPSULE=y
|
|
|
|
|
CONFIG_EFI_CAPSULE_ON_DISK=y
|
2022-10-21 12:46:05 +00:00
|
|
|
CONFIG_EFI_CAPSULE_FIRMWARE_RAW=y
|
2020-04-14 02:51:52 +00:00
|
|
|
CONFIG_EFI_SECURE_BOOT=y
|
2019-03-21 18:10:08 +00:00
|
|
|
CONFIG_TEST_FDTDEC=y
|
2022-11-07 16:58:57 +00:00
|
|
|
CONFIG_FWU_MULTI_BANK_UPDATE=y
|
2018-02-12 07:05:57 +00:00
|
|
|
CONFIG_UNIT_TEST=y
|
|
|
|
|
CONFIG_UT_TIME=y
|
|
|
|
|
CONFIG_UT_DM=y
|
