* Re: idma64.0 is keeping my processor awake after boot [not found] ` <CAJEfxfaz+K-Wpun4Crqu1i5ocXKm0+rJv9=PSP3rqmztdpdH5A@mail.gmail.com> @ 2019-08-06 13:08 ` Andy Shevchenko 2019-08-06 13:10 ` Andy Shevchenko 0 siblings, 1 reply; 2+ messages in thread From: Andy Shevchenko @ 2019-08-06 13:08 UTC (permalink / raw) To: Thomas Bohn; +Cc: dmaengine, Mika Westerberg 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@linux.intel.com>: > > On Tue, 2016-11-15 at 22:03 +0100, Thomas Bohn wrote: > >> 2016-11-15 17:19 GMT+01:00 Andy Shevchenko <andriy.shevchenko@linux.in > >> 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 ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: idma64.0 is keeping my processor awake after boot 2019-08-06 13:08 ` idma64.0 is keeping my processor awake after boot Andy Shevchenko @ 2019-08-06 13:10 ` Andy Shevchenko 0 siblings, 0 replies; 2+ messages in thread From: Andy Shevchenko @ 2019-08-06 13:10 UTC (permalink / raw) To: Thomas Bohn, Jarkko Nikula; +Cc: dmaengine, Mika Westerberg (+Cc Jarkko) On Tue, Aug 06, 2019 at 04:08:40PM +0300, Andy Shevchenko wrote: > 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@linux.intel.com>: > > > On Tue, 2016-11-15 at 22:03 +0100, Thomas Bohn wrote: > > >> 2016-11-15 17:19 GMT+01:00 Andy Shevchenko <andriy.shevchenko@linux.in > > >> 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 ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-08-06 13:10 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CAJEfxfYRZs_XH9Kp7ocB-ZZjAKa8eNo3vgCq1qWtL1Ak+cWS9A@mail.gmail.com>
[not found] ` <1479226768.24056.23.camel@linux.intel.com>
[not found] ` <CAJEfxfZAXfOJ79CjbfZWXVK_Y3+1+EQAja2wu3LGUGFzes75kQ@mail.gmail.com>
[not found] ` <1479291233.24056.35.camel@linux.intel.com>
[not found] ` <CAJEfxfaz+K-Wpun4Crqu1i5ocXKm0+rJv9=PSP3rqmztdpdH5A@mail.gmail.com>
2019-08-06 13:08 ` idma64.0 is keeping my processor awake after boot Andy Shevchenko
2019-08-06 13:10 ` Andy Shevchenko
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.