From: Sinan Kaya <okaya@codeaurora.org>
To: Rajat Jain <rajatja@google.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"Busch, Keith" <keith.busch@intel.com>,
Vidya Sagar <vidyas@nvidia.com>,
Philippe Ombredanne <pombredanne@nexb.com>,
Kees Cook <keescook@chromium.org>,
"Gustavo A. R. Silva" <garsilva@embeddedor.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Frederick Lawler <fred@fredlawl.com>,
linux-pci <linux-pci@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Patel, Mayurkumar" <mayurkumar.patel@intel.com>
Cc: Rajat Jain <rajatxjain@gmail.com>
Subject: Re: [PATCH v2] pci/aspm: Remove CONFIG_PCIEASPM_DEBUG
Date: Sat, 9 Jun 2018 19:49:23 -0400 [thread overview]
Message-ID: <d856a2c3-2f75-8e79-f791-d5c0787a9018@codeaurora.org> (raw)
In-Reply-To: <CACK8Z6H0PE-xBiNxhS+-P=-SyqAzKQi87xQoLGzgh6sgyt8zGA@mail.gmail.com>
> On Thu, May 10, 2018 at 4:39 PM Rajat Jain <rajatja@google.com> wrote:
>>
>> Currently, the linux kernel disables ASPM when a device is
>> removed from the kernel. But it is not enabled again when
>> a new device is added on that slot even if it was originally
>> enabled (by the BIOS) when the system booted up (assuming
>> POLICY_DEFAULT).
>>
>> This was earlier discussed here:
>> https://www.spinics.net/lists/linux-pci/msg60212.html
>>
>> And some suggestions from Bjorn here:
>> https://www.spinics.net/lists/linux-pci/msg60541.html
>>
>> This patch picks up one of the suggestion, to remove the
>> CONFIG_PCIEASPM_DEBUG and thus make the code always
>> avilable. This provides control to userspace to control
>> ASPM on a per slot / device basis using sysfs interface.
>>
>> Signed-off-by: Rajat Jain <rajatja@google.com>
>> ---
>> v2: provide function definitions for !CONFIG_PCIEASPM case
Reviewed-by: Sinan Kaya <okaya@codeaurora.org>
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2018-06-09 23:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 23:01 [PATCH] " Rajat Jain
2018-05-09 6:46 ` okaya
2018-05-09 9:43 ` kbuild test robot
2018-05-10 23:34 ` [PATCH] PM / s2idle: Clear the events_check_enabled flag Rajat Jain
2018-05-10 23:36 ` Rajat Jain
2018-05-10 23:39 ` [PATCH v2] pci/aspm: Remove CONFIG_PCIEASPM_DEBUG Rajat Jain
2018-06-05 22:15 ` Rajat Jain
2018-06-09 23:49 ` Sinan Kaya [this message]
2018-06-29 23:27 ` Bjorn Helgaas
2018-07-27 20:26 ` Bjorn Helgaas
2018-07-27 21:03 ` Takashi Iwai
2018-07-29 0:16 ` Sinan Kaya
2018-07-30 14:14 ` Bjorn Helgaas
2018-07-30 16:08 ` Sinan Kaya
2018-07-30 8:32 ` Lukas Wunner
2018-07-30 17:26 ` Bjorn Helgaas
2018-07-30 16:18 ` Rajat Jain
2018-07-31 8:13 ` Pali Rohár
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=d856a2c3-2f75-8e79-f791-d5c0787a9018@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=ard.biesheuvel@linaro.org \
--cc=bhelgaas@google.com \
--cc=fred@fredlawl.com \
--cc=garsilva@embeddedor.com \
--cc=keescook@chromium.org \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mayurkumar.patel@intel.com \
--cc=pombredanne@nexb.com \
--cc=rajatja@google.com \
--cc=rajatxjain@gmail.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
all inboxes | Powered by JetHome®