From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-12.8 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A6CF1C2D0E4 for ; Tue, 17 Nov 2020 14:57:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3E83B2168B for ; Tue, 17 Nov 2020 14:57:38 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=nvidia.com header.i=@nvidia.com header.b="ctuRNIY3" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729198AbgKQO5h (ORCPT ); Tue, 17 Nov 2020 09:57:37 -0500 Received: from hqnvemgate24.nvidia.com ([216.228.121.143]:9228 "EHLO hqnvemgate24.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725779AbgKQO5g (ORCPT ); Tue, 17 Nov 2020 09:57:36 -0500 Received: from hqmail.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate24.nvidia.com (using TLS: TLSv1.2, AES256-SHA) id ; Tue, 17 Nov 2020 06:57:46 -0800 Received: from HQMAIL101.nvidia.com (172.20.187.10) by HQMAIL105.nvidia.com (172.20.187.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 17 Nov 2020 14:57:34 +0000 Received: from vidyas-desktop.nvidia.com (10.124.1.5) by mail.nvidia.com (172.20.187.10) with Microsoft SMTP Server id 15.0.1473.3 via Frontend Transport; Tue, 17 Nov 2020 14:57:32 +0000 From: Vidya Sagar To: , , , CC: , , , , , Subject: [PATCH] PCI/MSI: Set device flag indicating only 32-bit MSI support Date: Tue, 17 Nov 2020 20:27:28 +0530 Message-ID: <20201117145728.4516-1-vidyas@nvidia.com> X-Mailer: git-send-email 2.17.1 X-NVConfidentiality: public MIME-Version: 1.0 Content-Type: text/plain DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1605625066; bh=ZTUMvtaqennQ1JdMmdsb/E7562d9dVUi9teJOnYd07c=; h=From:To:CC:Subject:Date:Message-ID:X-Mailer:X-NVConfidentiality: MIME-Version:Content-Type; b=ctuRNIY359o8unfTMllbc5J+MZOGVs+aYUuOr65JDk/A1YkFhI2XNj5plSaSw9YDs 7KEKrrn7MNcsBkOiMtm0RCDGFAPsDSev8TSWKtpq5WuvWcT+ki2dILqzRt0NPIT7Gd UdOClACtK/qkqKp8wwDkIQ8FD8BW7LBdnM8fF4iSUj/XUbzUwn2qwTO+mWPhuQVVqk YVegRtESl73kBT4GXImeAAeF3t4NyJUO06yLURaQwU9orqJvJe4JteRIA0lJmBvVXS KhD/9CV//VrQTdFZZLh3JgqUo87F+joeNdgFH0x6pllhyMUZmB60cf8Vva9u4p/Pgi pUxcnsMDtHjZA== Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org There are devices (Ex:- Marvell SATA controller) that don't support 64-bit MSIs and the same is advertised through their MSI capability register. Set no_64bit_msi flag explicitly for such devices in the MSI setup code so that the msi_verify_entries() API would catch if the MSI arch code tries to use 64-bit MSI. Signed-off-by: Vidya Sagar --- drivers/pci/msi.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c index d52d118979a6..af49da28854e 100644 --- a/drivers/pci/msi.c +++ b/drivers/pci/msi.c @@ -581,10 +581,12 @@ msi_setup_entry(struct pci_dev *dev, int nvec, struct irq_affinity *affd) entry->msi_attrib.multi_cap = (control & PCI_MSI_FLAGS_QMASK) >> 1; entry->msi_attrib.multiple = ilog2(__roundup_pow_of_two(nvec)); - if (control & PCI_MSI_FLAGS_64BIT) + if (control & PCI_MSI_FLAGS_64BIT) { entry->mask_pos = dev->msi_cap + PCI_MSI_MASK_64; - else + } else { entry->mask_pos = dev->msi_cap + PCI_MSI_MASK_32; + dev->no_64bit_msi = 1; + } /* Save the initial mask status */ if (entry->msi_attrib.maskbit) -- 2.17.1