Skip to contentSkip to conversation

PCI: Add d3cold and device-specific reset for Qualcomm devices

PATCH Superseded Jose Ignacio Tornos Martinez 2 participants 6 messages May 21 PCI

v5 of 15 Superseded Latest is v15 →

lore
Share & tools
lore
#0 lore raw

v5 cover PCI: Add d3cold and device-specific reset for Qualcomm devices

Some PCIe devices lack working reset methods for VFIO passthrough scenarios. These devices typically have no FLR, advertise NoSoftRst+ (blocking PM reset), and have broken or unavailable bus reset. When a VM crashes, VFIO cannot reset the device for reuse without a working reset method.

This series addresses the problem by adding general d3cold infrastructure and device-specific reset for Qualcomm devices:

**Patch 1/3: d3cold reset method**
Adds D3cold as a general reset method with strict _PR3 requirement. Only attempts true power cycling via platform control (ACPI _PR3), never falls back to D3hot. This provides genuine power-off reset on platforms that support it.

**Patch 2/3: device-specific reset for Qualcomm devices**
Adds device-specific reset entries for Qualcomm ath11k/ath12k WiFi and SDX62/SDX65 modems using D3cold power cycling with automatic D3hot fallback. Uses pci_set_power_state(D3cold) which automatically falls back to D3hot on platforms without _PR3. Extracts shared pci_dev_d3cold_d0_cycle() helper to avoid code duplication with general d3cold method. Device-specific reset is position #1 in reset hierarchy, providing immediate working reset for these Qualcomm devices.

**Patch 3/3: Qualcomm quirk_no_bus_reset**
Disables broken bus reset for Qualcomm devices. Testing proves this is
device-specific: MediaTek MT7925e works correctly with bus reset using the same passive M.2-to-PCIe adapters where Qualcomm devices fail, confirming PERST# is properly wired and the issue is not deployment-specific. Acts as safety net to prevent broken SBR if users override via sysfs.

v5: - Follow the advice from Alex Williamson, replace v4's general "soft"
reset method (patch 2/3) as too broad by a device-specific reset using pci_dev_reset_methods[]
- Address the suggestion of AI review (sashiko.dev), add IOMMU handling (pci_dev_reset_iommu_prepare/done) to prevent IOMMU faults during power state transitions
v4: https://lore.kernel.org/all/[email protected]/

Jose Ignacio Tornos Martinez (3):
PCI: Add d3cold as general reset method
PCI: Add device-specific reset for Qualcomm devices
PCI: Disable broken bus reset on Qualcomm devices

--
2.53.0

#1 lore raw

PATCH v5 1/3 PCI: Add d3cold as general reset method

Add D3cold power cycle as a general PCI reset method for single-function devices on platforms with ACPI _PR3 power resources. This provides true power cycle reset capability when the platform can physically cut power to the device.

The implementation strictly requires _PR3 to be present - the platform must be able to control device power. This ensures d3cold only attempts true power cycling, not falling back to D3hot transitions.

D3cold reset is placed at the end of the reset hierarchy since it requires specific platform support and should be tried after standard methods.

Reset hierarchy with this change:
1. device_specific
2. acpi
3. flr
4. af_flr
5. pm (D3hot via config space, checks NoSoftRst)
6. bus (SBR)
7. cxl_bus
8. d3cold (NEW - true power cycle, requires _PR3)

This benefits:
- Platforms with _PR3 support
- Single-function devices needing true power cycle
- VFIO passthrough scenarios where FLR/PM unavailable

---
v5: Address the suggestion of AI review (sashiko.dev), add IOMMU handling
(pci_dev_reset_iommu_prepare/done) to prevent IOMMU faults during power state transitions
v4: https://lore.kernel.org/all/[email protected]/

 drivers/pci/pci.c   | 50 +++++++++++++++++++++++++++++++++++++++++++++
 include/linux/pci.h |  2 +-
 2 files changed, 51 insertions(+), 1 deletion(-)
drivers/pci/pci.c +50 -0
index 8f7cfcc00090..096868f80cd4 100644
@@ -4491,6 +4491,55 @@ static int pci_pm_reset(struct pci_dev *dev, bool probe)
 	return ret;
 }
 
+/**
+ * pci_d3cold_reset - Put device into D3cold and back to D0 for reset
+ * @dev: PCI device to reset
+ * @probe: if true, check if D3cold reset is supported; if false, perform reset
+ *
+ * Reset the device by transitioning through D3cold (actual power removal via
+ * platform power control) and back to D0. This requires ACPI _PR3 power
+ * resources to be present - the platform must be able to physically cut power
+ * to the device.
+ *
+ * Only available for single-function devices to avoid affecting other
+ * functions in multi-function devices.
+ *
+ * Returns 0 if device can be/was reset this way, -ENOTTY if not supported,
+ * or other negative error code on failure.
+ */
+static int pci_d3cold_reset(struct pci_dev *dev, bool probe)
+{
+	int ret;
+
+	if (dev->multifunction)
+		return -ENOTTY;
+
+	if (!pci_pr3_present(dev))
+		return -ENOTTY;
+
+	if (probe)
+		return 0;
+
+	if (dev->current_state != PCI_D0)
+		return -EINVAL;
+
+	ret = pci_dev_reset_iommu_prepare(dev);
+	if (ret) {
+		pci_err(dev, "failed to stop IOMMU for a PCI reset: %d\n", ret);
+		return ret;
+	}
+
+	ret = pci_set_power_state(dev, PCI_D3cold);
+	if (ret)
+		goto done;
+
+	ret = pci_set_power_state(dev, PCI_D0);
+
+done:
+	pci_dev_reset_iommu_done(dev);
+	return ret;
+}
+
 /**
  * pcie_wait_for_link_status - Wait for link status change
  * @pdev: Device whose link to wait for.
@@ -5065,6 +5114,7 @@ const struct pci_reset_fn_method pci_reset_fn_methods[] = {
 	{ pci_pm_reset, .name = "pm" },
 	{ pci_reset_bus_function, .name = "bus" },
 	{ cxl_reset_bus_function, .name = "cxl_bus" },
+	{ pci_d3cold_reset, .name = "d3cold" },
 };
 
 /**
include/linux/pci.h +1 -1
index 2c4454583c11..1ca7b880ead7 100644
@@ -51,7 +51,7 @@
 			       PCI_STATUS_PARITY)
 
 /* Number of reset methods used in pci_reset_fn_methods array in pci.c */
-#define PCI_NUM_RESET_METHODS 8
+#define PCI_NUM_RESET_METHODS 9
 
 #define PCI_RESET_PROBE		true
 #define PCI_RESET_DO_RESET	false
Signature · 1 line
2.54.0
#2 lore raw

Re: [PATCH v5 1/3] PCI: Add d3cold as general reset method

Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider: - [Critical] pci_d3cold_reset() fails to apply PCIe link training delays and wait for device readiness…

Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
- [Critical] pci_d3cold_reset() fails to apply PCIe link training delays and wait for device readiness after transitioning from D3cold to D0, resulting in immediate reset failure and state corruption.
- [Critical] D3cold reset can silently fail to reset the device if the ACPI power resource is shared, posing a security isolation risk for VFIO.
- [High] Calling pci_set_power_state(dev, PCI_D0) inside a low-level reset callback triggers premature and unsafe state restoration.
--

commit c06e579db46f355df1b179a606f12711b2bbc974
Author: Jose Ignacio Tornos Martinez <[email protected]>

PCI: Add d3cold as general reset method

Add D3cold power cycle as a general PCI reset method for single-function devices on platforms with ACPI _PR3 power resources.

Quoted 5 lines
drivers/pci/pci.c +0 -0
index 8f7cfcc000901..096868f80cd4c 100644
@@ -4491,6 +4491,55 @@ static int pci_pm_reset(struct pci_dev *dev, bool probe)

[ ... ]

Quoted 13 lines
drivers/pci/pci.c +13 -0
+static int pci_d3cold_reset(struct pci_dev *dev, bool probe)
+{
+	int ret;
+
+	if (dev->multifunction)
+		return -ENOTTY;
+
+	if (!pci_pr3_present(dev))
+		return -ENOTTY;
+
+	if (probe)
+		return 0;
+

drivers/pci/pci.c static int pci_pm_reset(struct pci_dev *dev, bool probe) · line 4532

Quoted 10 lines
drivers/pci/pci.c +10 -0
+	if (dev->current_state != PCI_D0)
+		return -EINVAL;
+
+	ret = pci_dev_reset_iommu_prepare(dev);
+	if (ret) {
+		pci_err(dev, "failed to stop IOMMU for a PCI reset: %d\n", ret);
+		return ret;
+	}
+
+	ret = pci_set_power_state(dev, PCI_D3cold);

[Severity: Critical]
If the ACPI power resource is shared among multiple devices, does this actually remove physical power?

ACPI power resources are reference-counted. If the resource is shared, putting one device into D3cold merely decrements the reference count, leaving the device physically in D3hot.

When transitioned back to D0, if the device has the NoSoftRst property set, it will not undergo an internal reset, yet pci_set_power_state() will return 0 indicating success.

Can this silent failure break device isolation for userspace assignment?

drivers/pci/pci.c static int pci_pm_reset(struct pci_dev *dev, bool probe) · line 4536

Quoted 4 lines
drivers/pci/pci.c +4 -0
+	if (ret)
+		goto done;
+
+	ret = pci_set_power_state(dev, PCI_D0);

[Severity: Critical]
Does this code apply PCIe link training delays and wait for device readiness after reapplying physical power?

When returning from D3cold, pci_set_power_state() will transition through pci_power_up(), which turns on ACPI power and immediately attempts to read PCI_PM_CTRL without any bus-level delay.

Because the link is untrained, this read typically returns 0xFFFF, causing a -EIO failure. This failure can cause the reset framework to proceed to pci_dev_restore() while the link is still down, resulting in corrupted hardware state.

[Severity: High]
Does calling pci_set_power_state() here trigger premature state restoration?

The pci_set_power_state() function invokes pci_set_full_power_state(), which includes a call to pci_restore_bars() if it detects context was lost.

Since the PCI reset framework handles state saving and restoration exclusively in higher-level callers, restoring BARs within the low-level reset callback itself bypasses this design.

Additionally, these BAR restoration writes are likely to be dropped since they occur before the device is confirmed to be safely accepting configuration writes on a trained link.

Quoted 5 lines
drivers/pci/pci.c +5 -0
+
+done:
+	pci_dev_reset_iommu_done(dev);
+	return ret;
+}
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=1
#3 lore raw

PATCH v5 2/3 PCI: Add device-specific reset for Qualcomm devices

In reply to Jose Ignacio Tornos Martinez

Some Qualcomm PCIe devices (ath11k WiFi, ath12k WiFi, SDX62/SDX65 modems) lack working reset methods for VFIO passthrough scenarios. These devices have no FLR capability, advertise NoSoftRst+ (blocking PM reset), and have broken bus reset.

The problem manifests in VFIO passthrough scenarios:

- ath11k WiFi (17cb:1103): Normal VM operation works fine, including clean shutdown/reboot. However, when the VM terminates uncleanly (crash, force-off), VFIO attempts to reset the device before it can be assigned to another VM. Without a working reset method, the device remains in an undefined state, preventing reuse.

- ath12k WiFi (17cb:1107): Same behavior as ath11k.

- SDX62/SDX65 5G modems (17cb:0308): Never successfully initialize even on first VM assignment without proper reset capability.

Add device-specific reset entries for these Qualcomm devices using D3cold power cycling with automatic D3hot fallback. The implementation uses pci_set_power_state(D3cold) which automatically falls back to D3hot on platforms without ACPI _PR3 power resources.

Extract a shared pci_dev_d3cold_d0_cycle() helper function to avoid code duplication between pci_d3cold_reset() (strict _PR3 requirement) and the new reset_d3cold_d3hot() device-specific reset (automaticfallback). The helper handles IOMMU preparation, performs the power cycle via pci_set_power_state(), and cleans up IOMMU state.

Device-specific reset is position #1 in the reset hierarchy, so these Qualcomm devices will use power cycling as their primary reset method, with the general d3cold method (position #8) available as a fallback on _PR3-capable platforms if users override via sysfs.

---
v5: Follow the advice from Alex Williamson, replace v4's general "soft"
reset method (patch 2/3) as too broad by a device-specific reset using pci_dev_reset_methods[]
v4: https://lore.kernel.org/all/[email protected]/

 drivers/pci/pci.c    | 55 ++++++++++++++++++++++++++++----------------
 drivers/pci/pci.h    |  1 +
 drivers/pci/quirks.c | 19 +++++++++++++++
 3 files changed, 55 insertions(+), 20 deletions(-)
drivers/pci/pci.c +35 -20
index 096868f80cd4..3677aaf8d160 100644
@@ -4491,6 +4491,40 @@ static int pci_pm_reset(struct pci_dev *dev, bool probe)
 	return ret;
 }
 
+/**
+ * pci_dev_d3cold_d0_cycle - Perform D3cold->D0 power cycle
+ * @dev: Device to power cycle
+ *
+ * Common helper to perform D3cold->D0 power cycle for reset methods.
+ * Attempts D3cold transition with automatic fallback to D3hot on platforms
+ * without ACPI _PR3 power resources. Handles IOMMU preparation and cleanup.
+ *
+ * Returns 0 on success, negative error code on failure.
+ */
+int pci_dev_d3cold_d0_cycle(struct pci_dev *dev)
+{
+	int ret;
+
+	if (dev->current_state != PCI_D0)
+		return -EINVAL;
+
+	ret = pci_dev_reset_iommu_prepare(dev);
+	if (ret) {
+		pci_err(dev, "failed to stop IOMMU for a PCI reset: %d\n", ret);
+		return ret;
+	}
+
+	ret = pci_set_power_state(dev, PCI_D3cold);
+	if (ret)
+		goto done;
+
+	ret = pci_set_power_state(dev, PCI_D0);
+
+done:
+	pci_dev_reset_iommu_done(dev);
+	return ret;
+}
+
 /**
  * pci_d3cold_reset - Put device into D3cold and back to D0 for reset
  * @dev: PCI device to reset
@@ -4509,8 +4543,6 @@ static int pci_pm_reset(struct pci_dev *dev, bool probe)
  */
 static int pci_d3cold_reset(struct pci_dev *dev, bool probe)
 {
-	int ret;
-
 	if (dev->multifunction)
 		return -ENOTTY;
 
@@ -4520,24 +4552,7 @@ static int pci_d3cold_reset(struct pci_dev *dev, bool probe)
 	if (probe)
 		return 0;
 
-	if (dev->current_state != PCI_D0)
-		return -EINVAL;
-
-	ret = pci_dev_reset_iommu_prepare(dev);
-	if (ret) {
-		pci_err(dev, "failed to stop IOMMU for a PCI reset: %d\n", ret);
-		return ret;
-	}
-
-	ret = pci_set_power_state(dev, PCI_D3cold);
-	if (ret)
-		goto done;
-
-	ret = pci_set_power_state(dev, PCI_D0);
-
-done:
-	pci_dev_reset_iommu_done(dev);
-	return ret;
+	return pci_dev_d3cold_d0_cycle(dev);
 }
 
 /**
drivers/pci/pci.h +1 -0
index 4a14f88e543a..a9942787de9e 100644
@@ -234,6 +234,7 @@ void pci_init_reset_methods(struct pci_dev *dev);
 int pci_bridge_secondary_bus_reset(struct pci_dev *dev);
 int pci_bus_error_reset(struct pci_dev *dev);
 int pci_try_reset_bridge(struct pci_dev *bridge);
+int pci_dev_d3cold_d0_cycle(struct pci_dev *dev);
 
 struct pci_cap_saved_data {
 	u16		cap_nr;
drivers/pci/quirks.c +19 -0
index e49136ac5dbf..70f3b0f26799 100644
@@ -4237,6 +4237,22 @@ static int reset_hinic_vf_dev(struct pci_dev *pdev, bool probe)
 	return 0;
 }
 
+/*
+ * Device-specific reset method via D3cold/D3hot power cycle.
+ *
+ * Some devices lack working FLR, advertise NoSoftRst+ (blocking PM reset),
+ * and have broken bus reset. This function provides device-specific reset via
+ * power cycling, attempting D3cold with automatic fallback to D3hot on platforms
+ * without ACPI _PR3 power resources.
+ */
+static int reset_d3cold_d3hot(struct pci_dev *dev, bool probe)
+{
+	if (probe)
+		return 0;
+
+	return pci_dev_d3cold_d0_cycle(dev);
+}
+
 static const struct pci_dev_reset_methods pci_dev_reset_methods[] = {
 	{ PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82599_SFP_VF,
 		 reset_intel_82599_sfp_virtfn },
@@ -4252,6 +4268,9 @@ static const struct pci_dev_reset_methods pci_dev_reset_methods[] = {
 		reset_chelsio_generic_dev },
 	{ PCI_VENDOR_ID_HUAWEI, PCI_DEVICE_ID_HINIC_VF,
 		reset_hinic_vf_dev },
+	{ PCI_VENDOR_ID_QCOM, 0x1103, reset_d3cold_d3hot },  /* ath11k */
+	{ PCI_VENDOR_ID_QCOM, 0x1107, reset_d3cold_d3hot },  /* ath12k */
+	{ PCI_VENDOR_ID_QCOM, 0x0308, reset_d3cold_d3hot },  /* SDX62/SDX65 */
 	{ 0 }
 };
 
Signature · 1 line
2.54.0
#4 lore raw

Re: [PATCH v5 2/3] PCI: Add device-specific reset for Qualcomm devices

Thank you for your contribution! Sashiko AI review found 4 potential issue(s) to consider:

Thank you for your contribution! Sashiko AI review found 4 potential issue(s) to consider:

New issues:
- [Critical] Incomplete Device Reset / Cross-VM State Leak due to ineffective D3hot fallback
- [High] Logic Error / Resource Re-entry via double invocation of pci_dev_reset_iommu_prepare()

Pre-existing issues:
- [High] Missing Device Readiness Wait after D3cold->D0 transition
- [High] Lock Ordering Deadlock between device_lock and pci_bus_sem --

commit 3c339ed7150450f08a8ac36c7607f84ee659f04d
Author: Jose Ignacio Tornos Martinez <[email protected]>

PCI: Add device-specific reset for Qualcomm devices

This commit adds device-specific reset entries for several Qualcomm devices that lack working reset methods for VFIO passthrough scenarios. It extracts a shared helper function to perform a D3cold power cycle with an automatic fallback to D3hot.

Quoted 4 lines
drivers/pci/pci.c +0 -0
index 096868f80cd4c..f6be5c58cc91d 100644

[ ... ]

Quoted 12 lines
drivers/pci/pci.c +8 -0
@@ -4491,6 +4491,40 @@ static int pci_pm_reset(struct pci_dev *dev, bool probe)
 	return ret;
 }
 
+/**
+ * pci_dev_d3cold_d0_cycle - Perform D3cold->D0 power cycle
+ * @dev: Device to power cycle
+ *
+ * Common helper to perform D3cold->D0 power cycle for reset methods.
+ * Attempts D3cold transition with automatic fallback to D3hot on platforms
+ * without ACPI _PR3 power resources. Handles IOMMU preparation and cleanup.
+ *

drivers/pci/pci.c static int pci_pm_reset(struct pci_dev *dev, bool probe) · line 4511

Quoted 10 lines
drivers/pci/pci.c +10 -0
+ * Returns 0 on success, negative error code on failure.
+ */
+int pci_dev_d3cold_d0_cycle(struct pci_dev *dev)
+{
+	int ret;
+
+	if (dev->current_state != PCI_D0)
+		return -EINVAL;
+
+	ret = pci_dev_reset_iommu_prepare(dev);

[Severity: High]
Does this result in a double invocation of the IOMMU preparation routine?

The PCI core invokes device-specific reset quirks through __pci_dev_specific_reset(), which explicitly calls pci_dev_reset_iommu_prepare() before invoking the device's reset callback.

If the IOMMU subsystem's implementation checks the domain state and is not re-entrant, will this unconditional second call in the helper cause the reset to unconditionally fail with -EBUSY for devices attached to an IOMMU?

drivers/pci/pci.c static int pci_pm_reset(struct pci_dev *dev, bool probe) · line 4521

Quoted 10 lines
drivers/pci/pci.c +10 -0
+	if (ret) {
+		pci_err(dev, "failed to stop IOMMU for a PCI reset: %d\n", ret);
+		return ret;
+	}
+
+	ret = pci_set_power_state(dev, PCI_D3cold);
+	if (ret)
+		goto done;
+
+	ret = pci_set_power_state(dev, PCI_D0);

[Severity: Critical]
The commit message notes these devices advertise NoSoftRst+, meaning PM soft resets are blocked. If the platform lacks ACPI _PR3 power resources and pci_set_power_state() falls back to PCI_D3hot, does this transition sequence actually reset the device?

Because the D3hot fallback completes without error, it appears to return 0 (success) while falsely signaling to callers like VFIO that the device has been successfully reset. Can this result in assigning an un-reset, stateful device to a new VM?

[Severity: High]
This is a pre-existing issue, but should there be a polling delay after the D3cold to D0 transition to handle Configuration Request Retry Status?

A transition from D3cold to D0 acts as a Fundamental Reset. The helper calls pci_set_power_state() for PCI_D0 which applies PM delays, but does not poll for readiness. Can subsequent configuration accesses be sent to an unready device, causing Unsupported Requests or host Master Aborts?

[Severity: High]
This is a pre-existing issue, but does this sequence risk an AB-BA deadlock between device_lock and pci_bus_sem?

When a device reset is triggered via sysfs or VFIO, the lock order is:
pci_reset_function() [acquires device_lock]
-> pci_dev_d3cold_d0_cycle()

    -> pci_set_power_state()
      -> __pci_set_power_state()
        -> pcie_aspm_pm_state_change() [acquires pci_bus_sem]

Conversely, the AER recovery path lock order is:
pci_walk_bus() [acquires pci_bus_sem]
-> report_error_detected() [acquires device_lock]

Could an AER event occurring concurrently with a device reset trigger a deadlock here?

Quoted 5 lines
drivers/pci/pci.c +5 -0
+
+done:
+	pci_dev_reset_iommu_done(dev);
+	return ret;
+}
Signature · 1 line
Sashiko AI review · https://sashiko.dev/#/patchset/[email protected]?part=2
#5 lore raw

PATCH v5 3/3 PCI: Disable broken bus reset on Qualcomm devices

In reply to Jose Ignacio Tornos Martinez

Some Qualcomm PCIe devices (ath11k WiFi, ath12k WiFi, SDX62/SDX65 modems) do not properly support Secondary Bus Reset (SBR).

Testing confirms this is device-specific, not deployment-specific:
MediaTek MT7925e successfully uses bus reset through the same passive M.2-to-PCIe adapters where Qualcomm devices fail, proving PERST# is properly wired through the adapters.

This quirk acts as a safety net, preventing the broken bus reset from being attempted if users override reset methods (device_specific or d3cold when available) via sysfs.

---
v5: Quirk code unchanged from v4
v4: https://lore.kernel.org/all/[email protected]/

 drivers/pci/quirks.c | 3 +++
 1 file changed, 3 insertions(+)
drivers/pci/quirks.c +3 -0
index 000000000000..111111111111 100644
@@ -3789,6 +3789,9 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_ATHEROS, 0x0030, quirk_no_bus_reset);
 DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_ATHEROS, 0x0032, quirk_no_bus_reset);
 DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_ATHEROS, 0x003c, quirk_no_bus_reset);
 DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_ATHEROS, 0x0033, quirk_no_bus_reset);
 DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_ATHEROS, 0x0034, quirk_no_bus_reset);
 DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_ATHEROS, 0x003e, quirk_no_bus_reset);
+DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_QCOM, 0x1103, quirk_no_bus_reset); /* ath11k */
+DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_QCOM, 0x1107, quirk_no_bus_reset); /* ath12k */
+DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_QCOM, 0x0308, quirk_no_bus_reset); /* SDX62/SDX65 */
 

/*
* Root port on some Cavium CN8xxx chips do not successfully complete a bus
--
2.53.0