On Fri, Apr 6, 2012 at 12:14 PM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > On Fri, Apr 06, 2012 at 11:44:22AM -0700, Dan Williams wrote: >> The kt serial port intermittently reports unreliable data in its IIR >> register and needs to reset fifos to stay in sync with firmware when the >> device is reset. >> >> The IIR fixes that went into 3.3 were not complete so patch 3 replaces >> them with an explicit way to turn on UART_BUG_THRE (i.e. the "I don't >> trust my iir" flag). >> > > So the first 3 patches should go into 3.4 (and 3.3-stable) kernels, > right? Yes, since this fixes the workaround that went into 3.3 properly and addresses a regression. >> A new fix for resetting the fifos on device reset is patch 5. Alan >> asked to make this a new quirk rather than add more workarounds to the >> core (patch 4). > > These can wait for 3.5? I think they can wait especially because of the cross tree changes. >> Patch 6 is an untested RFC / RFT from anyone that has a serial >> suspend/resume use case with an 'init' quirk that has resources that >> need de-allocation at 'exit'. > > And I'll hold off on this one entirely for now, right? Yeah, if anyone runs into a similar problem with serial suspend / resume they may want to take a look at this patch. But for now I don't have a valid test case for it. -- Dan -- To unsubscribe from this list: send the line "unsubscribe linux-serial" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
