2021-02-09 04:14:29 +08:00
|
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
|
2022-11-15 03:10:59 +08:00
|
|
|
add_subdirectory_ifdef(CONFIG_ARM_ETHOS_U ethos_u)
|
2021-02-09 04:14:29 +08:00
|
|
|
add_subdirectory_ifdef(CONFIG_FT800 ft8xx)
|
2022-01-28 05:08:18 +08:00
|
|
|
add_subdirectory_ifdef(CONFIG_GROVE_LCD_RGB grove_lcd_rgb)
|
2023-03-06 05:06:16 +08:00
|
|
|
add_subdirectory_ifdef(CONFIG_PIO_RPI_PICO pio_rpi_pico)
|
2023-08-21 16:31:34 +08:00
|
|
|
add_subdirectory_ifdef(CONFIG_NXP_S32_EMIOS nxp_s32_emios)
|
2023-06-28 21:02:04 +08:00
|
|
|
add_subdirectory_ifdef(CONFIG_TIMEAWARE_GPIO timeaware_gpio)
|
drivers: misc: devmux: a device multiplexer pseudo-device
The Device Multiplexer (devmux) is a pseudo-device that can
be used to select between multiple included sub-devices.
It is experimental, but its current use is in system
remediation. Take for example, the scenario where the
system console and log subsystem both have the uart backend
enabled. The case may arise, where the chosen backing uart
could be an abstraction of another very high-bandwidth bus
- such as a PCIe BAR, a UDP socket, or even even just memory.
If the "service" (for lack of a better term) that backs this
abstract "uart" experiences an error, it is of critical
importance to be able to switch the system console, uart log
backend, or whatever to another uart (semi-transparently) in
order to bring up a shell, continue to view system logs, or
even just support user console I/O.
Signed-off-by: Christopher Friedt <cfriedt@meta.com>
2023-09-23 03:26:11 +08:00
|
|
|
add_subdirectory_ifdef(CONFIG_DEVMUX devmux)
|