On 08/29/2014 06:12 PM, Tony Lindgren wrote: > Looks like the paste bug is there for sure, doing off idle and pasting > 240 characters to the console can hang the UART RX after few attempts, > and pasting 16 charactes won't show up at all if the system is idling. > So you may want to play with that too a bit :) One character wakes it up. After that you can send 16, 64 and you see them. Right away. No delay. If you send "a lot" data in one-go it takes approx 152 characters until the first one is displayed properly at 115200,8N1. That is approx 13ms. Could it take that long to get up and be ready? Comparing it with serial-omap I see the same thing: I takes approx the same amount of data until the first one is displayed. After a lot of "long" writes which wake the chip up from idle I manage to freeze both, the serial-omap driver and mine driver. One thing that is probably a dumb idea is that printk in omap_8250_mdr1_errataset(). Would it be possible that when I hit a printk in the resume path that I may deadlock and box will freeze? > > Regards, > > Tony > Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
