[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e8f0b236-dfb3-c9cf-4683-c43e8bc0c0b4@nvidia.com>
Date: Mon, 12 Jul 2021 19:51:41 -0500
From: Shanker R Donthineni <sdonthineni@...dia.com>
To: Alex Williamson <alex.williamson@...hat.com>
CC: Amey Narkhede <ameynarkhede03@...il.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Raphael Norwitz <raphael.norwitz@...anix.com>,
<linux-pci@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<kw@...ux.com>, Sinan Kaya <okaya@...nel.org>,
Len Brown <lenb@...nel.org>,
"Rafael J . Wysocki" <rjw@...ysocki.net>
Subject: Re: [PATCH v10 7/8] PCI: Add support for ACPI _RST reset method
Hi Alex,
On 7/12/21 6:09 PM, Alex Williamson wrote:
>> +/**
>> + * pci_dev_acpi_reset - do a function level reset using _RST method
>> + * @dev: device to reset
>> + * @probe: check if _RST method is included in the acpi_device context.
>> + */
>> +int pci_dev_acpi_reset(struct pci_dev *dev, int probe)
>> +{
>> + acpi_handle handle = ACPI_HANDLE(&dev->dev);
>> +
>> + if (!handle || !acpi_has_method(handle, "_RST"))
>> + return -ENOTTY;
>> +
>> + if (probe)
>> + return 0;
>> +
>> + if (ACPI_FAILURE(acpi_evaluate_object(handle, "_RST", NULL, NULL))) {
>> + pci_warn(dev, "ACPI _RST failed\n");
>> + return -EINVAL;
> Should we return -ENOTTY here instead to give a possible secondary
> reset method a chance? Thanks,
Thanks for reviewing patches.
ACPI/AML _RST method type is VOID. The only possibility of failure would be
either system is running out of memory or bugs in ACPICA. There is no strong
reason not to return -NOTTY.
I'll fix in the next version. Is there opportunity to include reset feature in v5.14-rc2?
Can I add your reviewed-by since no other comments to this patch?
-Shanker
Powered by blists - more mailing lists