On Thu, 2018-02-01 at 23:51 +0200, Andy Shevchenko wrote: > On Thu, 2018-02-01 at 22:31 +0200, Andy Shevchenko wrote: > > On Thu, 2018-02-01 at 20:28 +0100, Nikola Ciprich wrote: > > > > > > > 7d8905d064058f4b65057e0101588f362f288bc0 is the first bad commit > > > commit 7d8905d064058f4b65057e0101588f362f288bc0 > > > Author: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> > > > Date: Mon Jul 24 20:28:32 2017 +0300 > > > > > > serial: 8250_pci: Enable device after we check black list > > Looking to the patch more I have only one idea in mind. The driver now > skips the function 0 which seems has correct IRQ line and continues > with > the rest where it eventually matches devices as serial. > > It would be nice to have output of > > % lspci -vv -n -xxx # before _and_ after this commit applied (or > reverted) Hmm... I'm not sure I understand fully what's going on there. Since there is no entry for the board it would fail either way (with or without above patch). Can you send output of lspci as asked above and describe how your board works before? (I think dmesg output with and without patch is also good to have, while kernel command line contains 'ignore_loglevel initcall_debug') -- Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> Intel Finland Oy -- 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
