Commit aa46a373 authored by Mengyuan Lou's avatar Mengyuan Lou Committed by Bjorn Helgaas
Browse files

PCI: Add ACS quirk for Wangxun FF5xxx NICs 

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: default avatarMengyuan Lou <mengyuanlou@net-swift.com>
Signed-off-by: default avatarBjorn Helgaas <bhelgaas@google.com>
parent 9852d85e

drivers/pci/quirks.c

+9 −6
Original line number Diff line number Diff line
@@ -4996,18 +4996,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);

	}