a7df3a1e09
The whole "tty" concept is conceived around efficient interrupt-driven operation. However, it's beneficial to add non interupt-driven operation under the same API: 1. Wider usecase coverage in general. 2. Allows to use the same familiar API (based on POSIX concepts) even for UART implementations without interrupt support. 3. Allows to switch operation dynamically based on the needs. For example, if the system is in degraded mode and interrupt handling cannot be trusted/disabled, allows to still output diagnostic information to user. This was the original motivation to provide such a mode, to support logging subsystem's "panic" mode. To implement this feature, tty_set_rx_buf() and tty_set_tx_buf() functions are provided, allowing to reconfigure buffers used dynamically. If configured buffer length is 0, the operation switched to unbuffered. Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org> |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| getchar.c | ||
| getline.c | ||
| Kconfig | ||
| line_fifo.c | ||
| tty.c | ||