Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
To: lpieralisi@kernel.org, kwilczynski@kernel.org,
	bhelgaas@google.com,
	Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
Cc: robh@kernel.org, linux-pci@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH] PCI: qcom: Clear ASPM L0s CAP for MSM8996 SoC
Date: Tue, 23 Dec 2025 12:11:19 +0530	[thread overview]
Message-ID: <176647207945.161450.8052515821884695336.b4-ty@kernel.org> (raw)
In-Reply-To: <20251126081718.8239-1-mani@kernel.org>


On Wed, 26 Nov 2025 13:47:18 +0530, Manivannan Sadhasivam wrote:
> Though I couldn't confirm the ASPM L0s support with the Qcom hardware team,
> bug report from Dmitry suggests that L0s is broken on this legacy SoC.
> Hence, clear the L0s CAP for the Root Ports in this SoC.
> 
> Since qcom_pcie_clear_aspm_l0s() is now used by more than one SoC config,
> call it from qcom_pcie_host_init() instead.
> 
> [...]

Applied, thanks!

[1/1] PCI: qcom: Clear ASPM L0s CAP for MSM8996 SoC
      commit: 91f2fb5fe4735c6c99c000857f2e0bd7ebbddb95

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


  parent reply	other threads:[~2025-12-23  6:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26  8:17 [PATCH] PCI: qcom: Clear ASPM L0s CAP for MSM8996 SoC Manivannan Sadhasivam
2025-11-26  8:47 ` Dmitry Baryshkov
2025-11-27 10:55 ` Konrad Dybcio
2025-11-27 13:55   ` Manivannan Sadhasivam
2025-11-27 14:12     ` Konrad Dybcio
2025-12-23  6:41 ` Manivannan Sadhasivam [this message]
2025-12-26 23:39 ` Bjorn Helgaas
2025-12-27  4:28   ` Manivannan Sadhasivam
2025-12-30 17:14     ` 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=176647207945.161450.8052515821884695336.b4-ty@kernel.org \
    --to=manivannan.sadhasivam@oss.qualcomm.com \
    --cc=bhelgaas@google.com \
    --cc=dmitry.baryshkov@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=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