From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 08C92C433FF for ; Tue, 6 Aug 2019 13:10:54 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id DB11920C01 for ; Tue, 6 Aug 2019 13:10:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729506AbfHFNKx (ORCPT ); Tue, 6 Aug 2019 09:10:53 -0400 Received: from mga01.intel.com ([192.55.52.88]:1931 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728582AbfHFNKx (ORCPT ); Tue, 6 Aug 2019 09:10:53 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Aug 2019 06:10:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,353,1559545200"; d="scan'208";a="174176343" Received: from smile.fi.intel.com (HELO smile) ([10.237.68.145]) by fmsmga008.fm.intel.com with ESMTP; 06 Aug 2019 06:10:41 -0700 Received: from andy by smile with local (Exim 4.92) (envelope-from ) id 1huzEe-0008Ne-DI; Tue, 06 Aug 2019 16:10:40 +0300 Date: Tue, 6 Aug 2019 16:10:40 +0300 From: Andy Shevchenko To: Thomas Bohn , Jarkko Nikula Cc: dmaengine , Mika Westerberg Subject: Re: idma64.0 is keeping my processor awake after boot Message-ID: <20190806131040.GE30120@smile.fi.intel.com> References: <1479226768.24056.23.camel@linux.intel.com> <1479291233.24056.35.camel@linux.intel.com> <20190806130840.GD30120@smile.fi.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190806130840.GD30120@smile.fi.intel.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.10.1 (2018-07-13) Sender: dmaengine-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: dmaengine@vger.kernel.org (+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 : > > > On Tue, 2016-11-15 at 22:03 +0100, Thomas Bohn wrote: > > >> 2016-11-15 17:19 GMT+01:00 Andy Shevchenko > >> 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