From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
lpieralisi@kernel.org, kw@linux.com, bhelgaas@google.com
Cc: robh@kernel.org, gustavo.pimentel@synopsys.com,
jingoohan1@gmail.com, andersson@kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 0/2] PCI: qcom: Enable ASPM on host bridge and devices
Date: Tue, 10 Oct 2023 18:25:35 +0200 [thread overview]
Message-ID: <5fab045d-3b09-496d-af30-b7355495694b@linaro.org> (raw)
In-Reply-To: <20231010155914.9516-1-manivannan.sadhasivam@linaro.org>
On 10/10/23 17:59, Manivannan Sadhasivam wrote:
> Hi,
>
> This series enables ASPM by default on the host bridge and devices of selected
> Qcom platforms.
>
> The motivation behind enabling ASPM in the controller driver is provided in the
> commit message of patch 2/2.
>
> This series has been tested on SC8280-CRD and Lenovo Thinkpad X13s laptop
> and it helped save ~0.6W of power during runtime.
That's a lot of power, thanks for looking into this!
Konrad
next prev parent reply other threads:[~2023-10-10 16:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 15:59 [PATCH v2 0/2] PCI: qcom: Enable ASPM on host bridge and devices Manivannan Sadhasivam
2023-10-10 15:59 ` [PATCH v2 1/2] PCI: dwc: Add host_post_init() callback Manivannan Sadhasivam
2023-10-16 20:58 ` Bjorn Helgaas
2023-10-17 7:59 ` Manivannan Sadhasivam
2023-10-18 16:47 ` Bjorn Helgaas
2023-10-10 15:59 ` [PATCH v2 2/2] PCI: qcom: Enable ASPM for platforms supporting 1.9.0 ops Manivannan Sadhasivam
2023-10-10 16:29 ` Bjorn Helgaas
2023-10-11 5:00 ` Manivannan Sadhasivam
2023-10-10 16:33 ` Konrad Dybcio
2023-10-11 5:03 ` Manivannan Sadhasivam
2023-10-10 16:25 ` Konrad Dybcio [this message]
2023-10-14 20:32 ` [PATCH v2 0/2] PCI: qcom: Enable ASPM on host bridge and devices Krzysztof Wilczyński
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=5fab045d-3b09-496d-af30-b7355495694b@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=andersson@kernel.org \
--cc=bhelgaas@google.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=kw@linux.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.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