Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
To: "Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Jingoo Han" <jingoohan1@gmail.com>,
	"Krishna Chaitanya Chundru" <krishna.chundru@oss.qualcomm.com>
Cc: linux-pci@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org, mayank.rana@oss.qualcomm.com,
	quic_vbadigan@quicinc.com, Shawn Lin <shawn.lin@rock-chips.com>
Subject: Re: [PATCH v5 0/3] PCI: qcom: Program T_POWER_ON value for L1.2 exit timing
Date: Fri, 15 May 2026 22:22:32 +0530	[thread overview]
Message-ID: <177886395239.8489.6933092111755683572.b4-ty@kernel.org> (raw)
In-Reply-To: <20260428-t_power_on_fux-v5-0-f1ef926a91ff@oss.qualcomm.com>


On Tue, 28 Apr 2026 14:07:14 +0530, Krishna Chaitanya Chundru wrote:
> The T_POWER_ON indicates the time (in μs) that a Port requires the port
> on the opposite side of Link to wait in L1.2.Exit after sampling CLKREQ#
> asserted before actively driving the interface. This value is used by
> the ASPM driver to compute the LTR_L1.2_THRESHOLD.
> 
> Currently, qcom root port exposes T_POWER_ON value of zero in the L1SS
> capability registers, leading to incorrect LTR_L1.2_THRESHOLD calculations,
> which can result in improper L1.2 exit behavior and can trigger AER's.
> 
> [...]

Applied, thanks!

[1/3] PCI/ASPM: Add helper to encode L1SS T_POWER_ON fields
      commit: ea803322d3a8ec4ba60699a21b4ddc8fdbc0a242
[2/3] PCI: dwc: Add helper to Program T_POWER_ON
      commit: a66a25538564850a977ee3cfc795aa05ac4f1700
[3/3] PCI: qcom: Program T_POWER_ON
      commit: fca5f83fa339b357311ed250ec8041bbae11f66d

Best regards,
-- 
Manivannan Sadhasivam <mani@kernel.org>


      parent reply	other threads:[~2026-05-15 16:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28  8:37 [PATCH v5 0/3] PCI: qcom: Program T_POWER_ON value for L1.2 exit timing Krishna Chaitanya Chundru
2026-04-28  8:37 ` [PATCH v5 1/3] PCI/ASPM: Add helper to encode L1SS T_POWER_ON fields Krishna Chaitanya Chundru
2026-04-28  9:27   ` Ilpo Järvinen
2026-04-29  3:04     ` Krishna Chaitanya Chundru
2026-05-13 12:54       ` Manivannan Sadhasivam
2026-05-14 16:17   ` Bjorn Helgaas
2026-05-15 16:52     ` Manivannan Sadhasivam
2026-04-28  8:37 ` [PATCH v5 2/3] PCI: dwc: Add helper to Program T_POWER_ON Krishna Chaitanya Chundru
2026-04-28  8:37 ` [PATCH v5 3/3] PCI: qcom: " Krishna Chaitanya Chundru
2026-05-14 16:18   ` Bjorn Helgaas
2026-05-13 12:52 ` [PATCH v5 0/3] PCI: qcom: Program T_POWER_ON value for L1.2 exit timing Manivannan Sadhasivam
2026-05-15 16:52 ` 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=177886395239.8489.6933092111755683572.b4-ty@kernel.org \
    --to=manivannan.sadhasivam@oss.qualcomm.com \
    --cc=bhelgaas@google.com \
    --cc=jingoohan1@gmail.com \
    --cc=krishna.chundru@oss.qualcomm.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=mayank.rana@oss.qualcomm.com \
    --cc=quic_vbadigan@quicinc.com \
    --cc=robh@kernel.org \
    --cc=shawn.lin@rock-chips.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