From: George Abraham P <george.abraham.p@intel.com>
To: <bhelgaas@google.com>
Cc: <linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<giovanni.cabiddu@intel.com>, Wei Huang <wei.huang2@amd.com>,
Jing Liu <jing2.liu@intel.com>,
Paul Luse <paul.e.luse@linux.intel.com>,
"Eric Van Tassell" <Eric.VanTassell@amd.com>,
Yishai Hadas <yishaih@nvidia.com>,
"Leon Romanovsky" <leon@kernel.org>
Subject: Re: [PATCH V2 RESEND] PCI/TPH: Skip Root Port completer check for RC_END devices
Date: Wed, 18 Feb 2026 10:24:28 +0530 [thread overview]
Message-ID: <564e872c-ecc0-479c-86c3-68b5d3fda512@intel.com> (raw)
In-Reply-To: <20260109052923.1170070-1-george.abraham.p@intel.com>
[+cc TPH authors that were missed in the previous mail]
On 09-Jan-26 10:59 AM, George Abraham P wrote:
> Root Complex Integrated Endpoint devices (PCI_EXP_TYPE_RC_END) are
> directly integrated into the root complex and do not have an
> associated Root Port in the traditional PCIe hierarchy. The current
> TPH implementation incorrectly attempts to find and check a Root Port's
> TPH completer capability for these devices.
>
> Add a check to skip Root Port completer type verification for RC_END
> devices, allowing them to use their full TPH requester capability
> without being limited by a non-existent Root Port's completer support.
>
> For RC_END devices, the root complex itself acts as the TPH completer,
> and this relationship is handled differently than the standard
> endpoint-to-Root-Port model.
>
> Fixes: f69767a1ada3 ("PCI: Add TLP Processing Hints (TPH) support")
> Signed-off-by: George Abraham P <george.abraham.p@intel.com>
> ---
> v1->v2:
> - Added "Fixes:" tag to link the commit hash that introduced the code
> ---
> drivers/pci/tph.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/pci/tph.c b/drivers/pci/tph.c
> index ca4f97be7538..e896b3958281 100644
> --- a/drivers/pci/tph.c
> +++ b/drivers/pci/tph.c
> @@ -407,10 +407,13 @@ int pcie_enable_tph(struct pci_dev *pdev, int mode)
> else
> pdev->tph_req_type = PCI_TPH_REQ_TPH_ONLY;
>
> - rp_req_type = get_rp_completer_type(pdev);
> + /* Check if the device is behind a Root Port */
> + if (pci_pcie_type(pdev) != PCI_EXP_TYPE_RC_END) {
> + rp_req_type = get_rp_completer_type(pdev);
>
> - /* Final req_type is the smallest value of two */
> - pdev->tph_req_type = min(pdev->tph_req_type, rp_req_type);
> + /* Final req_type is the smallest value of two */
> + pdev->tph_req_type = min(pdev->tph_req_type, rp_req_type);
> + }
>
> if (pdev->tph_req_type == PCI_TPH_REQ_DISABLE)
> return -EINVAL;
next prev parent reply other threads:[~2026-02-18 4:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 5:29 George Abraham P
2026-02-18 4:54 ` George Abraham P [this message]
2026-02-18 8:42 ` Leon Romanovsky
2026-02-18 15:30 ` George Abraham P
2026-02-27 7:08 ` Wei Huang
2026-02-18 20:58 ` 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=564e872c-ecc0-479c-86c3-68b5d3fda512@intel.com \
--to=george.abraham.p@intel.com \
--cc=Eric.VanTassell@amd.com \
--cc=bhelgaas@google.com \
--cc=giovanni.cabiddu@intel.com \
--cc=jing2.liu@intel.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=paul.e.luse@linux.intel.com \
--cc=wei.huang2@amd.com \
--cc=yishaih@nvidia.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
all inboxes | Powered by JetHome®