Considering that nobody has answered if he is affected by this too, or not, I have to assume that this only affects my platform. Maybe its a pinmuxing issue. We will have to investigate further. :-(. I thus revoke this patch. David On 07/13/2018 11:32 AM, David R. Piegdon wrote: > Hi, > a while back I sent a few mails regarding spurious interrupts in the > UARTA (hsuart) block of the Tegra2 SoC, when using the 8250 driver for > it instead of the hsuart driver. After going down a pretty deep > debugging/testing hole, I think I found a patch that fixes the issue. So > far testing in a reboot-cycle suggests that the error frequency dropped > from >3% of all reboots to at least <0.05% of all reboots. Tests > continue to run over the weekend. > > The patch below already is a second iteration; the first did not reset > the MCR or contain the lines below '// clear interrupts'. This resulted > in no more spurious interrupts, but in a few % of spurious interrupts > that were recovered the UART block did not receive any characters any > more. So further resetting was required to fully reacquire operational > state of the UART block. > > I'd love any comments/suggestions on this! > > Cheers, > > David -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
