From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: "Manivannan Sadhasivam" <manivannan.sadhasivam@oss.qualcomm.com>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Qiang Yu" <qiang.yu@oss.qualcomm.com>,
"Xilin Wu" <sophon@radxa.com>
Cc: linux-pci@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] PCI: qcom: Block accesses to downstream devices on link down
Date: Tue, 1 Sep 2026 14:39:49 +0200 [thread overview]
Message-ID: <74c0fc35-a56d-4297-9fcb-23e2df8646c3@oss.qualcomm.com> (raw)
In-Reply-To: <178826612782.58092.15490835074765422013.b4-ty@b4>
On 9/1/26 2:35 PM, Manivannan Sadhasivam wrote:
>
> On Wed, 19 Aug 2026 23:36:54 -0700, Qiang Yu wrote:
>> After a PCIe link goes down, software may still access the BAR (MMIO)
>> space or configuration space of devices behind that link before recovery
>> has run. As the link is down, these accesses never complete, resulting in
>> a storm of Completion Timeout AERs.
>>
>> Use the controller's ECAM blocker to drop these accesses to the PCIe
>> address space as soon as the link-down interrupt fires, so that Completion
>> Timeout AERs are reduced. The blocked range covers the entire address
>> space (base 0x0, all-ones limit), since the Root Port's own DBI/iATU
>> register space remains accessible regardless.
>>
>> [...]
>
> Applied, thanks!
>
> [1/1] PCI: qcom: Block accesses to downstream devices on link down
> commit: 86624b718f94517b26f96c1d7beb7632e5562afd
Could this be a fix for
https://lore.kernel.org/linux-arm-msm/b461c125-947b-4e06-b502-abb354e0cba6@oss.qualcomm.com/
?
(+Xilin)
Konrad
next prev parent reply other threads:[~2026-09-01 12:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 6:36 [PATCH v2] PCI: qcom: Block accesses to downstream devices on link down Qiang Yu
2026-08-20 6:52 ` sashiko-bot
2026-08-20 11:29 ` Konrad Dybcio
2026-09-01 12:35 ` Manivannan Sadhasivam
2026-09-01 12:39 ` Konrad Dybcio [this message]
2026-09-01 14:06 ` Xilin Wu
2026-09-03 7:50 ` Krishna Chaitanya Chundru
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=74c0fc35-a56d-4297-9fcb-23e2df8646c3@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=bhelgaas@google.com \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=manivannan.sadhasivam@oss.qualcomm.com \
--cc=qiang.yu@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=sophon@radxa.com \
/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