[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAKfTPtADp2cxgXGOAVfHKtQ5Sb4MNTBJ4FAwKNgpvvkxtOupdQ@mail.gmail.com>
Date: Tue, 13 Jan 2026 18:53:33 +0100
From: Vincent Guittot <vincent.guittot@...aro.org>
To: manivannan.sadhasivam@....qualcomm.com
Cc: Jingoo Han <jingoohan1@...il.com>, Manivannan Sadhasivam <mani@...nel.org>,
Lorenzo Pieralisi <lpieralisi@...nel.org>, Krzysztof WilczyĆski <kwilczynski@...nel.org>,
Rob Herring <robh@...nel.org>, Bjorn Helgaas <bhelgaas@...gle.com>, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, zhangsenchuan@...incomputing.com,
Shawn Lin <shawn.lin@...k-chips.com>, Richard Zhu <hongxing.zhu@....com>,
Frank Li <Frank.Li@....com>
Subject: Re: [PATCH v4 0/6] PCI: dwc: Rework the error handling of
dw_pcie_wait_for_link() API
On Wed, 7 Jan 2026 at 09:12, Manivannan Sadhasivam via B4 Relay
<devnull+manivannan.sadhasivam.oss.qualcomm.com@...nel.org> wrote:
>
> Hi,
>
> This series reworks the dw_pcie_wait_for_link() API to allow the callers to
> detect the absence of the device on the bus and skip the failure.
>
> Compared to v2, I've reworked the patch 2 to improve the API further and
> dropped the patch 1 that got applied (hence changed the subject). I've also
> modified the error code based on the feedback in v2 to return -ENODEV if device
> is not detected on the bus and -ETIMEDOUT otherwise. This allows the callers to
> skip the failure if device is not detected and handle error for other failure.
>
> Testing
> =======
>
> Tested this series on Rb3Gen2 board without powering on the PCIe switch. Now the
> dw_pcie_wait_for_link() API prints:
>
> qcom-pcie 1c08000.pcie: Device not found
>
> Instead of the previous log:
>
> qcom-pcie 1c08000.pcie: Phy link never came up
>
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@....qualcomm.com>
FWIW I tested it on s32g399a-rdb3 with a ssd on pcie0 and nothing on pcie1
Tested-By: Vincent Guittot <vincent.guittot@...aro.org>
> ---
> Changes in v4:
> - Skipped returning failure during resume as well if no device is found
> - Link to v3: https://lore.kernel.org/r/20251230-pci-dwc-suspend-rework-v3-0-40cd485714f5@oss.qualcomm.com
>
> Changes in v3:
> - Dropped patch 1 that got appplied
> - Reworked the error handling of dw_pcie_wait_for_link() API further
> - Link to v2: https://lore.kernel.org/r/20251218-pci-dwc-suspend-rework-v2-0-5a7778c6094a@oss.qualcomm.com
>
> Changes in v2:
> - Changed the logic to check for Detect.Quiet/Active states
> - Collected tags and rebased on top of v6.19-rc1
> - Link to v1: https://lore.kernel.org/r/20251119-pci-dwc-suspend-rework-v1-0-aad104828562@oss.qualcomm.com
>
> ---
> Manivannan Sadhasivam (6):
> PCI: dwc: Return -ENODEV from dw_pcie_wait_for_link() if device is not found
> PCI: dwc: Rename and move ltssm_status_string() to pcie-designware.c
> PCI: dwc: Rework the error print of dw_pcie_wait_for_link()
> PCI: dwc: Only skip the dw_pcie_wait_for_link() failure if it returns -ENODEV
> PCI: host-common: Add an API to check for any device under the Root Ports
> PCI: dwc: Skip failure during dw_pcie_resume_noirq() if no device is available
>
> .../pci/controller/dwc/pcie-designware-debugfs.c | 54 +---------------
> drivers/pci/controller/dwc/pcie-designware-host.c | 23 +++++--
> drivers/pci/controller/dwc/pcie-designware.c | 75 +++++++++++++++++++++-
> drivers/pci/controller/dwc/pcie-designware.h | 2 +
> drivers/pci/controller/pci-host-common.c | 21 ++++++
> drivers/pci/controller/pci-host-common.h | 2 +
> 6 files changed, 115 insertions(+), 62 deletions(-)
> ---
> base-commit: 68ac85fb42cfeb081cf029acdd8aace55ed375a2
> change-id: 20251119-pci-dwc-suspend-rework-8b0515a38679
>
> Best regards,
> --
> Manivannan Sadhasivam <manivannan.sadhasivam@....qualcomm.com>
>
>
Powered by blists - more mailing lists