On Wed, Jan 26, 2022 at 9:10 AM Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote: > > On Wed, Jan 26, 2022 at 09:52:26AM +0100, Greg Kroah-Hartman wrote: > > On Tue, Jan 25, 2022 at 03:40:36PM -0300, Wander Costa wrote: > > > On Tue, Jan 25, 2022 at 1:56 PM Andy Shevchenko > > > <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote: > > > > > > > > On Tue, Jan 25, 2022 at 06:53:48PM +0200, Andy Shevchenko wrote: > > > > > On Tue, Jan 25, 2022 at 12:40:27PM +0000, Jon Hunter wrote: > > > > > > On 25/01/2022 10:29, Wander Costa wrote: > > > > > > > > ... > > > > > > > > > > Andy, does this work for X86? > > > > > > > > > > Reported-by: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> > > > > > > > > > > No, it does NOT fix an issue (I see it on a handful x86) with the legacy UART > > > > > (means the 8250_pnp is in use). And I believe the same will be the case on LPSS > > > > > ones (8250_dw / 8250_lpss) and HSU (8250_mid), because the patch influences on > > > > > all of them. > > > > > > > > Shall I send a revert and we can continue with a new approach later on? > > > > > > > > > > Tomorrow (or maybe after tomorrow) I am going to post the fixes I > > > already have, and an additional patch adding a build option > > > (disabled to default) so people maybe if they want to use the FIFO on > > > console write. But I understand if people decide to go > > > ahead and revert the patch. > > > > Let me revert this for now. And no new config options please, this > > should "just work". > > Thanks! > > Wander, if you need a test for something new, I may help to perform on > our (sub)set of x86 machines. > Thanks, Andy. I will let you know when I have new patches.
