From: sashiko-bot@kernel.org
To: "Guangshuo Li" <lgs201920130244@gmail.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: qcom-ep: deinitialize endpoint on remove
Date: Wed, 16 Sep 2026 09:11:10 +0000 [thread overview]
Message-ID: <20260916091110.A6A511F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260916090126.2963064-1-lgs201920130244@gmail.com>
> qcom_pcie_ep_probe() initializes the DesignWare PCIe endpoint with
> dw_pcie_ep_init(). The probe failure paths call dw_pcie_ep_deinit() to
> release the corresponding endpoint resources, but the remove path does
> not perform the matching teardown after a successful probe.
>
> As a result, resources initialized by the DesignWare endpoint core can
> remain allocated when the endpoint controller is removed.
>
> Notify endpoint functions about EPC deinitialization and call
> dw_pcie_ep_deinit() before disabling the controller resources. Keep the
> existing early return when the link is already disabled since Qualcomm
> endpoint controllers depend on the host refclk for hardware cleanup.
>
> This issue was found by manual code inspection.
>
> Fixes: f55fee56a631 ("PCI: qcom-ep: Add Qualcomm PCIe Endpoint controller driver")
> Cc: stable@vger.kernel.org
> Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260916090126.2963064-1-lgs201920130244@gmail.com?part=1
prev parent reply other threads:[~2026-09-16 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 9:01 [PATCH] PCI: qcom-ep: deinitialize endpoint on remove Guangshuo Li
2026-09-16 9:11 ` sashiko-bot [this message]
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=20260916091110.A6A511F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=lgs201920130244@gmail.com \
--cc=linux-pci@vger.kernel.org \
--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