Re: [PATCH] serial: imx: reduce irq-latency after rx overflow

2015-06-22 Thread Alexander Stein
Hello Manfred, On Monday 22 June 2015 10:20:10, Manfred Schlaegl wrote: > On 2015-06-22 08:48, Alexander Stein wrote: > > Am Samstag, 20. Juni 2015, 19:25:52 schrieb Manfred Schlaegl: > >> To prevent problems with interrupt latency, and due to the fact, that > >> the error will be counted anyway (

Re: [PATCH] serial: imx: reduce irq-latency after rx overflow

2015-06-22 Thread Manfred Schlaegl
On 2015-06-22 08:48, Alexander Stein wrote: > Am Samstag, 20. Juni 2015, 19:25:52 schrieb Manfred Schlaegl: >> To prevent problems with interrupt latency, and due to the fact, that >> the error will be counted anyway (icount.overrun), the dev_err is simply >> removed. >> >> Background: >> If an rx-

Re: [PATCH] serial: imx: reduce irq-latency after rx overflow

2015-06-21 Thread Alexander Stein
Am Samstag, 20. Juni 2015, 19:25:52 schrieb Manfred Schlaegl: > To prevent problems with interrupt latency, and due to the fact, that > the error will be counted anyway (icount.overrun), the dev_err is simply > removed. > > Background: > If an rx-fifo overflow occurs a dev_err message was called i

[PATCH] serial: imx: reduce irq-latency after rx overflow

2015-06-20 Thread Manfred Schlaegl
To prevent problems with interrupt latency, and due to the fact, that the error will be counted anyway (icount.overrun), the dev_err is simply removed. Background: If an rx-fifo overflow occurs a dev_err message was called in interrupt context. Since dev_err messages are written to console in a sy

[PATCH] serial: imx: reduce irq-latency after rx overflow

2015-06-20 Thread manfred.schla...@gmx.at
To prevent problems with interrupt latency, and due to the fact, that the error will be counted anyway (icount.overrun), the dev_err is simply removed. Background: If an rx-fifo overflow occurs a dev_err message was called in interrupt context. Since dev_err messages are written to console in a sy