External email: Use caution opening links or attachmentsThanks Sinan/Alex, Agree ACPI _RST is a generic method applicable
On Fri, 23 Apr 2021 11:12:05 -0400
Sinan Kaya <okaya@xxxxxxxxxx> wrote:
+Alex,Agreed, we should add a new function level reset method for this rather
On 4/23/2021 10:54 AM, Shanker Donthineni wrote:
+static int reset_nvidia_gpu_quirk(struct pci_dev *dev, int probe)Interesting, some pieces of this function (especially the ACPI _RST)
+{
+#ifdef CONFIG_ACPI
+ acpi_handle handle = ACPI_HANDLE(&dev->dev);
+
+ /*
+ * Check for the affected devices' ID range. If device is not in
+ * the affected range, return -ENOTTY indicating no device
+ * specific reset method is available.
+ */
+ if ((dev->device & 0xffc0) != 0x2340)
+ return -ENOTTY;
+
+ /*
+ * Return -ENOTTY indicating no device-specific reset method if _RST
+ * method is not defined
+ */
+ if (!handle || !acpi_has_method(handle, "_RST"))
+ return -ENOTTY;
+
+ /* Return 0 for probe phase indicating that we can reset this device */
+ if (probe)
+ return 0;
+
+ /* Invoke _RST() method to perform the device-specific reset */
+ if (ACPI_FAILURE(acpi_evaluate_object(handle, "_RST", NULL, NULL))) {
+ pci_warn(dev, "Failed to reset the device\n");
+ return -EINVAL;
+ }
+ return 0;
+#else
+ return -ENOTTY;
+#endif
+}
could be generalized.
than a device specific reset. At that point the extent of the device
specific quirk could be to restrict SBR.
It'd be useful to know whatThese are not plug-in PCIe GPU cards, will exist on upcoming
these devices are (not in pciids yet), why we expect to only see them in
specific platforms (embedded device?), and the failure mode of the SBR.
Thanks,
Alex