From: Bjorn Helgaas <helgaas@kernel.org>
To: Vidya Sagar <vidyas@nvidia.com>
Cc: bhelgaas@google.com, lorenzo.pieralisi@arm.com,
refactormyself@gmail.com, kw@linux.com, rajatja@google.com,
kenny@panix.com, kai.heng.feng@canonical.com, abhsahu@nvidia.com,
sagupta@nvidia.com, treding@nvidia.com, jonathanh@nvidia.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
kthota@nvidia.com, mmaddireddy@nvidia.com, sagar.tv@gmail.com,
Krishna chaitanya chundru <quic_krichai@quicinc.com>
Subject: Re: [PATCH V4 1/2] PCI/ASPM: Refactor ASPM L1SS control register programming
Date: Thu, 29 Sep 2022 17:00:18 -0500 [thread overview]
Message-ID: <20220929220018.GA1927153@bhelgaas> (raw)
In-Reply-To: <20220913131822.16557-2-vidyas@nvidia.com>
[+cc Krishna]
On Tue, Sep 13, 2022 at 06:48:21PM +0530, Vidya Sagar wrote:
> Refactor the code to extract the command code out to program
> Control Registers-1 & 2 of L1 Sub-States capability to a new function
> aspm_program_l1ss() and call it for both parent and child devices.
>
> Signed-off-by: Vidya Sagar <vidyas@nvidia.com>
> ---
> V4:
> * New patch in this series
>
> drivers/pci/pcie/aspm.c | 63 +++++++++++++++++++----------------------
> 1 file changed, 29 insertions(+), 34 deletions(-)
>
> diff --git a/drivers/pci/pcie/aspm.c b/drivers/pci/pcie/aspm.c
> index a8aec190986c..ecbe3af4188d 100644
> --- a/drivers/pci/pcie/aspm.c
> +++ b/drivers/pci/pcie/aspm.c
> @@ -455,6 +455,31 @@ static void pci_clear_and_set_dword(struct pci_dev *pdev, int pos,
> pci_write_config_dword(pdev, pos, val);
> }
>
> +static void aspm_program_l1ss(struct pci_dev *dev, u32 ctl1, u32 ctl2)
> +{
> + u16 l1ss = dev->l1ss;
> + u32 l1_2_enable;
> +
> + /*
> + * Per PCIe r6.0, sec 5.5.4, T_POWER_ON in PCI_L1SS_CTL2 must be
> + * programmed prior to setting the L1.2 enable bits in PCI_L1SS_CTL1.
> + */
> + pci_write_config_dword(dev, l1ss + PCI_L1SS_CTL2, ctl2);
> +
> + /*
> + * In addition, Common_Mode_Restore_Time and LTR_L1.2_THRESHOLD in
> + * PCI_L1SS_CTL1 must be programmed *before* setting the L1.2
> + * enable bits, even though they're all in PCI_L1SS_CTL1.
> + */
> + l1_2_enable = ctl1 & PCI_L1SS_CTL1_L1_2_MASK;
> + ctl1 &= ~PCI_L1SS_CTL1_L1_2_MASK;
> +
> + pci_write_config_dword(dev, l1ss + PCI_L1SS_CTL1, ctl1);
> + if (l1_2_enable)
> + pci_write_config_dword(dev, l1ss + PCI_L1SS_CTL1,
> + ctl1 | l1_2_enable);
> +}
> +
> /* Calculate L1.2 PM substate timing parameters */
> static void aspm_calc_l1ss_info(struct pcie_link_state *link,
> u32 parent_l1ss_cap, u32 child_l1ss_cap)
> @@ -464,7 +489,6 @@ static void aspm_calc_l1ss_info(struct pcie_link_state *link,
> u32 t_common_mode, t_power_on, l1_2_threshold, scale, value;
> u32 ctl1 = 0, ctl2 = 0;
> u32 pctl1, pctl2, cctl1, cctl2;
> - u32 pl1_2_enables, cl1_2_enables;
>
> if (!(link->aspm_support & ASPM_STATE_L1_2_MASK))
> return;
> @@ -513,39 +537,10 @@ static void aspm_calc_l1ss_info(struct pcie_link_state *link,
> ctl2 == pctl2 && ctl2 == cctl2)
> return;
>
> - /* Disable L1.2 while updating. See PCIe r5.0, sec 5.5.4, 7.8.3.3 */
> - pl1_2_enables = pctl1 & PCI_L1SS_CTL1_L1_2_MASK;
> - cl1_2_enables = cctl1 & PCI_L1SS_CTL1_L1_2_MASK;
> -
> - if (pl1_2_enables || cl1_2_enables) {
> - pci_clear_and_set_dword(child, child->l1ss + PCI_L1SS_CTL1,
> - PCI_L1SS_CTL1_L1_2_MASK, 0);
> - pci_clear_and_set_dword(parent, parent->l1ss + PCI_L1SS_CTL1,
> - PCI_L1SS_CTL1_L1_2_MASK, 0);
> - }
> -
> - /* Program T_POWER_ON times in both ports */
> - pci_write_config_dword(parent, parent->l1ss + PCI_L1SS_CTL2, ctl2);
> - pci_write_config_dword(child, child->l1ss + PCI_L1SS_CTL2, ctl2);
> -
> - /* Program Common_Mode_Restore_Time in upstream device */
> - pci_clear_and_set_dword(parent, parent->l1ss + PCI_L1SS_CTL1,
> - PCI_L1SS_CTL1_CM_RESTORE_TIME, ctl1);
> -
> - /* Program LTR_L1.2_THRESHOLD time in both ports */
> - pci_clear_and_set_dword(parent, parent->l1ss + PCI_L1SS_CTL1,
> - PCI_L1SS_CTL1_LTR_L12_TH_VALUE |
> - PCI_L1SS_CTL1_LTR_L12_TH_SCALE, ctl1);
> - pci_clear_and_set_dword(child, child->l1ss + PCI_L1SS_CTL1,
> - PCI_L1SS_CTL1_LTR_L12_TH_VALUE |
> - PCI_L1SS_CTL1_LTR_L12_TH_SCALE, ctl1);
> -
> - if (pl1_2_enables || cl1_2_enables) {
> - pci_clear_and_set_dword(parent, parent->l1ss + PCI_L1SS_CTL1, 0,
> - pl1_2_enables);
> - pci_clear_and_set_dword(child, child->l1ss + PCI_L1SS_CTL1, 0,
> - cl1_2_enables);
> - }
> + aspm_program_l1ss(parent,
> + ctl1 | (pctl1 & PCI_L1SS_CTL1_L1_2_MASK), ctl2);
> + aspm_program_l1ss(child,
> + ctl1 | (cctl1 & PCI_L1SS_CTL1_L1_2_MASK), ctl2);
This doesn't seem right to me. I think the intent is to update
LTR_L1.2_THRESHOLD and Common_Mode_Restore_Time, which are encoded in
"ctl1". It does do that, but it looks like it *also* clears
everything except PCI_L1SS_CTL1_L1_2_MASK, i.e., the L1.1 Enable bits,
the Link Activation bits, and the RsvdP bits, which I don't think we
should be clearing. Am I missing something?
Bjorn
next prev parent reply other threads:[~2022-09-29 22:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 13:18 [PATCH V4 0/2] PCI/ASPM: Save/restore L1SS Capability for suspend/resume Vidya Sagar
2022-09-13 13:18 ` [PATCH V4 1/2] PCI/ASPM: Refactor ASPM L1SS control register programming Vidya Sagar
2022-09-29 22:00 ` Bjorn Helgaas [this message]
2022-10-03 6:42 ` Vidya Sagar
2022-10-05 2:35 ` Bjorn Helgaas
2022-10-09 5:44 ` Vidya Sagar
2022-09-13 13:18 ` [PATCH V4 2/2] PCI/ASPM: Save/restore L1SS Capability for suspend/resume Vidya Sagar
2022-09-13 17:17 ` [PATCH V4 0/2] " 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=20220929220018.GA1927153@bhelgaas \
--to=helgaas@kernel.org \
--cc=abhsahu@nvidia.com \
--cc=bhelgaas@google.com \
--cc=jonathanh@nvidia.com \
--cc=kai.heng.feng@canonical.com \
--cc=kenny@panix.com \
--cc=kthota@nvidia.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mmaddireddy@nvidia.com \
--cc=quic_krichai@quicinc.com \
--cc=rajatja@google.com \
--cc=refactormyself@gmail.com \
--cc=sagar.tv@gmail.com \
--cc=sagupta@nvidia.com \
--cc=treding@nvidia.com \
--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;
as well as URLs for NNTP newsgroup(s).