+Jakub, linux-serial Michael, let the list know what you find. I don't have access to a sc16is7xx device with more than one port. Jon On Wed, Jun 24, 2015 at 10:59 AM, Michael Allwright <michael.allwright@xxxxxx> wrote: > Thanks Jon, > > This version of the driver is no longer causing those threading > complaints on the OMAP4 platform, opening the first port of the > sc16is762 works perfectly, but the second port appears to be > overflowing and giving me garbage. Even after exiting picocom I get > these messages every 2-3 seconds and the system takes a long time (a > minute or so?) to recover. > > [ 505.289154] sc16is7xx_handle_rx: XXXX callbacks suppressed > [ 505.294921] sc16is7xx 1-0048: Port 1: Possible RX FIFO overrun: 64 > [ 505.303894] sc16is7xx 1-0048: Port 1: Possible RX FIFO overrun: 64 > [ 505.312835] sc16is7xx 1-0048: Port 1: Possible RX FIFO overrun: 64 > [ 505.321807] sc16is7xx 1-0048: Port 1: Possible RX FIFO overrun: 64 > [ 505.330688] sc16is7xx 1-0048: Port 1: Possible RX FIFO overrun: 64 > [ 505.339599] sc16is7xx 1-0048: Port 1: Possible RX FIFO overrun: 64 > [ 505.348663] sc16is7xx 1-0048: Port 1: Possible RX FIFO overrun: 64 > [ 505.357635] sc16is7xx 1-0048: Port 1: Possible RX FIFO overrun: 64 > [ 505.366577] sc16is7xx 1-0048: Port 1: Possible RX FIFO overrun: 64 > [ 505.375701] sc16is7xx 1-0048: Port 1: Possible RX FIFO overrun: 64 > > where XXXX is typically around 2000 callbacks. I will investigate > tomorrow and try find a solution. > > Cheers, > > Michael > > Michael Allwright > > PhD Student > Paderborn Institute for Advanced Studies in Computer Science and Engineering > > University of Paderborn > Office-number 02-47 > Zukunftsmeile 1 > 33102 Paderborn > Germany > > > On 19 June 2015 at 17:47, Jon Ringle <jon@xxxxxxxxxx> wrote: >> On Fri, Jun 19, 2015 at 11:13 AM, Michael Allwright >> <michael.allwright@xxxxxx> wrote: >>> No problem, by the way - I have your driver running on 4.0.5 on a dual >>> core OMAP4, and when closing port for the first time (only) I see >>> these errors is the kernel log. Everything keeps working and I can >>> open/close the ports as much as I want afterwards without any >>> complaint... Any thoughts? >> >> Work has been done in tty-next >> (git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git) to >> change sc16is7xx driver to use kworker threads. The changes there may >> resolve what you are observing >> >> -Jon -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
