public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wei Huang <wei.huang2@amd.com>
To: George Abraham P <george.abraham.p@intel.com>
Cc: Leon Romanovsky <leon@kernel.org>,
	bhelgaas@google.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, giovanni.cabiddu@intel.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>
Subject: Re: [PATCH V2 RESEND] PCI/TPH: Skip Root Port completer check for RC_END devices
Date: Fri, 27 Feb 2026 01:08:02 -0600	[thread overview]
Message-ID: <aaFC0pJDq5JW_ZAy@weiserver> (raw)
In-Reply-To: <561a71f3-dca9-49d7-a9cb-13c916340ad3@intel.com>

On Wed, Feb 18, 2026 at 09:00:59PM +0530, George Abraham P wrote:
> Hi Leon,
> 
> On 18-Feb-26 2:12 PM, Leon Romanovsky wrote:
> > On Wed, Feb 18, 2026 at 10:24:28AM +0530, George Abraham P wrote:
> >> [+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
> > 
> > I do not have a strong preference; I am fine with adding a Fixes tag or
> > leaving it out. Up to commit 2961f841b025, pcie_enable_tph() is called
> > in two drivers: bnxt and mlx5. Which of these devices is the RC_END
> > device?
> > 
> > Thanks
> 
> qat_6xxx supports TPH and is a RC_END device. The patches to enable TPH on qat_6xxx is yet to be reviewed. However, it requires this fix for the same to work.
> 

The patche looks fine to me - it shouldn't affect regular PCI Express Endpoint (type 0000b) devices.

> Thanks,
> George

  reply	other threads:[~2026-02-27  7:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09  5:29 [PATCH V2 RESEND] PCI/TPH: Skip Root Port completer check for RC_END devices George Abraham P
2026-02-18  4:54 ` George Abraham P
2026-02-18  8:42   ` Leon Romanovsky
2026-02-18 15:30     ` George Abraham P
2026-02-27  7:08       ` Wei Huang [this message]
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=aaFC0pJDq5JW_ZAy@weiserver \
    --to=wei.huang2@amd.com \
    --cc=Eric.VanTassell@amd.com \
    --cc=bhelgaas@google.com \
    --cc=george.abraham.p@intel.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=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