summaryrefslogtreecommitdiffstats
path: root/crypto
diff options
context:
space:
mode:
authorAndrey Smirnov <andrew.smirnov@gmail.com>2018-04-12 14:33:17 -0700
committerSascha Hauer <s.hauer@pengutronix.de>2018-04-17 09:21:10 +0200
commit0f73d8fb36ec9b51cea9f78aa66a138b4a361cd0 (patch)
tree141a0a34cf15915200acce596663f49fc720b5c7 /crypto
parent25cb29b1357d5005de3e149744a2ebee03a743bf (diff)
downloadbarebox-0f73d8fb36ec9b51cea9f78aa66a138b4a361cd0.tar.gz
barebox-0f73d8fb36ec9b51cea9f78aa66a138b4a361cd0.tar.xz
serdev: Allow polling interval to be adjusted at runtime
Due to blocking, synchronous, polling driven nature of Barebox's serial communication handling trying to use two or more serial ports at high (1Mbaud+) baudrates results in data loss and noticeable perofmance degradation. This happens as soon as individual message being sent around start exceeding HW Rx FIFO in size. A good example of such a usecase would be using a system that has a serdev driver (operating @ 1Mbaud+) and trying to do a X/YMODEM transfer via serial console at comparable baudrates. To at least partially ameliorate the problem, add code that will expose "polling_interval" as a parameter, so that the user would have an option of temporarily disabling (or significatly decreasing the rate) of a given serdev's polling. Signed-off-by: Andrey Smirnov <andrew.smirnov@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions