Received: by 2002:ac0:950c:0:0:0:0:0 with SMTP id f12csp2286386imc; Tue, 12 Mar 2019 10:36:32 -0700 (PDT) X-Google-Smtp-Source: APXvYqzIvnpFPdKU7D1G661d+UTQ+ebeQyl7j9aPHMmbRw6HZp8pmLYTNWm43ZuGeH3IS63ZRDQ3 X-Received: by 2002:aa7:9259:: with SMTP id 25mr39294129pfp.221.1552412192783; Tue, 12 Mar 2019 10:36:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552412192; cv=none; d=google.com; s=arc-20160816; b=Ow577w3lHrStpRPmBf85pIg90Yp/Mzpm50JosPLEWFB8es9E+FM8S4QuZ/MZo7EFbm wjTHcSviD7igCLBeysbhQHE+kB6JFmvD0wQ/7swYDBE8KeND+nOLSoVMfKtzDHjaRwQD krVz+B9sLaWFcHSKHkkpOklsKiuNbwvU/np+b5LR65AgckChTWNHV4Z37bs1x9AN5YFs 3sK/6ID5r2UW3azTNkFaOCIDWIis3yHOezHG82ROF8rmHYLypGPI+PvJaFoVK0bFaEyO NNLab4c27aLYTw4n7Q+28i3iU0qok0IynIxo0BngiS240KPVGFqyVIKqaoqMZJrxMKi1 rTlg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:references:cc:to:from:subject; bh=i3gPPb+Xjuz74VNQyLtiZphoMTrlapj1oV0hp9ccN5A=; b=pXIFeycHajbVIAwBlm97TP9yfaEIj4CM9PpNXtjFYt3lJpUlsZO6n4pG8+3+YTgzSM isXXZmoViRjSM6ADDZburM8MdvwwBhLypZxYcgSfvgg3AEdBWFrUJjtUVbi9g5WSP3kp r0/uviyjltR/mmR/xsLimzIxmrNP5SSPe+M3Qf8Df8WCuESPa68oK++jSDuyPT7hr8XY lBQOWmKyCzKtwl5ckMzTQVKCi8It64fXqIEecHIKZHtUXhNvqS8FA6j63/fvzM72qQJo oHzuu1OsW+mRQ6wzE9DtTy6MpWkbP8fpUrz1KENMH5+7Pcwpq/Swc6NdtF2KXxCJFc0A pbsg== 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 r5si3628195plo.40.2019.03.12.10.36.17; Tue, 12 Mar 2019 10:36:32 -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 S1729817AbfCLRfS (ORCPT + 99 others); Tue, 12 Mar 2019 13:35:18 -0400 Received: from smtp3-g21.free.fr ([212.27.42.3]:56654 "EHLO smtp3-g21.free.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729354AbfCLRfQ (ORCPT ); Tue, 12 Mar 2019 13:35:16 -0400 Received: from [192.168.108.8] (unknown [213.36.7.13]) (Authenticated sender: marc.w.gonzalez) by smtp3-g21.free.fr (Postfix) with ESMTPSA id 9C78313F8E2; Tue, 12 Mar 2019 18:34:55 +0100 (CET) Subject: Re: [RFC PATCH v1] PCI: qcom: Use quirk to override incorrect device class From: Marc Gonzalez To: Stanimir Varbanov , Bjorn Helgaas Cc: Andy Gross , David Brown , Bjorn Andersson , PCI , MSM , LKML , Jeffrey Hugo References: <94bb3f22-c5a7-1891-9d89-42a520e9a592@free.fr> <65321fe3-ca29-c454-63ae-98a46c2e5158@mm-sol.com> <1205cbfb-ac06-63a5-9401-75d4e68b15b5@free.fr> Message-ID: <38ad143b-3b07-4d19-8ccd-ca39fb51e53d@free.fr> Date: Tue, 12 Mar 2019 18:34:55 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 In-Reply-To: <1205cbfb-ac06-63a5-9401-75d4e68b15b5@free.fr> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? Regards.