Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp12224732ybl; Sat, 28 Dec 2019 07:43:50 -0800 (PST) X-Google-Smtp-Source: APXvYqwJ3sSDwHCodWxifinIHd67DYT1eXaZRVPjH0rdg1CjCiQNFuNZqMHvAcnqOfXldP+F4zG/ X-Received: by 2002:a9d:51ca:: with SMTP id d10mr61175080oth.76.1577547830783; Sat, 28 Dec 2019 07:43:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1577547830; cv=none; d=google.com; s=arc-20160816; b=VhRH6lUtcgrUcx1EKY8gAuBXnbAjYdVSX0Rj1k7YjdcODWxQUzVGLirD6GsgJKRrdw bTM90hc26YwcIYaoPJ5+nbysr9N5X40lxmw/Rl0hxsmZK9pDvcr4XbL+azv7agDy5xCW L+cnWPzhOZGTEPIeJ0EIoo5S1wLeFWobhebbkIDSLwB6aewRg5HsymrI5JJ7SIVSDytI Hdr21Yr+UfrJeIzHnlI+I7w886z909rVqrxXQ4jbFYp5ux7b+dtdE+q8kaEISXso+cWP JPS/0S7PGW4IhGELkYmUvKiSGz6SqDb6+dfjFIfw5JNQo+GcQyrl88TwpfnCdzkZk0Mg s1aQ== 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:from:references:cc:to:subject; bh=K6eYwFM2Vobyxaxt2nXTSiibn9ndA1An5YcMB7sDgBQ=; b=MYu+mORnJhY7xyss43XvBQkBLNPDwC6JmzuPlf6zUpVf1a1TxKKiV0YAj53/ixR9Ix l1Dy95yGm44Ub8XjpBGp8udekjn4MmoBFKGfVjxes2SYJ8zQ3TBxttPsEuX2KX5BSNa/ KV20+tKRdIn8vGqq39gW/tBLFKfyJKyJMnhkDcZvv4QXetIoO3toWDrUEYIlGJb1xk7K DnlCAH3cWPC3HoIepKnwtUGchGvOYDnSfxbVyOCI/CVZo8CNZpGvwpY6lQERFLsfh/2U gmC/UmqxT1eRNYSE1nvgfTI1Lv4H+e+iwFtqFKihNbb7XjY9Bcvv2JHChuVdMe+ihFYn TU6Q== 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 a9si10640978oid.132.2019.12.28.07.43.39; Sat, 28 Dec 2019 07:43:50 -0800 (PST) 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 S1726460AbfL1Pla (ORCPT + 99 others); Sat, 28 Dec 2019 10:41:30 -0500 Received: from smtp4-g21.free.fr ([212.27.42.4]:21342 "EHLO smtp4-g21.free.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726080AbfL1Pla (ORCPT ); Sat, 28 Dec 2019 10:41:30 -0500 Received: from [192.168.1.91] (unknown [77.207.133.132]) (Authenticated sender: marc.w.gonzalez) by smtp4-g21.free.fr (Postfix) with ESMTPSA id 6AC7119F5A8; Sat, 28 Dec 2019 16:41:08 +0100 (CET) Subject: Re: [PATCH v2] PCI: qcom: Fix the fixup of PCI_VENDOR_ID_QCOM To: Stanimir Varbanov , Bjorn Andersson , Lorenzo Pieralisi , Andrew Murray , Bjorn Helgaas Cc: linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org References: <20191227012717.78965-1-bjorn.andersson@linaro.org> <9e5ee7e8-aa63-e82c-8135-acc77b476c87@mm-sol.com> From: Marc Gonzalez Message-ID: <38acf5fc-85aa-7090-e666-97a1281e9905@free.fr> Date: Sat, 28 Dec 2019 16:41:08 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: <9e5ee7e8-aa63-e82c-8135-acc77b476c87@mm-sol.com> 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 27/12/2019 09:51, Stanimir Varbanov wrote: > On 12/27/19 3:27 AM, Bjorn Andersson wrote: > >> There exists non-bridge PCIe devices with PCI_VENDOR_ID_QCOM, so limit >> the fixup to only affect the relevant PCIe bridges. >> >> Cc: stable@vger.kernel.org >> Signed-off-by: Bjorn Andersson >> --- >> >> Stan, I picked up all the suggested device id's from the previous thread and >> added 0x1000 for QCS404. I looked at creating platform specific defines in >> pci_ids.h, but SDM845 has both 106 and 107... Please let me know if you would >> prefer that I do this anyway. > > Looks good, > > Acked-by: Stanimir Varbanov > >> drivers/pci/controller/dwc/pcie-qcom.c | 8 +++++++- >> 1 file changed, 7 insertions(+), 1 deletion(-) >> >> diff --git a/drivers/pci/controller/dwc/pcie-qcom.c b/drivers/pci/controller/dwc/pcie-qcom.c >> index 5ea527a6bd9f..138e1a2d21cc 100644 >> --- a/drivers/pci/controller/dwc/pcie-qcom.c >> +++ b/drivers/pci/controller/dwc/pcie-qcom.c >> @@ -1439,7 +1439,13 @@ static void qcom_fixup_class(struct pci_dev *dev) >> { >> dev->class = PCI_CLASS_BRIDGE_PCI << 8; >> } >> -DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_QCOM, PCI_ANY_ID, qcom_fixup_class); >> +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_QCOM, 0x0101, qcom_fixup_class); >> +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_QCOM, 0x0104, qcom_fixup_class); >> +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_QCOM, 0x0106, qcom_fixup_class); >> +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_QCOM, 0x0107, qcom_fixup_class); >> +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_QCOM, 0x0302, qcom_fixup_class); >> +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_QCOM, 0x1000, qcom_fixup_class); >> +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_QCOM, 0x1001, qcom_fixup_class); Hrmmm... still not CCed on the patch, and still don't think the fixup is required(?) for 0x106 and 0x107. Regards.