Dropped characters in serial connection without flow control
Quoted 2 lines · Peter Stuge
I'm writing a line discipline for a serial port multiplexing hardware
There is no(!) support for flow control in the hardware.
Is there anything I can do to reduce serial port interrupt latency or otherwise try to mitigate this in my ldisc or in Linux in general? I realize that it will never be quite reliable without any flow control.
Baud rate is currently 115200 but could become 57600.
Is there something in particular that I can do wrong or right in the ldisc?
Might it be a good idea to add a circ_buf in the receiver path and move out any and all attempts at parsing incoming data? Currently it has a simple message buffer and a state machine in there.
Characters are dropped both going out and coming in. Nothing to do about the out direction, but maybe input can be made reliable?
I don't expect it, but maybe you know a trick?
//Peter
Quoted 10 lines · Peter Stuge
Quoted 2 lines · Peter Stuge
I'm writing a line discipline for a serial port multiplexing hardware
There is no(!) support for flow control in the hardware.
Is there anything I can do to reduce serial port interrupt latency or otherwise try to mitigate this in my ldisc or in Linux in general? I realize that it will never be quite reliable without any flow control.
What's wrong with XON/XOFF? That is a well-known flow control protocol for systems without hardware support for it.
And since when is adding a UART to a hardware chip expensive these days?
thanks,
greg k-h
Quoted 5 lines · Greg KH
Quoted 3 lines
There is no(!) support for flow control in the hardware.
Is there anything I can do
What's wrong with XON/XOFF?
That was my thought also. I asked about flow control, both hardware and software, and got word from the firmware developer that the device firmware can not be changed to support hardware flow control. I didn't get a comment on XON/XOFF and have already asked again. Meanwhile I wanted to also check here.
Quoted 2 lines
And since when is adding a UART to a hardware chip expensive these days?
I agree. I'm trying to work toward a more advanced hardware solution.
//Peter
Quoted 1 line
There is no(!) support for flow control in the hardware.
So do XON/XOFF ?
Quoted 6 lines
Is there anything I can do to reduce serial port interrupt latency or otherwise try to mitigate this in my ldisc or in Linux in general? I realize that it will never be quite reliable without any flow control.
Baud rate is currently 115200 but could become 57600.
The core tty buffering code tops out at about 40Mbits on a decent PC system so you shouldn't be seeing problems from that. Our internal buffering is about 64K which at 115200 is actually over 5 seconds.
Quoted 6 lines
Is there something in particular that I can do wrong or right in the ldisc?
Might it be a good idea to add a
circ_bufin the receiver path and move out any and all attempts at parsing incoming data? Currently it has a simple message buffer and a state machine in there.
ldisc processing is not done in the receiver path
Quoted 4 lines
Characters are dropped both going out and coming in. Nothing to do about the out direction, but maybe input can be made reliable?
I don't expect it, but maybe you know a trick?
Without knowing more about the hardware and the code and the like its a bit tricky to even guess what your problems are.