esp-idf/tools/mocks
fl0wl0w 90d1dcfd76 feat(freertos): Introduced new Kconfig option CONFIG_FREERTOS_NUMBER_OF_CORES
This commit replaces the use of portNUM_PROCESSORS and configNUM_CORES
macros in all of ESP-IDF. These macros are needed to realize an SMP
scenario by fetching the number of active cores FreeRTOS is running on.
Instead, a new Kconfig option, CONFIG_FREERTOS_NUMBER_OF_CORES, has been
added as a proxy for the FreeRTOS config option, configNUMBER_OF_CORES.
This new commit is now used to realize an SMP scenario in various places
in ESP-IDF.

[Sudeep Mohanty: Added new Kconfig option CONFIG_FREERTOS_NUMBER_OF_CORES]

Signed-off-by: Sudeep Mohanty <sudeep.mohanty@espressif.com>
2024-02-09 09:11:28 +01:00
..
driver refactor(usb_serial_jtag): make usb_serial_jtag as component 2024-01-05 19:42:04 +08:00
esp-tls
esp_event feat(linux): added esp_wifi mocking support 2023-07-10 19:40:09 +08:00
esp_hw_support
esp_netif fix(linux): Fixed esp_wifi mock build test 2024-01-23 09:39:03 +08:00
esp_partition
esp_timer
esp_wifi feat(wifi): Sync public header files between ESP-IDF and Wi-Fi driver 2024-02-01 12:17:43 +01:00
freertos feat(freertos): Introduced new Kconfig option CONFIG_FREERTOS_NUMBER_OF_CORES 2024-02-09 09:11:28 +01:00
http_parser
lwip
spi_flash
startup
tcp_transport feat(http_client): Add support for TLS session tickets 2023-11-29 20:48:35 +01:00
README.md

README.md

Mocked Components

All components in this directory mock their respective originals in the component directory. The components in this directory are for testing only. Currently, the main goal is to implement Linux-based host tests with these mocking components. Target-based tests using the mocking components are not possible now but may be possible in the future.

Some components only consist of header files without any CMakeLists.txt file. The headers in these are currently needed by other mocking components to satisfy a minimal set of definitions from dependencies. They are not a full mock implementation. These components with header files only may be replaced by an actual mock implementation of the corresponding component in the future.