diff options
| author | Mathieu Othacehe <[email protected]> | 2024-08-08 08:06:37 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2024-08-13 11:06:46 +0200 |
| commit | c9f6613b16123989f2c3bd04b1d9b2365d6914e7 (patch) | |
| tree | 06b5a341cf8f821700d9adadbd1c89dd11fb71d1 /lib/test_fortify/write_overflow-strncpy-src.c | |
| parent | 7258fdd7d7459616b3fe1a603e33900584b10c13 (diff) | |
tty: atmel_serial: use the correct RTS flag.
In RS485 mode, the RTS pin is driven high by hardware when the transmitter
is operating. This behaviour cannot be changed. This means that the driver
should claim that it supports SER_RS485_RTS_ON_SEND and not
SER_RS485_RTS_AFTER_SEND.
Otherwise, when configuring the port with the SER_RS485_RTS_ON_SEND, one
get the following warning:
kern.warning kernel: atmel_usart_serial atmel_usart_serial.2.auto:
ttyS1 (1): invalid RTS setting, using RTS_AFTER_SEND instead
which is contradictory with what's really happening.
Signed-off-by: Mathieu Othacehe <[email protected]>
Cc: stable <[email protected]>
Tested-by: Alexander Dahl <[email protected]>
Fixes: af47c491e3c7 ("serial: atmel: Fill in rs485_supported")
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions