Linux PCI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Qiang Yu" <qiang.yu@oss.qualcomm.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: qcom: Clear Attention Button Present in Slot Capabilities
Date: Fri, 10 Jul 2026 13:30:23 +0000	[thread overview]
Message-ID: <20260710133023.CF76A1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260710-clear_abp_0710-v1-1-efd63ebdaa09@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:

Pre-existing issues:
- [High] The patch attempts to fix PCIe surprise hot-plug by clearing the Attention Button Present (ABP) bit, but fails to apply this fix to platforms using the v2.3.3 and v2.9.0 init sequences, leaving hot-plug broken on these platforms.
--

--- Patch [1]: [PATCH] PCI: qcom: Clear Attention Button Present in Slot Capabilities ---
commit 65069d64a9bc5c0ab8831d1f4774fc266f4a082e
Author: Qiang Yu <qiang.yu@oss.qualcomm.com>
Subject: PCI: qcom: Clear Attention Button Present in Slot Capabilities

Qcom PCIe Root Ports advertise the Attention Button Present (ABP) bit in
the Slot Capabilities register, but the slots have no attention button.
This patch clears the ABP bit so that presence detect changes can be
reported, allowing surprise hot-plug detection to work.

> diff --git a/drivers/pci/controller/dwc/pcie-qcom.c b/drivers/pci/controller/dwc/pcie-qcom.c
> index b193c989b2b80..89c2d4cb1fbeb 100644
> --- a/drivers/pci/controller/dwc/pcie-qcom.c
> +++ b/drivers/pci/controller/dwc/pcie-qcom.c

[ ... ]

> @@ -372,6 +372,11 @@ static void qcom_pcie_set_slot_nccs(struct dw_pcie *pci)
>  	 */
>  	val = readl(pci->dbi_base + offset + PCI_EXP_SLTCAP);
>  	val |= PCI_EXP_SLTCAP_NCCS;
> +	/*
> +	 * Qcom PCIe Root Ports do not support Attention Button, so clear
> +	 * Attention Button Present in Slot Capabilities.
> +	 */
> +	val &= ~PCI_EXP_SLTCAP_ABP;
>  	writel(val, pci->dbi_base + offset + PCI_EXP_SLTCAP);
>  
>  	dw_pcie_dbi_ro_wr_dis(pci);

[Severity: High]
This is a pre-existing issue, but does this fix need to cover platforms
using the v2.3.3 and v2.9.0 init sequences as well?

While this patch clears the Attention Button Present (ABP) bit in
qcom_pcie_set_slot_cap(), platforms using qcom_pcie_post_init_2_3_3() and
qcom_pcie_post_init_2_9_0() appear to bypass this fix.

Looking at drivers/pci/controller/dwc/pcie-qcom.c, these platforms use a
hardcoded macro that explicitly sets the ABP bit:

#define PCIE_CAP_SLOT_VAL			(PCI_EXP_SLTCAP_ABP | \
...

qcom_pcie_post_init_2_3_3() {
    ...
    writel(PCIE_CAP_SLOT_VAL, pci->dbi_base + offset + PCI_EXP_SLTCAP);
    ...
}

Will this leave PCIe surprise hot-plug broken on these platforms, since
the ABP bit remains set in their slot capabilities?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260710-clear_abp_0710-v1-1-efd63ebdaa09@oss.qualcomm.com?part=1

  reply	other threads:[~2026-07-10 13:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10 13:20 [PATCH] PCI: qcom: Clear Attention Button Present in Slot Capabilities Qiang Yu
2026-07-10 13:30 ` sashiko-bot [this message]
2026-07-10 15:14 ` Konrad Dybcio
2026-07-10 17:30 ` Bjorn Helgaas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260710133023.CF76A1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=qiang.yu@oss.qualcomm.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox