Re: [linux-sunxi] Designware UART bug

2017-05-04 Thread Olliver Schinagl
Hey Tim, On 04-05-17 05:51, Tim Kryger wrote: On Wed, May 3, 2017 at 8:40 AM, Olliver Schinagl wrote: Hey Tim, Ok, so as far as I understand (from the datasheet) the intended way to do this would be to check for the BUSY IRQ & USR[0] IRQ and if it is busy, (re-write)

Re: [linux-sunxi] Designware UART bug

2017-05-04 Thread Olliver Schinagl
Hey Tim, On 04-05-17 05:51, Tim Kryger wrote: On Wed, May 3, 2017 at 8:40 AM, Olliver Schinagl wrote: Hey Tim, Ok, so as far as I understand (from the datasheet) the intended way to do this would be to check for the BUSY IRQ & USR[0] IRQ and if it is busy, (re-write) the LCR. We no longer

Re: [linux-sunxi] Designware UART bug

2017-05-03 Thread Tim Kryger
On Wed, May 3, 2017 at 8:40 AM, Olliver Schinagl wrote: > Hey Tim, > > Ok, so as far as I understand (from the datasheet) the intended way to do > this would be to check for the BUSY IRQ & USR[0] IRQ and if it is busy, > (re-write) the LCR. We no longer do this because it did

Re: [linux-sunxi] Designware UART bug

2017-05-03 Thread Tim Kryger
On Wed, May 3, 2017 at 8:40 AM, Olliver Schinagl wrote: > Hey Tim, > > Ok, so as far as I understand (from the datasheet) the intended way to do > this would be to check for the BUSY IRQ & USR[0] IRQ and if it is busy, > (re-write) the LCR. We no longer do this because it did not work due to the

Re: [linux-sunxi] Designware UART bug

2017-05-03 Thread Olliver Schinagl
Hey Tim, On 03-05-17 16:22, Tim Kryger wrote: On Wed, May 3, 2017 at 4:26 AM, Olliver Schinagl wrote: Hey Chen-Yu On 03-05-17 12:40, Chen-Yu Tsai wrote: On Wed, May 3, 2017 at 6:17 PM, Olliver Schinagl wrote: Hey Jamie, Several years ago you

Re: [linux-sunxi] Designware UART bug

2017-05-03 Thread Olliver Schinagl
Hey Tim, On 03-05-17 16:22, Tim Kryger wrote: On Wed, May 3, 2017 at 4:26 AM, Olliver Schinagl wrote: Hey Chen-Yu On 03-05-17 12:40, Chen-Yu Tsai wrote: On Wed, May 3, 2017 at 6:17 PM, Olliver Schinagl wrote: Hey Jamie, Several years ago you wrote the glue-code [0] for the DW 8250 IP.

Re: [linux-sunxi] Designware UART bug

2017-05-03 Thread Tim Kryger
On Wed, May 3, 2017 at 4:26 AM, Olliver Schinagl wrote: > Hey Chen-Yu > > On 03-05-17 12:40, Chen-Yu Tsai wrote: >> >> On Wed, May 3, 2017 at 6:17 PM, Olliver Schinagl >> wrote: >>> >>> Hey Jamie, >>> >>> Several years ago you wrote the glue-code [0] for

Re: [linux-sunxi] Designware UART bug

2017-05-03 Thread Tim Kryger
On Wed, May 3, 2017 at 4:26 AM, Olliver Schinagl wrote: > Hey Chen-Yu > > On 03-05-17 12:40, Chen-Yu Tsai wrote: >> >> On Wed, May 3, 2017 at 6:17 PM, Olliver Schinagl >> wrote: >>> >>> Hey Jamie, >>> >>> Several years ago you wrote the glue-code [0] for the DW 8250 IP. Over >>> the >>> years

Re: [linux-sunxi] Designware UART bug

2017-05-03 Thread Olliver Schinagl
Hey Chen-Yu On 03-05-17 12:40, Chen-Yu Tsai wrote: On Wed, May 3, 2017 at 6:17 PM, Olliver Schinagl wrote: Hey Jamie, Several years ago you wrote the glue-code [0] for the DW 8250 IP. Over the years various 'fixes' have been applied to resolve certain 'weird' problems

Re: [linux-sunxi] Designware UART bug

2017-05-03 Thread Olliver Schinagl
Hey Chen-Yu On 03-05-17 12:40, Chen-Yu Tsai wrote: On Wed, May 3, 2017 at 6:17 PM, Olliver Schinagl wrote: Hey Jamie, Several years ago you wrote the glue-code [0] for the DW 8250 IP. Over the years various 'fixes' have been applied to resolve certain 'weird' problems that Tim tried to fix

Re: [linux-sunxi] Designware UART bug

2017-05-03 Thread Chen-Yu Tsai
On Wed, May 3, 2017 at 6:17 PM, Olliver Schinagl wrote: > Hey Jamie, > > Several years ago you wrote the glue-code [0] for the DW 8250 IP. Over the > years various 'fixes' have been applied to resolve certain 'weird' problems > that Tim tried to fix with [1]. > > After going

Re: [linux-sunxi] Designware UART bug

2017-05-03 Thread Chen-Yu Tsai
On Wed, May 3, 2017 at 6:17 PM, Olliver Schinagl wrote: > Hey Jamie, > > Several years ago you wrote the glue-code [0] for the DW 8250 IP. Over the > years various 'fixes' have been applied to resolve certain 'weird' problems > that Tim tried to fix with [1]. > > After going over the datasheets