From: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: "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>,
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
Subject: Re: [PATCH v4 3/3] PCI: qcom: Program T_POWER_ON
Date: Tue, 28 Apr 2026 12:34:18 +0530 [thread overview]
Message-ID: <5233eb62-7b6c-45c6-b24c-af4db5248352@oss.qualcomm.com> (raw)
In-Reply-To: <hd3zmtaaetewdlki77jtqqfz2dzv2mad2dcqmssvqbagm3p62h@qihlc6xw4vqn>
On 4/10/2026 10:25 PM, Manivannan Sadhasivam wrote:
> On Sat, Apr 04, 2026 at 01:47:20PM +0530, Krishna Chaitanya Chundru wrote:
>> Some platforms have incorrect T_POWER_ON value programmed in hardware.
>> Generally these will be corrected by bootloaders, but not all targets
>> support bootloaders to program correct values due to that
>> LTR_L1.2_THRESHOLD value calculated by aspm driver can be wrong, which
>> can result in improper L1.2 exit behavior and if AER happens to be
>> supported and enabled, the error may be *reported* via AER.
>>
>> Parse "t-power-on-us" property from each root port node and program them
>> as part of host initialization using dw_pcie_program_t_power_on() before
>> link training.
>>
>> This property in added to the dtschema here[1].
>>
>> Signed-off-by: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
>> Link[1]: https://lore.kernel.org/all/20260205093346.667898-1-krishna.chundru@oss.qualcomm.com/
>> ---
>> drivers/pci/controller/dwc/pcie-qcom.c | 14 ++++++++++++++
>> 1 file changed, 14 insertions(+)
>>
>> diff --git a/drivers/pci/controller/dwc/pcie-qcom.c b/drivers/pci/controller/dwc/pcie-qcom.c
>> index 67a16af69ddc75fca1b123e70715e692a91a9135..a8f82f860c08fe2eabad2c0eed541b8dd121215e 100644
>> --- a/drivers/pci/controller/dwc/pcie-qcom.c
>> +++ b/drivers/pci/controller/dwc/pcie-qcom.c
>> @@ -269,6 +269,7 @@ struct qcom_pcie_perst {
>> struct qcom_pcie_port {
>> struct list_head list;
>> struct phy *phy;
>> + u32 l1ss_t_power_on;
>> struct list_head perst;
>> };
>>
>> @@ -1283,6 +1284,14 @@ static int qcom_pcie_phy_power_on(struct qcom_pcie *pcie)
>> return 0;
>> }
>>
>> +static void qcom_pcie_configure_ports(struct qcom_pcie *pcie)
>> +{
>> + struct qcom_pcie_port *port;
>> +
>> + list_for_each_entry(port, &pcie->ports, list)
>> + dw_pcie_program_t_power_on(pcie->pci, port->l1ss_t_power_on);
> Since this writes to the same register, there is no point in iterating over all
> ports. Add a TODO here also and write it only once.
we will iterate only once in case of single root port. so we are good here.
- Krishna Chaitanya.
>> +}
>> +
>> static int qcom_pcie_host_init(struct dw_pcie_rp *pp)
>> {
>> struct dw_pcie *pci = to_dw_pcie_from_pp(pp);
>> @@ -1317,6 +1326,8 @@ static int qcom_pcie_host_init(struct dw_pcie_rp *pp)
>> dw_pcie_remove_capability(pcie->pci, PCI_CAP_ID_MSIX);
>> dw_pcie_remove_ext_capability(pcie->pci, PCI_EXT_CAP_ID_DPC);
>>
>> + qcom_pcie_configure_ports(pcie);
>> +
>> qcom_pcie_perst_deassert(pcie);
>>
>> if (pcie->cfg->ops->config_sid) {
>> @@ -1759,6 +1770,9 @@ static int qcom_pcie_parse_port(struct qcom_pcie *pcie, struct device_node *node
>> if (ret)
>> return ret;
>>
>> + /* TODO: Need to move to dwc once multi root port support is added. */
> s/dwc/DWC core
>
> s/root port/Root Port
>
> - Mani
>
prev parent reply other threads:[~2026-04-28 7:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 8:17 [PATCH v4 0/3] PCI: qcom: Program T_POWER_ON value for L1.2 exit timing Krishna Chaitanya Chundru
2026-04-04 8:17 ` [PATCH v4 1/3] PCI/ASPM: Add helper to encode L1SS T_POWER_ON fields Krishna Chaitanya Chundru
2026-04-10 16:46 ` Manivannan Sadhasivam
2026-04-04 8:17 ` [PATCH v4 2/3] PCI: dwc: Add helper to Program T_POWER_ON Krishna Chaitanya Chundru
2026-04-04 8:17 ` [PATCH v4 3/3] PCI: qcom: " Krishna Chaitanya Chundru
2026-04-10 16:55 ` Manivannan Sadhasivam
2026-04-28 7:04 ` Krishna Chaitanya Chundru [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=5233eb62-7b6c-45c6-b24c-af4db5248352@oss.qualcomm.com \
--to=krishna.chundru@oss.qualcomm.com \
--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=mayank.rana@oss.qualcomm.com \
--cc=quic_vbadigan@quicinc.com \
--cc=robh@kernel.org \
/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