Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp4964787yba; Tue, 30 Apr 2019 07:09:37 -0700 (PDT) X-Google-Smtp-Source: APXvYqxKrJlYhluFXuFSSIloAkaiHJCTVdKltousvUN0oWZf/eeZ8OCwpJQPc1A4yCV5Aed9J9Pl X-Received: by 2002:a17:902:b28:: with SMTP id 37mr68164731plq.322.1556633377009; Tue, 30 Apr 2019 07:09:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1556633377; cv=none; d=google.com; s=arc-20160816; b=z99RQefUGFYUBKufue4sU1GdLWoWlsquSA9LmYMDpdQwMViQyr6UeWRNQ/XJB56eOx h64kAlyLhFOCAAaz7Pe0pBGI0Va2jfZxXBqZMSdwtqC/87vfO5OdOAQpjBUkti9wBfNd z2sYkoEVPGPnp2VpWPvUxuiy2eDlv/vRE+oGL50WHIwxzHQc1F2P2RP9wph/QAS1o3cO vWXGdofmdjx9HdnTFl84iWRIjDRKXRsu9aC1v7NEVPYek+gjf3SdxvlxIIjnd2WzJEE0 mcMfGzkiYhBdsQT/6asWTos0Tz1V3aeKHEBUqr60VQTpa0WvNCxiiCtxOKchO7+2h/oc dsOQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=THJa1ZmiN9Z9Z3Ciqt0E7WRytXq7IE0rM3aai9/ovPk=; b=JgHRXfoU26L6woC1MwWTKe0NzKCe84W6e9g0Rp7aoahHQKp9fP3ONdM3vuDiWj0+WZ R0PNh9WeAw+UNS+WUkoT1ErH7WXhEsECRHG+0uGWSlfYFIOUbRIJOIF1M8VAqEimXa5H maA6YxZloKkWqu8gZl7FhyljkYpM+3E4opERrugel2nll4xAHixnl6q1ydOaPxL9zfWw tNzaGFchbpSCHb1Vp1mxRvfOU7LP52693Z+OwY2S9XymQWFswU5pE5p0SSY3HhypRZ/N 7WWr6etBIUg19dUqQGg/GQVwtt48lSdz+9jrEG8SOLYmHOEsATmQUtlCZpbgHt5aJqV2 i4YQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j7si40385417pfb.75.2019.04.30.07.09.00; Tue, 30 Apr 2019 07:09:36 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728077AbfD3OG1 (ORCPT + 99 others); Tue, 30 Apr 2019 10:06:27 -0400 Received: from foss.arm.com ([217.140.101.70]:48040 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726436AbfD3OG0 (ORCPT ); Tue, 30 Apr 2019 10:06:26 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 64DCD80D; Tue, 30 Apr 2019 07:06:26 -0700 (PDT) Received: from e121166-lin.cambridge.arm.com (e121166-lin.cambridge.arm.com [10.1.196.255]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 85A763F719; Tue, 30 Apr 2019 07:06:24 -0700 (PDT) Date: Tue, 30 Apr 2019 15:06:21 +0100 From: Lorenzo Pieralisi To: Marc Gonzalez Cc: Stanimir Varbanov , Bjorn Helgaas , Andy Gross , David Brown , Bjorn Andersson , PCI , MSM , LKML , Jeffrey Hugo Subject: Re: [RFC PATCH v1] PCI: qcom: Use quirk to override incorrect device class Message-ID: <20190430140621.GB18742@e121166-lin.cambridge.arm.com> References: <94bb3f22-c5a7-1891-9d89-42a520e9a592@free.fr> <65321fe3-ca29-c454-63ae-98a46c2e5158@mm-sol.com> <1205cbfb-ac06-63a5-9401-75d4e68b15b5@free.fr> <38ad143b-3b07-4d19-8ccd-ca39fb51e53d@free.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <38ad143b-3b07-4d19-8ccd-ca39fb51e53d@free.fr> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 12, 2019 at 06:34:55PM +0100, Marc Gonzalez wrote: > On 12/03/2019 18:18, Marc Gonzalez wrote: > > > On 12/03/2019 13:42, Stanimir Varbanov wrote: > > > >> I wonder, in case that dw_pcie_setup_rc() already has a write to > >> PCI_CLASS_DEVICE configuration register to set it as a bridge do we > >> still need to do the above fixup? > > > > I don't know, I don't have an affected device. Unless the msm8998 /is/ affected, > > and dw_pcie_setup_rc() actually fixes it? > > I think you hit the nail on the head... > > If I comment out > //dw_pcie_wr_own_conf(pp, PCI_CLASS_DEVICE, 2, PCI_CLASS_BRIDGE_PCI); > from dw_pcie_setup_rc() > then pci_class() returns 0xff000000 instead of 0x6040000 > > So perhaps you're right: the quirk can be omitted altogether. > Unless it is not possible to program the device class on older chips? Marc, I would drop this patch from the PCI queue since in a different form it was already merged, please let me know if I am wrong. Thanks, Lorenzo