diff options
| author | Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com> | 2026-06-16 21:45:19 +0530 |
|---|---|---|
| committer | Manivannan Sadhasivam <mani@kernel.org> | 2026-07-07 07:24:16 +0200 |
| commit | 3edb3a038d423480efeb204dbc6ddc9a292f8ecb (patch) | |
| tree | d3653dbb2eafd7a6ad9bcabe9160b60e41ac0911 /scripts/Makefile.thinlto | |
| parent | 533171173882ca88195c3c2e7396454457b05fd6 (diff) | |
| download | linux-stable-3edb3a038d423480efeb204dbc6ddc9a292f8ecb.tar.gz linux-stable-3edb3a038d423480efeb204dbc6ddc9a292f8ecb.zip | |
PCI: qcom: Skip PERST# GPIOs provided by downstream PCIe devices
Currently, the pcie-qcom driver recursively parses the PERST# GPIO from all
child nodes defined in DT and acquires them. But this creates issues with
PERST# GPIO provided by one of the child devices like the PCIe switch port.
In this case, the RC driver cannot acquire the PERST# GPIO since it will be
provided by the child PCIe device which was not yet enumerated during RC
driver probe.
Fix this by checking if the GPIO provider is a child of the RC's DT node
(i.e., sits behind this PCIe controller). If so, skip it, as PERST#
should be controlled by the respective PCIe client driver implementation.
GPIOs provided by external GPIO controllers (e.g., TLMM in Qcom SoCs)
continue to be handled normally.
Fixes: 2fd60a2edb83 ("PCI: qcom: Parse PERST# from all PCIe bridge nodes")
Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
Signed-off-by: Manivannan Sadhasivam <mani@kernel.org>
Link: https://patch.msgid.link/20260616-pci-qcom-perst-fix-v1-1-27600d6ae357@oss.qualcomm.com
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions
