2021-02-09 04:14:29 +08:00
|
|
|
# Miscellaneous drivers not exposing Zephyr Device Driver API
|
|
|
|
|
|
|
|
|
|
# Copyright (c) 2021 Nordic Semiconductor
|
|
|
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
|
|
|
|
|
|
menu "Miscellaneous Drivers"
|
|
|
|
|
|
|
|
|
|
source "drivers/misc/ft8xx/Kconfig"
|
2022-01-28 05:08:18 +08:00
|
|
|
source "drivers/misc/grove_lcd_rgb/Kconfig"
|
2023-03-06 05:06:16 +08:00
|
|
|
source "drivers/misc/pio_rpi_pico/Kconfig"
|
2023-08-21 16:31:34 +08:00
|
|
|
source "drivers/misc/nxp_s32_emios/Kconfig"
|
2023-06-28 21:02:04 +08:00
|
|
|
source "drivers/misc/timeaware_gpio/Kconfig"
|
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
|
|
|
source "drivers/misc/devmux/Kconfig"
|
2021-02-09 04:14:29 +08:00
|
|
|
|
|
|
|
|
endmenu
|
