From patchwork Tue Sep 5 17:57:01 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Bjorn Helgaas X-Patchwork-Id: 9939421 X-Patchwork-Delegate: bhelgaas@google.com Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id 25EC760350 for ; Tue, 5 Sep 2017 17:57:07 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 1BA6B289E6 for ; Tue, 5 Sep 2017 17:57:07 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 10198289F3; Tue, 5 Sep 2017 17:57:07 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.9 required=2.0 tests=BAYES_00,RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 9AC91289E6 for ; Tue, 5 Sep 2017 17:57:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752136AbdIER5F (ORCPT ); Tue, 5 Sep 2017 13:57:05 -0400 Received: from mail.kernel.org ([198.145.29.99]:57962 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752129AbdIER5E (ORCPT ); Tue, 5 Sep 2017 13:57:04 -0400 Received: from localhost (unknown [69.71.4.159]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id DD13821E92; Tue, 5 Sep 2017 17:57:03 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org DD13821E92 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=helgaas@kernel.org Date: Tue, 5 Sep 2017 12:57:01 -0500 From: Bjorn Helgaas To: Arnd Bergmann Cc: Bjorn Helgaas , Ray Jui , Scott Branden , Jon Mason , bcm-kernel-feedback-list@broadcom.com, Oza Pawandeep , Lorenzo Pieralisi , linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/2] PCI: iproc: fix Stingray CRS defect handling Message-ID: <20170905175701.GB14367@bhelgaas-glaptop.roam.corp.google.com> References: <20170905072004.3959082-1-arnd@arndb.de> <20170905072004.3959082-2-arnd@arndb.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20170905072004.3959082-2-arnd@arndb.de> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-pci-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP On Tue, Sep 05, 2017 at 09:19:45AM +0200, Arnd Bergmann wrote: > The condition that was used to detect the PCI_EXP_RTCAP > flag access is wrong, as pointed out by gcc-8: > > drivers/pci/host/pcie-iproc.c: In function 'iproc_pcie_config_read': > drivers/pci/host/pcie-iproc.c:531:22: error: bitwise comparison always evaluates to false [-Werror=tautological-compare] > if ((where & ~0x3) == PCI_EXP_CAP + PCI_EXP_RTCAP) > > This adds the same bit mask to the other end as well, so the > condition is evaluated correctly for any access. > > Fixes: ac8d3e852f75 ("PCI: iproc: Work around Stingray CRS defects") > Signed-off-by: Arnd Bergmann > --- > drivers/pci/host/pcie-iproc.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/pci/host/pcie-iproc.c b/drivers/pci/host/pcie-iproc.c > index d7f4c29aed96..f2df9c2266b9 100644 > --- a/drivers/pci/host/pcie-iproc.c > +++ b/drivers/pci/host/pcie-iproc.c > @@ -528,7 +528,7 @@ static int iproc_pcie_config_read(struct pci_bus *bus, unsigned int devfn, > return ret; > > /* Don't advertise CRS SV support */ > - if ((where & ~0x3) == PCI_EXP_CAP + PCI_EXP_RTCAP) > + if ((where & ~0x3) == ((PCI_EXP_CAP + PCI_EXP_RTCAP) & ~0x03)) > *val &= ~(PCI_EXP_RTCAP_CRSVIS << 16); > return PCIBIOS_SUCCESSFUL; > } Definitely looks like a bug. I'm slightly confused because Oza tested this and reported that lspci said CRS SV was not supported. But there used to be an lspci bug related to reporting CRS SV, and there are a lot of executables that don't have the fix: http://git.kernel.org/cgit/utils/pciutils/pciutils.git/commit/?id=1cefd379194e lspci -vvxxx should have enough info to tell for sure. Oza, any chance you could apply the incremental patch (or use my pci/host-iproc branch) and collect that lspci output? I propose the following slightly different fix because (a) the shift in the next line depends on the fact that we read the 32-bit value that contains both PCI_EXP_RTCTL and PCI_EXP_RTCAP so I like the use of PCI_EXP_RTCTL as a hint that it's involved and (b) there's similar code in xgene_pcie_config_read32() that uses the equivalent of PCI_EXP_RTCTL; see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pci/host/pci-xgene.c?h=v4.13#n191 diff --git a/drivers/pci/host/pcie-iproc.c b/drivers/pci/host/pcie-iproc.c index 0e29338703bf..9a006cbc3021 100644 --- a/drivers/pci/host/pcie-iproc.c +++ b/drivers/pci/host/pcie-iproc.c @@ -528,7 +528,7 @@ static int iproc_pcie_config_read(struct pci_bus *bus, unsigned int devfn, return ret; /* Don't advertise CRS SV support */ - if ((where & ~0x3) == PCI_EXP_CAP + PCI_EXP_RTCAP) + if ((where & ~0x3) == PCI_EXP_CAP + PCI_EXP_RTCTL) *val &= ~(PCI_EXP_RTCAP_CRSVIS << 16); return PCIBIOS_SUCCESSFUL; }