From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Thomas Bohn <thbohn@gmail.com>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: dmaengine <dmaengine@vger.kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: idma64.0 is keeping my processor awake after boot
Date: Tue, 6 Aug 2019 16:10:40 +0300 [thread overview]
Message-ID: <20190806131040.GE30120@smile.fi.intel.com> (raw)
In-Reply-To: <20190806130840.GD30120@smile.fi.intel.com>
(+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
prev parent reply other threads:[~2019-08-06 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190806131040.GE30120@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=thbohn@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.