On Wed, Nov 16, 2016 at 06:14:51PM +0100, Thomas Bohn wrote: > 2016-11-16 11:13 GMT+01:00 Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>: > > On Tue, 2016-11-15 at 22:03 +0100, Thomas Bohn wrote: > >> 2016-11-15 17:19 GMT+01:00 Andy Shevchenko <andriy.shevchenko@xxxxxxxx > >> tel.com>: > >> > idma64 itself can't be a culprit of such behaviour. > >> > > >> > The driver is loaded and bound whenever one of I2C, UART or SPI > >> > controllers is enumerated and have DMA capability enabled. > >> > > >> > So, if you check /proc/interrupt and see what is the counterpart for > >> > this DMA IP (some driver with .0 at the end) it would be helpful. Isn't it the same as described in https://bugzilla.kernel.org/show_bug.cgi?id=177311 -- With Best Regards, Andy Shevchenko
