esp-idf/components/esp_hw_support
Armando 16a91399f1 psram: put opiram_psram and spiram_psram in internal ram
External memory is accessed via SPI0. When modifying the SPI0 registers,
should put the code in internal RAM. Otherwise when there is an ongoing
SPI0 transaction, CPU changes the SPI0 registers. This is dangerous.
Besides, modifying SPI0 registers may lead external memory to an
unstable state. Therefore putting these code in internal RAM is
necessary.
2021-10-08 17:39:41 +08:00
..
include Merge branch 'feature/ledc_use_rtc8m_or_xtal_lightsleep' into 'master' 2021-09-27 04:02:29 +00:00
port psram: put opiram_psram and spiram_psram in internal ram 2021-10-08 17:39:41 +08:00
test adc: support adc efuse-based calibration on esp32s3 2021-09-14 11:42:50 +08:00
CMakeLists.txt light sleep: separate sleep retention function 2021-08-24 11:54:47 +08:00
Kconfig light sleep: fix Flash leakage when its CS pin has no hardware pullup 2021-09-15 20:34:18 +08:00
Kconfig.spiram.common Adjust the variable name & 2021-08-25 16:06:28 +08:00
Makefile.projbuild
README.md
clk_ctrl_os.c esp32h2: add rtc clock support 2021-08-26 11:25:39 +08:00
compare_set.c
component.mk light sleep: separate sleep retention function 2021-08-24 11:54:47 +08:00
cpu_util.c
esp_async_memcpy.c
esp_clk.c
hw_random.c
intr_alloc.c
linker.lf psram: put opiram_psram and spiram_psram in internal ram 2021-10-08 17:39:41 +08:00
mac_addr.c
project_include.cmake
regi2c_ctrl.c
sdkconfig.rename
sleep_gpio.c light sleep: fix Flash leakage when its CS pin has no hardware pullup 2021-09-15 20:34:18 +08:00
sleep_mac_bb.c light sleep: separate sleep wifi/bt mac bb function 2021-08-23 10:25:04 +08:00
sleep_modes.c Power Management: add XTAL power domain to control whether external 40MHz xtal is powered down during sleep 2021-09-16 14:43:43 +08:00
sleep_retention.c light sleep: add i/d-cache tagmem retention support for esp32s3 2021-08-27 11:11:09 +08:00

README.md

esp_hw_support

This component contains hardware-related operations for supporting the system. These operations are one level above that of hal in that these(1) use system services such as memory allocation, logging, scheduling or (2) may be multi-step operations involving/affecting multiple parts of the SoC.

Implementations that don't fit other components cleanly, but are not worth creating a new component for (yet) may also be placed here as long as they don't pull dependencies other than the core system components.