On Sat, 8 Feb 2025 at 16:39, Philippe Mathieu-Daudé <[email protected]> wrote: > > If the UART back-end chardev doesn't drain data as fast as stdout > does or blocks, buffer in the TX FIFO to try again later. > > This avoids having the IO-thread busy waiting on chardev back-ends, > reported recently when testing the Trusted Reference Stack and > using the socket backend. > > Implement registering a front-end 'watch' callback on back-end > events, so we can resume transmitting when the back-end is writable > again, not blocking the main loop. > > Similarly to the RX FIFO path, FIFO level selection is not > implemented (interrupt is triggered when a single byte is available > in the FIFO). > > Reported-by: Mikko Rapeli <[email protected]> > Suggested-by: Alex Bennée <[email protected]> > Signed-off-by: Philippe Mathieu-Daudé <[email protected]> > ---
Reviewed-by: Peter Maydell <[email protected]> thanks -- PMM
