[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210527120531.GB213718@rocinante.localdomain>
Date: Thu, 27 May 2021 14:05:31 +0200
From: Krzysztof WilczyĆski <kw@...ux.com>
To: Om Prakash Singh <omp@...dia.com>
Cc: vidyas@...dia.com, lorenzo.pieralisi@....com, bhelgaas@...gle.com,
thierry.reding@...il.com, jonathanh@...dia.com,
linux-tegra@...r.kernel.org, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, kthota@...dia.com,
mmaddireddy@...dia.com
Subject: Re: [RESEND PATCH V1 4/5] PCI: tegra: Don't allow suspend when Tegra
PCIe is in EP mode
Hi Prakash
[...]
> @@ -2276,6 +2276,11 @@ static int tegra_pcie_dw_suspend_late(struct device *dev)
[...]
> + if (pcie->mode == DW_PCIE_EP_TYPE) {
> + dev_err(dev, "Tegra PCIe is in EP mode, suspend not allowed");
> + return -EPERM;
> + }
Would the -EINVAL be more appropriate here? It seem more appropriate
when something is an invalid operation, rather than access to the
resource being denied (or something along these lines), what do you
think?
Krzysztof
Powered by blists - more mailing lists