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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id EFCDEC433FE for ; Wed, 26 Oct 2022 13:29:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233040AbiJZN3Y (ORCPT ); Wed, 26 Oct 2022 09:29:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57304 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233810AbiJZN3G (ORCPT ); Wed, 26 Oct 2022 09:29:06 -0400 Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8C87C1011A9 for ; Wed, 26 Oct 2022 06:29:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1666790944; x=1698326944; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=afQlBJK1A7StgB+cXIhXdVoxkjfKZpJynWrKwkAWWj4=; b=KbtxREPF0+w/2l1htHAl0xYROvrMROuc+THKdsNz4hHNDTQStaR4wzQ2 drO5K//Y9uvGyUtsHju6Lou1Z4lJ8fF0K6zBWCu0oeOd2Z7933UwzE9LU /3CoX6e/SyL4X7d4LC2fwptsiDSg+NRc6vSSa7zPQQpRtBB05vE0FTxBd SYx5IHravPi4xbqIhjZADCLEET2RdeoWx+0AkeXIpq0n+XMtgSwFTfTcx YQ9zdXBMM7QTUGeWmT2hLRrJ0O/SVB7R+KEBPB49nxlSMDBU6FsGAmrqF xGNabKgh6ggyN+wFHpShDM9Hb5wwvUcEY/eZ+Ug5Tvfxue6bOPWpWxgTX A==; X-IronPort-AV: E=McAfee;i="6500,9779,10512"; a="309036776" X-IronPort-AV: E=Sophos;i="5.95,214,1661842800"; d="scan'208";a="309036776" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 26 Oct 2022 06:29:04 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10512"; a="757299748" X-IronPort-AV: E=Sophos;i="5.95,214,1661842800"; d="scan'208";a="757299748" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga004.jf.intel.com with ESMTP; 26 Oct 2022 06:29:01 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1ongSp-002fOk-2R; Wed, 26 Oct 2022 16:28:59 +0300 Date: Wed, 26 Oct 2022 16:28:59 +0300 From: Andy Shevchenko To: Jarkko Nikula Cc: linux-i2c@vger.kernel.org, Wolfram Sang , Mika Westerberg , Jan Dabros , Michael Wu , Tian Ye , Luis Oliveira Subject: Re: [PATCH 07/11] i2c: designware: Do not process interrupt when device is suspended Message-ID: References: <20221026123912.2833271-1-jarkko.nikula@linux.intel.com> <20221026123912.2833271-8-jarkko.nikula@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221026123912.2833271-8-jarkko.nikula@linux.intel.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-i2c@vger.kernel.org On Wed, Oct 26, 2022 at 03:39:08PM +0300, Jarkko Nikula wrote: > Do not return with interrupt handled if host controller is off and thus > interrupt is originating from other device or is spurious. > > Add a check to detect when controller is runtime suspended or > transitioning/reset. In latter case all raw interrupt status register > bits may read one. In both cases return IRQ_NONE to indicate interrupt > was not from this device. ... > dev_dbg(dev->dev, "enabled=%#x stat=%#x\n", enabled, stat); > if (!enabled || !(stat & ~DW_IC_INTR_ACTIVITY)) > return IRQ_NONE; > + if (pm_runtime_suspended(dev->dev) || stat == ~0) > + return IRQ_NONE; I haven't checked the type of 'stat', but usually be careful with ~0. Due to integer promotion it may give the unexpected results. -- With Best Regards, Andy Shevchenko