Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	mani@kernel.org
Subject: Re: [PATCH v6 0/3] PCI/ASPM: Mask ASPM states based on Devicetree properties
Date: Tue, 11 Aug 2026 21:37:35 -0500	[thread overview]
Message-ID: <20260812023735.GA846004@bhelgaas> (raw)
In-Reply-To: <20260727-aspm-v6-0-2ebb3ee7ef71@oss.qualcomm.com>

On Mon, Jul 27, 2026 at 07:32:35PM +0530, Krishna Chaitanya Chundru wrote:
> Signed-off-by: Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>

Applied to pci/aspm for v7.3, thank you!

> ---
> Changes in v6:
> - Disable/enable each function L0s/L1. (sashiko)
> - Move from pcie_capability_write_word to
>   pcie_capability_clear_and_set_word (Sashiko)
> - Link to v5: https://patch.msgid.link/20260721-aspm-v5-1-58860c48d0c7@oss.qualcomm.com
> 
> Changes in v5:
> - update all the child devices when enabling the ASPM back (sashiko).
> - Link to v4: https://patch.msgid.link/20260707-aspm-v4-1-d66f85b728b0@oss.qualcomm.com
> 
> Changes in v4:
> - Clear link->aspm_enabled alongside aspm_support/aspm_default when an
>   ASPM state is masked, so it no longer goes stale relative to hardware (sashiko).
> - Mask the LNKCTL restore snapshot against the post-override
>   aspm_support so the restore step can no longer re-enable a state the
>   Devicetree override just disabled. (sashiko)
> - Link to v3: https://patch.msgid.link/20260704-aspm-v3-1-157217aff76f@oss.qualcomm.com
> 
> Changes in v3:
> - Move pcie_aspm_override_default_link_state() call in pcie_aspm_cap_init() to
>   before the "Restore L0s/L1" block. pcie_aspm_cap_init() disables L1 in
>   hardware prior to aspm_l1ss_init() and re-enables it only in the
>   restore block. Calling pcie_config_aspm_l1ss() while L1 is already
>   disabled satisfies its precondition ("Caller must disable L1 first"),
>   whereas the previous placement after the restore violated it (sashiko).
> - Link to v2: https://patch.msgid.link/20260624-aspm-v2-1-800a4151ba3a@oss.qualcomm.com
> 
> Changes in v2:
> - Disable L1ss when L1 is disabled as pointed by sashiko.
> - Disable L1ss if bootloader enables them but we are disabling via
>   devicetree pointed by sashiko.
> - Link to v1: https://patch.msgid.link/20260511-aspm-v1-1-b4a9fe955cf9@oss.qualcomm.com
> 
> ---
> Krishna Chaitanya Chundru (3):
>       PCI/ASPM: Use pcie_capability_clear_and_set_word() for ASPM disable/restore
>       PCI/ASPM: Disable/restore ASPM on every function for multi-function devices
>       PCI/ASPM: Mask ASPM states based on Devicetree properties
> 
>  drivers/pci/pcie/aspm.c | 149 +++++++++++++++++++++++++++++++++---------------
>  1 file changed, 102 insertions(+), 47 deletions(-)
> ---
> base-commit: f5098b6bae761e346ebcd9da7f95622c04733cff
> change-id: 20260429-aspm-da55a54279e4
> 
> Best regards,
> --  
> Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>
> 

      parent reply	other threads:[~2026-08-12  2:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 14:02 [PATCH v6 0/3] PCI/ASPM: Mask ASPM states based on Devicetree properties Krishna Chaitanya Chundru
2026-07-27 14:02 ` [PATCH v6 1/3] PCI/ASPM: Use pcie_capability_clear_and_set_word() for ASPM disable/restore Krishna Chaitanya Chundru
2026-07-27 14:11   ` sashiko-bot
2026-07-30  4:40   ` Manivannan Sadhasivam
2026-07-27 14:02 ` [PATCH v6 2/3] PCI/ASPM: Disable/restore ASPM on every function for multi-function devices Krishna Chaitanya Chundru
2026-07-27 14:15   ` sashiko-bot
2026-07-30  4:40   ` Manivannan Sadhasivam
2026-07-27 14:02 ` [PATCH v6 3/3] PCI/ASPM: Mask ASPM states based on Devicetree properties Krishna Chaitanya Chundru
2026-07-27 14:16   ` sashiko-bot
2026-07-30  5:06   ` Manivannan Sadhasivam
2026-08-12  2:37 ` Bjorn Helgaas [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=20260812023735.GA846004@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=krishna.chundru@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mani@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