esp-idf/tools/unit-test-app/disabled_configs/psram_s2

TEST_EXCLUDE_COMPONENTS=libsodium bt app_update driver spi_flash
CONFIG_SPIRAM=y
CONFIG_IDF_TARGET="esp32s2"
CONFIG_SPIRAM_OCCUPY_NO_HOST=y
esp_hw_support: move test to pytest 2022-10-25 04:20:44 -04:00			`TEST_EXCLUDE_COMPONENTS=libsodium bt app_update driver spi_flash`
kconfig: move remaining kconfig options out of target component The kconfig options are moved to the component where they are used, mostly esp_hw_support and esp_system. 2022-05-10 00:27:36 -04:00			`CONFIG_SPIRAM=y`
global: rename esp32s2beta to esp32s2 2020-01-16 22:47:08 -05:00			`CONFIG_IDF_TARGET="esp32s2"`
ci: fix one ut issue when using Wrover-B module with newer ver of PSRAM The workaround for PSRAM that will occupy an SPI bus is enabled only when: 1. used on 32MBit ver 0 PSRAM. 2. work at 80MHz. The test used to only check 32MBit by the config option, but for PSRAM on Wrover-B module seems to use a newer version of 32MBit PSRAM. So it expects the workaround to be enabled, but actually not. This commit split the unit test into two parts: 1. check all SPI buses are available, for all configs except psram_hspi and psram_vspi, run on regular runners (including Wrover and Wrover-B). a hidden option is enabled so that the compiler knows it's not building psram_hspi or psram_vspi. 2. check the specified bus are acquired, for config psram_hspi and psram_vspi. This only run on special runner (legacy Wrover module). 2019-10-31 00:00:46 -04:00			`CONFIG_SPIRAM_OCCUPY_NO_HOST=y`