From: Frank Li <Frank.li@oss.nxp.com>
To: Manikanta Maddireddy <mmaddireddy@nvidia.com>
Cc: lpieralisi@kernel.org, kwilczynski@kernel.org, mani@kernel.org,
bhelgaas@google.com, linux-pci@vger.kernel.org, robh@kernel.org,
thierry.reding@kernel.org, jonathanh@nvidia.com,
kishon@kernel.org, Frank.Li@kernel.org, vidyas@nvidia.com,
cassel@kernel.org, den@valinux.co.jp, marco.crivellari@suse.com,
andriy.shevchenko@linux.intel.com, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 06/10] PCI: tegra194: Check for L1SS capability before programming
Date: Wed, 21 Oct 2026 10:28:35 -0500 [thread overview]
Message-ID: <atjaI9HAoB_KBUaZ@SMW015318> (raw)
In-Reply-To: <20261021061349.1265704-7-mmaddireddy@nvidia.com>
On Wed, Oct 21, 2026 at 11:43:45AM +0530, Manikanta Maddireddy wrote:
> init_host_aspm() programs the L1 PM Substates capability without checking
> whether the controller advertises it. If the capability is absent, the
> code writes offsets from zero instead of L1SS registers.
>
> Check for the L1SS capability before programming L1SS-specific fields.
> Keep RAS-DES discovery, ASPM counter enablement and AFR latency
> programming outside that guard because they do not depend on L1SS.
> Only create the ASPM counter debugfs file when the RAS-DES capability is
> present.
>
> Fixes: 56e15a238d92 ("PCI: tegra: Add Tegra194 PCIe support")
> Signed-off-by: Manikanta Maddireddy <mmaddireddy@nvidia.com>
> ---
Reviewed-by: Frank Li <Frank.Li@nxp.com>
> Changes V1 -> V2:
> - Use RAS_DES_EVENT_COUNTER_CONTROL to match the preceding DWC register
> renames. No functional changes.
>
> drivers/pci/controller/dwc/pcie-tegra194.c | 72 ++++++++++++----------
> 1 file changed, 41 insertions(+), 31 deletions(-)
>
> diff --git a/drivers/pci/controller/dwc/pcie-tegra194.c b/drivers/pci/controller/dwc/pcie-tegra194.c
> index 14031cfaee8b..7c349478556d 100644
> --- a/drivers/pci/controller/dwc/pcie-tegra194.c
> +++ b/drivers/pci/controller/dwc/pcie-tegra194.c
> @@ -673,37 +673,46 @@ static void init_host_aspm(struct tegra_pcie_dw *pcie)
>
> pcie->ras_des_cap = dw_pcie_find_ext_capability(&pcie->pci,
> PCI_EXT_CAP_ID_VNDR);
> -
> - /* Enable ASPM counters */
> - val = FIELD_PREP(EVENT_COUNTER_ENABLE_MASK, EVENT_COUNTER_ENABLE_ALL);
> - val |= FIELD_PREP(EVENT_COUNTER_GROUP_SEL_MASK, EVENT_COUNTER_GROUP_5);
> - dw_pcie_writel_dbi(pci, pcie->ras_des_cap +
> - RAS_DES_EVENT_COUNTER_CONTROL, val);
> -
> - /* Program T_cmrt and T_pwr_on values */
> - val = dw_pcie_readl_dbi(pci, l1ss + PCI_L1SS_CAP);
> - FIELD_MODIFY(PCI_L1SS_CAP_CM_RESTORE_TIME, &val, pcie->aspm_cmrt);
> - FIELD_MODIFY(PCI_L1SS_CAP_P_PWR_ON_VALUE, &val, pcie->aspm_pwr_on_t);
> - dw_pcie_writel_dbi(pci, l1ss + PCI_L1SS_CAP, val);
> -
> - if (pcie->supports_clkreq)
> - pci->l1ss_support = true;
> -
> - /*
> - * Disable L1.2 capability advertisement for Tegra234 Endpoint mode.
> - * Tegra234 has a hardware bug where during L1.2 exit, the UPHY PLL is
> - * powered up immediately without waiting for REFCLK to stabilize. This
> - * causes the PLL to fail to lock to the correct frequency, resulting in
> - * PCIe link loss. Since there is no hardware fix available, we prevent
> - * the Endpoint from advertising L1.2 support by clearing the L1.2 bits
> - * in the L1 PM Substates Capabilities register. This ensures the host
> - * will not attempt to enter L1.2 state with this Endpoint.
> - */
> - if (pcie->of_data->disable_l1_2 &&
> - pcie->of_data->mode == DW_PCIE_EP_TYPE) {
> + if (pcie->ras_des_cap) {
> + /* Enable ASPM counters */
> + val = FIELD_PREP(EVENT_COUNTER_ENABLE_MASK,
> + EVENT_COUNTER_ENABLE_ALL);
> + val |= FIELD_PREP(EVENT_COUNTER_GROUP_SEL_MASK,
> + EVENT_COUNTER_GROUP_5);
> + dw_pcie_writel_dbi(pci, pcie->ras_des_cap +
> + RAS_DES_EVENT_COUNTER_CONTROL, val);
> + }
> +
> + if (l1ss) {
> + /* Program T_cmrt and T_pwr_on values */
> val = dw_pcie_readl_dbi(pci, l1ss + PCI_L1SS_CAP);
> - val &= ~(PCI_L1SS_CAP_PCIPM_L1_2 | PCI_L1SS_CAP_ASPM_L1_2);
> + FIELD_MODIFY(PCI_L1SS_CAP_CM_RESTORE_TIME, &val,
> + pcie->aspm_cmrt);
> + FIELD_MODIFY(PCI_L1SS_CAP_P_PWR_ON_VALUE, &val,
> + pcie->aspm_pwr_on_t);
> dw_pcie_writel_dbi(pci, l1ss + PCI_L1SS_CAP, val);
> +
> + if (pcie->supports_clkreq)
> + pci->l1ss_support = true;
> +
> + /*
> + * Disable L1.2 capability advertisement for Tegra234 Endpoint
> + * mode. Tegra234 has a hardware bug where during L1.2 exit,
> + * the UPHY PLL is powered up immediately without waiting for
> + * REFCLK to stabilize. This causes the PLL to fail to lock to
> + * the correct frequency, resulting in PCIe link loss. Since
> + * there is no hardware fix available, prevent the Endpoint
> + * from advertising L1.2 support by clearing the L1.2 bits in
> + * the L1 PM Substates Capabilities register. This ensures the
> + * host will not attempt to enter L1.2 with this Endpoint.
> + */
> + if (pcie->of_data->disable_l1_2 &&
> + pcie->of_data->mode == DW_PCIE_EP_TYPE) {
> + val = dw_pcie_readl_dbi(pci, l1ss + PCI_L1SS_CAP);
> + val &= ~(PCI_L1SS_CAP_PCIPM_L1_2 |
> + PCI_L1SS_CAP_ASPM_L1_2);
> + dw_pcie_writel_dbi(pci, l1ss + PCI_L1SS_CAP, val);
> + }
> }
>
> /* Program L0s and L1 entrance latencies */
> @@ -727,8 +736,9 @@ static void init_debugfs(struct tegra_pcie_dw *pcie)
>
> pcie->debugfs = debugfs_create_dir(name, NULL);
>
> - debugfs_create_devm_seqfile(dev, "aspm_state_cnt", pcie->debugfs,
> - aspm_state_cnt);
> + if (pcie->ras_des_cap)
> + debugfs_create_devm_seqfile(dev, "aspm_state_cnt", pcie->debugfs,
> + aspm_state_cnt);
> }
> #else
> static inline void init_host_aspm(struct tegra_pcie_dw *pcie) { return; }
> --
> 2.34.1
>
next prev parent reply other threads:[~2026-10-21 15:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 6:13 [PATCH v2 00/10] PCI: tegra194: Fix EP and Root Port corner cases Manikanta Maddireddy
2026-10-21 6:13 ` [PATCH v2 01/10] PCI: tegra194: Propagate REFCLK select GPIO errors Manikanta Maddireddy
2026-10-21 15:14 ` Frank Li
2026-10-21 6:13 ` [PATCH v2 02/10] PCI: tegra194: Check core reset deassertion Manikanta Maddireddy
2026-10-21 15:16 ` Frank Li
2026-10-21 6:13 ` [PATCH v2 03/10] PCI: tegra194: Fix Endpoint PERST# IRQ suspend race Manikanta Maddireddy
2026-10-21 15:19 ` Frank Li
2026-10-21 6:13 ` [PATCH v2 04/10] PCI: tegra194: Do not skip no-link Root Port remove cleanup Manikanta Maddireddy
2026-10-21 15:22 ` Frank Li
2026-10-21 6:13 ` [PATCH v2 05/10] PCI: tegra194: Check for 16 GT/s capability before programming Manikanta Maddireddy
2026-10-21 15:24 ` Frank Li
2026-10-21 6:13 ` [PATCH v2 06/10] PCI: tegra194: Check for L1SS " Manikanta Maddireddy
2026-10-21 15:28 ` Frank Li [this message]
2026-10-21 6:13 ` [PATCH v2 07/10] PCI: tegra194: Always disable Tegra234 Endpoint L1.2 Manikanta Maddireddy
2026-10-21 15:32 ` Frank Li
2026-10-21 6:13 ` [PATCH v2 08/10] PCI: tegra194: Guard Endpoint PLL-off error path Manikanta Maddireddy
2026-10-21 15:36 ` Frank Li
2026-10-21 6:13 ` [PATCH v2 09/10] PCI: tegra194: Balance core monitor clock on failures Manikanta Maddireddy
2026-10-21 15:43 ` Frank Li
2026-10-21 6:13 ` [PATCH v2 10/10] PCI: tegra194: Reject zero MSI interrupt number Manikanta Maddireddy
2026-10-21 15:44 ` Frank Li
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=atjaI9HAoB_KBUaZ@SMW015318 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=den@valinux.co.jp \
--cc=jonathanh@nvidia.com \
--cc=kishon@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mmaddireddy@nvidia.com \
--cc=robh@kernel.org \
--cc=thierry.reding@kernel.org \
--cc=vidyas@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®