Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp1233327pxf; Fri, 9 Apr 2021 03:31:19 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyRx04QaRAOGCK1mRC+BNLDen8pbUGUYXlqSO/hnGPZRYzir5Vyhjc1aXeHMftkr7cDKlTN X-Received: by 2002:a05:6402:440d:: with SMTP id y13mr16964356eda.316.1617964279050; Fri, 09 Apr 2021 03:31:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617964279; cv=none; d=google.com; s=arc-20160816; b=BE8kBdmNoGzx7SPUtWHHY5jrUl17kED9LhNjteg/+cGkRTtplDgjvHLRxniypQdOwt v5FmAFjNil35kN6jvSfBGzaCqQqH9PkcZnbOS5pIwmFzZmhrmNNTS4zxGGhJxGsHDmjL Ca+D9wGWIL+ZbsufYhonTUe69Ymokt7PMlfCh+ZW/QD0CjrxLu5cK6fA1PjgCr+Mh65j RTb9NOP1tmfMcaR0huWfyczH4JCUAPsCozFbLUJ+nnSvBBOp7smIVIynxMJtj9I6SjHW Br+o8xtftl8vqJc2zA+iKru8ko0oKhPE+JtrH0Rx4vWmWGpMhyQCquTkmgJdsUl8exMY OSFg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=VwpsJJ+zuSevmRbp6PtAgYQL53jtwECP/DB0HjQmSrM=; b=f3gtXEGPTphkvi0EokYXevbrCaj8Vj1zxhZKeXpfXzcW0iWQkeqXjX8i/RW/ChY0Nk Qjsk8rdk7EeVKaCBYJ0AyOeE6y7aBLRMBc6WnY13ayoCwPgaqA3GQ+I+06KdUb3zZqR5 MnGu8ZvUexdQZlcweOq/gDzIdLd/q8OJp6DeHekYls0mrxO9bm6QDx/RJ26BkQ6iTQ4C XQqNEuCh7TYpen/cZ+kR8Q11Sa41cfyApV9KqYyqs8dpFdL44kavLDLsjwdV7qyl1Oba LsTAVrAnXIWOjerxN0xMUNRZTbWqhmsptevHZhq6JNC+S0PCKx9L3iYYMtkb+/IihdFr we/Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bm7si2028865edb.188.2021.04.09.03.30.56; Fri, 09 Apr 2021 03:31:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233173AbhDIKaH (ORCPT + 99 others); Fri, 9 Apr 2021 06:30:07 -0400 Received: from foss.arm.com ([217.140.110.172]:47724 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231402AbhDIKaG (ORCPT ); Fri, 9 Apr 2021 06:30:06 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 72E8F1FB; Fri, 9 Apr 2021 03:29:53 -0700 (PDT) Received: from lpieralisi (e121166-lin.cambridge.arm.com [10.1.196.255]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 397DB3F73D; Fri, 9 Apr 2021 03:29:52 -0700 (PDT) Date: Fri, 9 Apr 2021 11:29:46 +0100 From: Lorenzo Pieralisi To: Rahul Tanwar Cc: Martin Blumenstingl , "robh@kernel.org" , "linux-pci@vger.kernel.org" , "bhelgaas@google.com" , "linux-kernel@vger.kernel.org" , Cheol Yong Kim , Qiming Wu , Lei Chuan Hua Subject: Re: [PATCH] PCI: dwc/intel-gw: Fix enabling the legacy PCI interrupt lines Message-ID: <20210409102946.GA14799@lpieralisi> References: <20210106135540.48420-1-martin.blumenstingl@googlemail.com> <20210323113559.GE29286@e121166-lin.cambridge.arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 09, 2021 at 10:17:12AM +0000, Rahul Tanwar wrote: > On 9/4/2021 4:40 am, Martin Blumenstingl wrote: > > This email was sent from outside of MaxLinear. > > > > Hi Lorenzo, > > > > On Tue, Mar 23, 2021 at 12:36 PM Lorenzo Pieralisi > > wrote: > > > > > > On Wed, Jan 06, 2021 at 02:55:40PM +0100, Martin Blumenstingl wrote: > > > > The legacy PCI interrupt lines need to be enabled using PCIE_APP_IRNEN > > > > bits 13 (INTA), 14 (INTB), 15 (INTC) and 16 (INTD). The old code > > however > > > > was taking (for example) "13" as raw value instead of taking BIT(13). > > > > Define the legacy PCI interrupt bits using the BIT() macro and then use > > > > these in PCIE_APP_IRN_INT. > > > > > > > > Fixes: ed22aaaede44 ("PCI: dwc: intel: PCIe RC controller driver") > > > > Signed-off-by: Martin Blumenstingl > > > > --- > > > > drivers/pci/controller/dwc/pcie-intel-gw.c | 10 ++++++---- > > > > 1 file changed, 6 insertions(+), 4 deletions(-) > > > > > > > > diff --git a/drivers/pci/controller/dwc/pcie-intel-gw.c > > b/drivers/pci/controller/dwc/pcie-intel-gw.c > > > > index 0cedd1f95f37..ae96bfbb6c83 100644 > > > > --- a/drivers/pci/controller/dwc/pcie-intel-gw.c > > > > +++ b/drivers/pci/controller/dwc/pcie-intel-gw.c > > > > @@ -39,6 +39,10 @@ > > > > #define PCIE_APP_IRN_PM_TO_ACK BIT(9) > > > > #define PCIE_APP_IRN_LINK_AUTO_BW_STAT BIT(11) > > > > #define PCIE_APP_IRN_BW_MGT BIT(12) > > > > +#define PCIE_APP_IRN_INTA BIT(13) > > > > +#define PCIE_APP_IRN_INTB BIT(14) > > > > +#define PCIE_APP_IRN_INTC BIT(15) > > > > +#define PCIE_APP_IRN_INTD BIT(16) > > > > #define PCIE_APP_IRN_MSG_LTR BIT(18) > > > > #define PCIE_APP_IRN_SYS_ERR_RC BIT(29) > > > > #define PCIE_APP_INTX_OFST 12 > > > > @@ -48,10 +52,8 @@ > > > > PCIE_APP_IRN_RX_VDM_MSG | PCIE_APP_IRN_SYS_ERR_RC | \ > > > > PCIE_APP_IRN_PM_TO_ACK | PCIE_APP_IRN_MSG_LTR | \ > > > > PCIE_APP_IRN_BW_MGT | PCIE_APP_IRN_LINK_AUTO_BW_STAT | \ > > > > - (PCIE_APP_INTX_OFST + PCI_INTERRUPT_INTA) | \ > > > > - (PCIE_APP_INTX_OFST + PCI_INTERRUPT_INTB) | \ > > > > - (PCIE_APP_INTX_OFST + PCI_INTERRUPT_INTC) | \ > > > > - (PCIE_APP_INTX_OFST + PCI_INTERRUPT_INTD)) > > > > + PCIE_APP_IRN_INTA | PCIE_APP_IRN_INTB | \ > > > > + PCIE_APP_IRN_INTC | PCIE_APP_IRN_INTD) > > > > > > > > #define BUS_IATU_OFFSET SZ_256M > > > > #define RESET_INTERVAL_MS 100 > > > > > > This looks like a significant bug - which in turn raises the question > > > on how well this driver has been tested. > > to give them the benefit of doubt: maybe only MSIs were tested > > > > > Dilip, can you review and ACK asap please ? > > From "Re: MaxLinear, please maintain your drivers was Re: [PATCH] > > leds: lgm: fix gpiolib dependency" [0]: > > > Please send any Lightning Mountain SoC related issues email to Rahul > > > Tanwar (rtanwar@maxlinear.com) and I will ensure that I address the > > > issues in a timely manner. > > so I added rtanwar@maxlinear.com to this email > > > > > > Best regards, > > Martin > > > > > > [0] https://lkml.org/lkml/2021/3/16/282 > > > > > Dilip has left the org. So not sure how exactly he tested it (maybe only > MSIs). But i have confirmed it to be a bug. Thanks Martin for fixing it. Can you take on maintainership for this driver please ? If yes please send a MAINTAINERS file patch. Thanks, Lorenzo > Acked-by: Rahul Tanwar > > Regards, > Rahul > > > > >