aboutsummaryrefslogtreecommitdiff
path: root/sys/contrib/dev/mediatek/mt76/mt7615/mac.c
diff options
context:
space:
mode:
authorJohn Baldwin <jhb@FreeBSD.org>2025-11-03 15:24:23 +0000
committerJohn Baldwin <jhb@FreeBSD.org>2025-11-03 15:24:23 +0000
commitb9efaeb87a8f9cfc0cd87076a8b314785d6e04d9 (patch)
tree81ef996acc2837eab1029e86ec22e4d3c87b6a79 /sys/contrib/dev/mediatek/mt76/mt7615/mac.c
parent5f43b0cb7c3cb7c3209598f8c0818cb47cd9de96 (diff)
tb_pci: Don't try to attach to PCI buses that aren't below a PCI-PCI brigeHEADmain
This driver is a subclass of the normal PCI bus driver that is intended to be used for the logical child bus of a Thunderbolt PCI-PCI bridge device. To determine if a given PCI bus's parent is a TB bridge, it examines the PCI device IDs of the parent pcibX device. However, this only works for pcibX devices that are actual PCI-PCI bridges and panics for PCI buses that are children of host bridges such as the pci0 child of pcib0. Probably this should not be reading device IDs (as that doesn't tell you if the device driver for the PCI-PCI bridge is actually a TB driver). Instead, the TB PCI-PCI driver should be exporting a new IVAR (with a globally unique number as we do for ACPI handles) that returns the TB generation and the probe routine for this PCI bus driver should be checking for that IVAR (the way acpi_pci.c checks for the presence of an ACPI handle). This fixes a panic on boot if tb.ko is loaded at boot time (which the driver recommends for certain chipsets). Reviewed by: imp Differential Revision: https://reviews.freebsd.org/D53202
Diffstat (limited to 'sys/contrib/dev/mediatek/mt76/mt7615/mac.c')
0 files changed, 0 insertions, 0 deletions