zephyr/drivers/serial/Kconfig.esp32

# SPDX-License-Identifier: Apache-2.0


DT_COMPAT_ESP32_UART := espressif,esp32-uart

config UART_ESP32
	bool "ESP32 UART driver"
	default $(dt_compat_enabled,$(DT_COMPAT_ESP32_UART))
	select SERIAL_HAS_DRIVER
	select SERIAL_SUPPORT_INTERRUPT
	select GPIO_ESP32
	depends on SOC_ESP32 || SOC_ESP32S2 || SOC_ESP32C3
	help
	  Enable the ESP32 UART.
license: cleanup: add SPDX Apache-2.0 license identifier Update the files which contain no license information with the 'Apache-2.0' SPDX license identifier. Many source files in the tree are missing licensing information, which makes it harder for compliance tools to determine the correct license. By default all files without license information are under the default license of Zephyr, which is Apache version 2. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2019-04-06 15:08:09 +02:00			`# SPDX-License-Identifier: Apache-2.0`

drivers: serial: esp32: Unify serial driver for esp32 & esp32s2 1) Allow use of interrup driven instance. ROM implementation could be selected via dts compatiable. 2) Use UART rx fifo and timeout interrupt for end of message detection. Added to decrease interrupts count on data reception 3) Use ESP_LL api. Signed-off-by: Pavlo Hamov <p.hamov@venstar.com> 2021-10-12 16:10:05 +02:00
			`DT_COMPAT_ESP32_UART := espressif,esp32-uart`

kconfig: Turn pointless/confusing 'menuconfig's into 'config's Defining a symbol with 'menuconfig' just tells the menuconfig to display any dependent symbols that immediately follow it in a separate menu. 'menuconfig' has no effect on symbol values. Making a symbol that doesn't have any dependent symbols after it a 'menuconfig' should be avoided, because then you end up with an empty menu, which is shown as e.g. [] Enable foo --- This is how it would be shown if there were children but they all happened to be invisible as well. With a regular 'config', it turns into [] Enable foo Change all pointless 'menuconfig's to 'config's. See the section on 'menuconfig' on the Kconfig - Tips and Best Practices page as well. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no> 2019-10-22 01:04:04 +02:00			`config UART_ESP32`
drivers: esp32: Add minimal UART driver based on ROM routines This is a minimal driver enabling console output during the port bringup. While the driver works, only one of the three UART devices are supported, and there isn't any way to change any parameters or use interrupts. This will most likely be superceded by a proper driver after the port has matured. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com> 2017-05-11 02:12:12 +02:00			`bool "ESP32 UART driver"`
drivers: serial: esp32: Unify serial driver for esp32 & esp32s2 1) Allow use of interrup driven instance. ROM implementation could be selected via dts compatiable. 2) Use UART rx fifo and timeout interrupt for end of message detection. Added to decrease interrupts count on data reception 3) Use ESP_LL api. Signed-off-by: Pavlo Hamov <p.hamov@venstar.com> 2021-10-12 16:10:05 +02:00			`default $(dt_compat_enabled,$(DT_COMPAT_ESP32_UART))`
drivers: esp32: Add minimal UART driver based on ROM routines This is a minimal driver enabling console output during the port bringup. While the driver works, only one of the three UART devices are supported, and there isn't any way to change any parameters or use interrupts. This will most likely be superceded by a proper driver after the port has matured. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com> 2017-05-11 02:12:12 +02:00			`select SERIAL_HAS_DRIVER`
drivers: esp32: Add UART Driver with FIFO/Interrupt support - Fixes #3981 - Implement UART Polling functions - Implement UART Interrupt APIs - Remove dependency on esp32_rom_uart_xxx functions - Update Device tree with UART addresses and pin config - Update ESP32 UART KConfig Notes about implementation: - Interrupts now defined as a local macros, and should be removed later on, when interrupts for esp32 are supported in dts - Threshold interrupts are used for TX/RX - Reseting FIFOs using _RST bit will corrupt FIFO of UART2 when used for UART1 and vice-versa, so a generic way is used for all three UARTs - Old Silicon rev is not supported Signed-off-by: Mohamed ElShahawi <ExtremeGTX@hotmail.com> 2019-08-21 23:54:00 +02:00			`select SERIAL_SUPPORT_INTERRUPT`
			`select GPIO_ESP32`
drivers: serial: add support for esp32c3 into esp32_serial unified driver Signed-off-by: Felipe Neves <felipe.neves@espressif.com> 2021-10-18 22:19:25 +02:00			`depends on SOC_ESP32 \|\| SOC_ESP32S2 \|\| SOC_ESP32C3`
drivers: esp32: Add minimal UART driver based on ROM routines This is a minimal driver enabling console output during the port bringup. While the driver works, only one of the three UART devices are supported, and there isn't any way to change any parameters or use interrupts. This will most likely be superceded by a proper driver after the port has matured. Signed-off-by: Leandro Pereira <leandro.pereira@intel.com> 2017-05-11 02:12:12 +02:00			`help`
drivers: esp32: uart: use hal functions In order to have Espressif SoCs working with the same uart drivers, all low level functions are now replaced to hal_espressif HAL calls. This also changes pinmux, gpio and uart init order to meet its dependencies. Signed-off-by: Sylvio Alves <sylvio.alves@espressif.com> 2021-10-28 06:16:33 +02:00			`Enable the ESP32 UART.`