From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A0998231B18; Wed, 4 Dec 2024 17:12:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1733332371; cv=none; b=VXz6xmOty1NXuVIgc4dGZAWavL0GzuQ8jWMIAdojMANhieqii8TgyEU+iMuNihclsjmUeGFu86+XLN/OWrKp9yDhhBJYCdLlb1n7RFRnMBrt0p7W9T7UyHUrR8UTLv+Vsqx1ivJB9DuGpVoFFv6I6pUbst73bqLfI4OayGh+WOA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1733332371; c=relaxed/simple; bh=SNcve0V9xevORIZCAX9ZqrZqeOThNfVhFiQknY9ghGk=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=CNfh1exD2/iCIyIZqZs4YQMLdzb980LNKy0urApCyaiiLcqMAheXCR2z1Ao3iIgqIcEH+pYG9bsyes2EIdiP55Gq1a20dXs7271bYtlRQMalnkGTZsf/JfuyIKsN724ISxPagVT28cWAbaYLhSeObhc8Y3L/GPBVzo1HQ0P4CnI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=CxgD6nRT; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="CxgD6nRT" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8184CC4CED1; Wed, 4 Dec 2024 17:12:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1733332371; bh=SNcve0V9xevORIZCAX9ZqrZqeOThNfVhFiQknY9ghGk=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=CxgD6nRTVYLbJmUd50bTJJf1hXnzdIr7Jix1M/NUBscvoUpcNhV7/HJZ6f3fhZwoA BDtRJEix32iepUo9vfzIKTunWDaN5bJlQO8nrbNhxqwiUjXK5xbWA0oorP2LGSSZfv QBZqpYiMXTlsKYE3mQQVmLZC4yKTBckTZ/aPOtjE0QKDuyCUNmq1JlagwODpseRxgy ulPz6CCt9gMfUJqdNhCT244u1ndUXSyS+cj9tzg/B7Ug5CyzvHHns7U7e9nkhe3a5a SLOeLsS40qVpjakCzhmnCzBrC4RehBm6m3NRq9u88WVvmDMM34I7Ofzz6dKtcfniwf v1gIixYFafmLw== From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Mengyuan Lou , Bjorn Helgaas , Sasha Levin , linux-pci@vger.kernel.org Subject: [PATCH AUTOSEL 6.6 09/12] PCI: Add ACS quirk for Wangxun FF5xxx NICs Date: Wed, 4 Dec 2024 11:01:06 -0500 Message-ID: <20241204160115.2216718-9-sashal@kernel.org> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20241204160115.2216718-1-sashal@kernel.org> References: <20241204160115.2216718-1-sashal@kernel.org> Precedence: bulk X-Mailing-List: linux-pci@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore X-stable-base: Linux 6.6.63 Content-Transfer-Encoding: 8bit From: Mengyuan Lou [ Upstream commit aa46a3736afcb7b0793766d22479b8b99fc1b322 ] Wangxun FF5xxx NICs are similar to SFxxx, RP1000 and RP2000 NICs. They may be multi-function devices, but they do not advertise an ACS capability. But the hardware does isolate FF5xxx functions as though it had an ACS capability and PCI_ACS_RR and PCI_ACS_CR were set in the ACS Control register, i.e., all peer-to-peer traffic is directed upstream instead of being routed internally. Add ACS quirk for FF5xxx NICs in pci_quirk_wangxun_nic_acs() so the functions can be in independent IOMMU groups. Link: https://lore.kernel.org/r/E16053DB2B80E9A5+20241115024604.30493-1-mengyuanlou@net-swift.com Signed-off-by: Mengyuan Lou Signed-off-by: Bjorn Helgaas Signed-off-by: Sasha Levin --- drivers/pci/quirks.c | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c index 54061b65a2b72..c5115ad597664 100644 --- a/drivers/pci/quirks.c +++ b/drivers/pci/quirks.c @@ -4989,18 +4989,21 @@ static int pci_quirk_brcm_acs(struct pci_dev *dev, u16 acs_flags) } /* - * Wangxun 10G/1G NICs have no ACS capability, and on multi-function - * devices, peer-to-peer transactions are not be used between the functions. - * So add an ACS quirk for below devices to isolate functions. + * Wangxun 40G/25G/10G/1G NICs have no ACS capability, but on + * multi-function devices, the hardware isolates the functions by + * directing all peer-to-peer traffic upstream as though PCI_ACS_RR and + * PCI_ACS_CR were set. * SFxxx 1G NICs(em). * RP1000/RP2000 10G NICs(sp). + * FF5xxx 40G/25G/10G NICs(aml). */ static int pci_quirk_wangxun_nic_acs(struct pci_dev *dev, u16 acs_flags) { switch (dev->device) { - case 0x0100 ... 0x010F: - case 0x1001: - case 0x2001: + case 0x0100 ... 0x010F: /* EM */ + case 0x1001: case 0x2001: /* SP */ + case 0x5010: case 0x5025: case 0x5040: /* AML */ + case 0x5110: case 0x5125: case 0x5140: /* AML */ return pci_acs_ctrl_enabled(acs_flags, PCI_ACS_SV | PCI_ACS_RR | PCI_ACS_CR | PCI_ACS_UF); } -- 2.43.0