mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <mani@kernel.org>
To: bhelgaas@google.com, lpieralisi@kernel.org,
	kwilczynski@kernel.org,  Hans Zhang <18255117159@163.com>
Cc: robh@kernel.org, mpillai@cadence.com, a-garg7@ti.com,
	 s-vadapalli@ti.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 0/3] PCI: cadence: Add LTSSM debugfs
Date: Wed, 15 Jul 2026 09:39:01 +0200	[thread overview]
Message-ID: <178410114155.126778.6712169476306452015.b4-ty@b4> (raw)
In-Reply-To: <20260701073513.1101559-1-18255117159@163.com>


On Wed, 01 Jul 2026 15:35:09 +0800, Hans Zhang wrote:
> This series adds debugfs support to the Cadence PCIe controller driver,
> allowing users to read the current LTSSM state of the link for debugging
> purposes.
> 
> Patch 1 introduces a new flag 'is_hpa' in the cdns_pcie structure to
> distinguish HPA (High Performance Architecture) IP platforms from LGA
> (Legacy Architecture) IP platforms, as they have different register
> layouts for LTSSM status.
> 
> [...]

Applied, thanks!

[1/3] PCI: cadence: Add HPA architecture flag
      commit: b5672f9463f2ee184730daaa5c43b9b5e8fb9f86
[2/3] PCI: cadence: Add HPA IP debugfs for LTSSM status
      commit: ea34744eb0949c7b1e53aea579f5a3e2d2b88d63
[3/3] PCI: cadence: Add LGA IP debugfs for LTSSM status
      commit: d70e964dc099821f6c159d8f40aa7be2c62ecfd2

Best regards,
-- 
மணிவண்ணன் சதாசிவம்



      parent reply	other threads:[~2026-07-15  7:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01  7:35 Hans Zhang
2026-07-01  7:35 ` [PATCH v8 1/3] PCI: cadence: Add HPA architecture flag Hans Zhang
2026-07-01  7:35 ` [PATCH v8 2/3] PCI: cadence: Add HPA IP debugfs for LTSSM status Hans Zhang
2026-07-01  7:35 ` [PATCH v8 3/3] PCI: cadence: Add LGA " Hans Zhang
2026-07-15  7:39 ` Manivannan Sadhasivam [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=178410114155.126778.6712169476306452015.b4-ty@b4 \
    --to=mani@kernel.org \
    --cc=18255117159@163.com \
    --cc=a-garg7@ti.com \
    --cc=bhelgaas@google.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mpillai@cadence.com \
    --cc=robh@kernel.org \
    --cc=s-vadapalli@ti.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

Powered by JetHome