Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp964999rwr; Thu, 20 Apr 2023 08:18:51 -0700 (PDT) X-Google-Smtp-Source: AKy350aDN+V5+aZyjtaoXR2HfnjeS+3TR8kpZSKt1es/5N+C3BmM/Pv+Hcexocm3Y1M41gBxFd4i X-Received: by 2002:a05:6a20:3d24:b0:f0:ae73:c58a with SMTP id y36-20020a056a203d2400b000f0ae73c58amr3163559pzi.45.1682003931590; Thu, 20 Apr 2023 08:18:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1682003931; cv=none; d=google.com; s=arc-20160816; b=UINBSk0AHQi2ySHUVFNFKjwp32OZVL8UZ9/UgWPhomEhaCPjs2fj6kVCD0hmf0SpiD Ja+4xGQuGppKso9RPtO/XUlYzSYeLpUnPpb/YitAQvIH6N+r0LYTBZrYX7AlnuQ+GjWE Sgo/NPf2OeTvYoNK686gi78ILboW9kJFMq/faKR570cabLyBdOkpYou7PFKyU2dGA2uL fsnz6+dQ4ofCATIfa5HbdaqAdPfgLBvOC2dT+BZl2UJB7qDqE2c2JOm/7/0eDw+NjWK5 Sh6jG5RzRONPEgjYS/d2TTFbQKSJglB9pdaY2kShqNIhRaiAnn9W7r9o3OmIihtjIKNW qEjA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=p1HH/gfRdJI0RAxiezxcbsJW29w1ox57o9+c8lP0sJ8=; b=mFRtMujJtg2d7QPQBBQ4iG1nX695BRgS1bWudGvorpH2pwIW99RCDXc08Ux261lPY4 +75pzcqJk60mbpDLbWeqqkg/1QVZFJeV2Zx1yHArktV2LRoLcafELauiLVCu/MMqTTt5 ZqqhNjmMO5AClZOrT6T9qPPGh2z3zOt+U5kitZ8I4qF8pqYP7ZN8iqlwiHDL5kh3+ju+ nrsaBXeV3000TYKV/eTcWIzUeacWdff/gM9oYHdvYj43p92+EIc6kPS9QCI3aWQv+ImR T8P9lQzcAcAbKhK/374iQAb+z0tiav2aW9Xq4jmhrQ7ncZTTNm7E9mOl9xNIgsFdGrlK YwQg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=TSEUYmem; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id y24-20020a63e258000000b0051bb433f5bbsi1973770pgj.386.2023.04.20.08.18.36; Thu, 20 Apr 2023 08:18:51 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=TSEUYmem; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232758AbjDTOx1 (ORCPT + 99 others); Thu, 20 Apr 2023 10:53:27 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45938 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229515AbjDTOx0 (ORCPT ); Thu, 20 Apr 2023 10:53:26 -0400 Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DDC414EDE; Thu, 20 Apr 2023 07:53:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1682002402; x=1713538402; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=o/3VG858q4YbnM1I++jrLu1F3Cew6aaRH5Qeb4OT78Q=; b=TSEUYmem78P5tAztsA1Ahseb7foYdls9ncHPqq8wBKurX7Y1eZZy6swB YLhI++x4TGk/whOvC6WpMMlaQxLnQ5KIWUOTsjjsXsXvHgiHPbTQcDiRJ CRYf/YlUciSVo7sPkBoUUaOpjynf3FY4ERAI0DCz/HsHiiGGJtXbxF0ZL 9R8W6Ptr5xgNP0Wrhcg5VFMjmVzpcherr4zD2KoPvcBDYkcV96yNFrWEV OXPlmtDfnqX/ZtsEpBa2yqJsv84gfiX4bildvOjBou5RzrpNakYjL0Z85 oooZb8rnIo0FML4BNoxq/pDY0OOBHd10dwYaoC/Rd9a8wo02kpBlx0M/V w==; X-IronPort-AV: E=McAfee;i="6600,9927,10686"; a="373658541" X-IronPort-AV: E=Sophos;i="5.99,213,1677571200"; d="scan'208";a="373658541" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Apr 2023 07:53:22 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10686"; a="642165231" X-IronPort-AV: E=Sophos;i="5.99,213,1677571200"; d="scan'208";a="642165231" Received: from samuelra-mobl7.amr.corp.intel.com (HELO [10.255.229.46]) ([10.255.229.46]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Apr 2023 07:53:22 -0700 Message-ID: Date: Thu, 20 Apr 2023 07:53:21 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Thunderbird/102.10.0 Subject: Re: [PATCH v3 3/4] PCI/AER: Disable AER interrupt on suspend Content-Language: en-US To: Kai-Heng Feng , bhelgaas@google.com Cc: mika.westerberg@linux.intel.com, koba.ko@canonical.com, Mahesh J Salgaonkar , Oliver O'Halloran , linuxppc-dev@lists.ozlabs.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org References: <20230420125941.333675-1-kai.heng.feng@canonical.com> <20230420125941.333675-3-kai.heng.feng@canonical.com> From: Sathyanarayanan Kuppuswamy In-Reply-To: <20230420125941.333675-3-kai.heng.feng@canonical.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/20/23 5:59 AM, Kai-Heng Feng wrote: > PCIe service that shares IRQ with PME may cause spurious wakeup on > system suspend. > > PCIe Base Spec 5.0, section 5.2 "Link State Power Management" states > that TLP and DLLP transmission is disabled for a Link in L2/L3 Ready > (D3hot), L2 (D3cold with aux power) and L3 (D3cold), so we don't lose > much here to disable AER during system suspend. > > This is very similar to previous attempts to suspend AER and DPC [1], > but with a different reason. > > [1] https://lore.kernel.org/linux-pci/20220408153159.106741-1-kai.heng.feng@canonical.com/ > Link: https://bugzilla.kernel.org/show_bug.cgi?id=216295 > > Reviewed-by: Mika Westerberg > Signed-off-by: Kai-Heng Feng > --- In Patch #1, you skip clearing AER errors in the resume path, right? So if we disable interrupts here, will AER driver not be notified on resume path error? > v3: > - No change. > > v2: > - Only disable AER IRQ. > - No more check on PME IRQ#. > - Use helper. > > drivers/pci/pcie/aer.c | 22 ++++++++++++++++++++++ > 1 file changed, 22 insertions(+) > > diff --git a/drivers/pci/pcie/aer.c b/drivers/pci/pcie/aer.c > index 1420e1f27105..9c07fdbeb52d 100644 > --- a/drivers/pci/pcie/aer.c > +++ b/drivers/pci/pcie/aer.c > @@ -1356,6 +1356,26 @@ static int aer_probe(struct pcie_device *dev) > return 0; > } > > +static int aer_suspend(struct pcie_device *dev) > +{ > + struct aer_rpc *rpc = get_service_data(dev); > + struct pci_dev *pdev = rpc->rpd; > + > + aer_disable_irq(pdev); > + > + return 0; > +} > + > +static int aer_resume(struct pcie_device *dev) > +{ > + struct aer_rpc *rpc = get_service_data(dev); > + struct pci_dev *pdev = rpc->rpd; > + > + aer_enable_irq(pdev); > + > + return 0; > +} > + > /** > * aer_root_reset - reset Root Port hierarchy, RCEC, or RCiEP > * @dev: pointer to Root Port, RCEC, or RCiEP > @@ -1420,6 +1440,8 @@ static struct pcie_port_service_driver aerdriver = { > .service = PCIE_PORT_SERVICE_AER, > > .probe = aer_probe, > + .suspend = aer_suspend, > + .resume = aer_resume, > .remove = aer_remove, > }; > -- Sathyanarayanan Kuppuswamy Linux Kernel Developer