Unreliable register being read in max310x UART driver

[Alexander Shi]

Hello all,



The datasheet for MAX3107 UART
(http://datasheets.maximintegrated.com/en/ds/MAX3107.pdf) was updated
in February 2015 with a notice that the RxFIFOLvl register may be
inaccurate if read while being updated. The respective max310x.c
driver actively makes use of the RxFIFOLvl register, but has not been
updated since the notice was posted. Does anyone have a workaround to
this bug?



The notice was phrased as follows:

âThe RxFIFOLvl register represents the current number of words in the
receive FIFO whenever the receive UART is idle. When the receive UART
actively receives characters, the value in this register can sometimes
be inaccurate if this register is read at the same time that the
receive UART updates the receive FIFO. To manage the receive FIFO even
when the receive UART is active, do not use this register to determine
receive FIFO state. Use the RFIFOEmptyInt bit, the RxTrgInt bit, and
the RTimeOut bit instead.â



Thanks,

Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/