diff options
| author | Siftar, Gabe <Gabe.Siftar@getingeusa.com> | 2012-03-29 15:40:05 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-04-09 19:30:39 +0200 |
| commit | 57c3686842114de3b0c00633591e9605c46fb769 (patch) | |
| tree | c90d5dda0cf538951e3598cc4b9cbe160d0f440e /Documentation/usb/gadget_hid.txt | |
| parent | tty: serial: altera_uart: Check for NULL platform_data in probe. (diff) | |
| download | linux-57c3686842114de3b0c00633591e9605c46fb769.tar.xz linux-57c3686842114de3b0c00633591e9605c46fb769.zip | |
tty/serial: atmel_serial: fix RS485 half-duplex problem
On our custom board, we are using RS485 in half-duplex mode on an AT91SAM9G45.
SER_RS485_RX_DURING_TX is not set as we do not want to receive the data we
transmit (our transceiver will receive transmitted data).
Although the current driver attempts to disable and enable the receiver at the
appropriate points, incoming data is still loaded into the receive register
causing our code to receive the very last byte that was sent once the receiver
is enabled.
I ran this by Atmel support and they wrote: "The issue comes from the fact
that you disable the PDC/DMA Reception and not the USART Reception channel. In
your case, the[n] you will still receive data into the USART_RHR register, and
maybe you [h]ave the overrun flag set. So please disable the USART reception
channel."
The following patch should force the driver to enable/disable the receiver via
RXEN/RXDIS fields of the USART control register. It fixed the issue I was
having.
Signed-off-by: Gabe Siftar <gabe.siftar@getingeusa.com>
[nicolas.ferre@atmel.com: slightly modify commit message]
Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/usb/gadget_hid.txt')
0 files changed, 0 insertions, 0 deletions