From: Niklas Cassel <cassel@kernel.org>
To: Qiang Yu <qiang.yu@oss.qualcomm.com>
Cc: "Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Jingoo Han" <jingoohan1@gmail.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
"Wenbin Yao" <wenbin.yao@oss.qualcomm.com>
Subject: Re: [PATCH 2/5] PCI: dwc: Add new APIs to remove standard and extended Capability
Date: Tue, 23 Dec 2025 08:24:26 +0100 [thread overview]
Message-ID: <aUpDqu8598J4yNHb@ryzen> (raw)
In-Reply-To: <20251109-remove_cap-v1-2-2208f46f4dc2@oss.qualcomm.com>
Hello Qiang Yu,
I just saw that this patch was queued up.
dw_pcie_remove_ext_capability() basically seems to be identical to:
dw_pcie_ep_hide_ext_capability(), only that your new function does
not require previous cap as an argument (so it seems better).
It seems a bit silly to have two functions that do the same thing,
perhaps you can send a patch that removes dw_pcie_ep_hide_ext_capability()
and updates the only user of that function to use your new function?
Sorry for not seeing this earlier.
Kind regards,
Niklas
On Sun, Nov 09, 2025 at 10:59:41PM -0800, Qiang Yu wrote:
> On some platforms, certain PCIe Capabilities may be present in hardware
> but are not fully implemented as defined in PCIe spec. These incomplete
> capabilities should be hidden from the PCI framework to prevent unexpected
> behavior.
>
> Introduce two APIs to remove a specific PCIe Capability and Extended
> Capability by updating the previous capability's next offset field to skip
> over the unwanted capability. These APIs allow RC drivers to easily hide
> unsupported or partially implemented capabilities from software.
>
> Co-developed-by: Wenbin Yao <wenbin.yao@oss.qualcomm.com>
> Signed-off-by: Wenbin Yao <wenbin.yao@oss.qualcomm.com>
> Signed-off-by: Qiang Yu <qiang.yu@oss.qualcomm.com>
> ---
> drivers/pci/controller/dwc/pcie-designware.c | 53 ++++++++++++++++++++++++++++
> drivers/pci/controller/dwc/pcie-designware.h | 2 ++
> 2 files changed, 55 insertions(+)
next prev parent reply other threads:[~2025-12-23 7:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 6:59 [PATCH 0/5] PCI: Remove unsupported or incomplete PCIe Capabilities Qiang Yu
2025-11-10 6:59 ` [PATCH 1/5] PCI: Add preceding capability position support and update drivers Qiang Yu
2025-11-10 6:59 ` [PATCH 2/5] PCI: dwc: Add new APIs to remove standard and extended Capability Qiang Yu
2025-12-23 7:24 ` Niklas Cassel [this message]
2025-12-24 6:20 ` Qiang Yu
2025-12-26 21:07 ` Bjorn Helgaas
2025-12-27 5:10 ` Manivannan Sadhasivam
2025-12-28 7:49 ` Qiang Yu
2026-01-09 7:59 ` Qiang Yu
2025-11-10 6:59 ` [PATCH 3/5] PCI: dwc: Remove MSI/MSIX capability if iMSI-RX is used as MSI controller Qiang Yu
2025-11-20 11:18 ` Manivannan Sadhasivam
2025-11-20 14:06 ` Shawn Lin
2025-11-20 17:00 ` Manivannan Sadhasivam
2025-11-21 4:04 ` Shawn Lin
2025-11-21 7:56 ` Qiang Yu
2025-11-28 9:57 ` Qiang Yu
2025-11-28 10:02 ` Shawn Lin
2025-12-04 1:27 ` Brian Norris
2025-12-26 21:25 ` Bjorn Helgaas
2025-12-27 4:58 ` Manivannan Sadhasivam
2025-12-04 1:51 ` Brian Norris
2025-12-18 7:31 ` Manivannan Sadhasivam
2025-12-26 21:31 ` Bjorn Helgaas
2025-12-27 5:21 ` Manivannan Sadhasivam
2025-12-28 7:02 ` Qiang Yu
2025-11-10 6:59 ` [PATCH 4/5] PCI: qcom: Remove MSI-X Capability for Root Ports Qiang Yu
2025-11-10 6:59 ` [PATCH 5/5] PCI: qcom: Remove DPC Extended Capability Qiang Yu
2025-12-18 7:35 ` [PATCH 0/5] PCI: Remove unsupported or incomplete PCIe Capabilities Manivannan Sadhasivam
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=aUpDqu8598J4yNHb@ryzen \
--to=cassel@kernel.org \
--cc=bhelgaas@google.com \
--cc=jingoohan1@gmail.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=qiang.yu@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=wenbin.yao@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.