[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d856a2c3-2f75-8e79-f791-d5c0787a9018@codeaurora.org>
Date: Sat, 9 Jun 2018 19:49:23 -0400
From: Sinan Kaya <okaya@...eaurora.org>
To: Rajat Jain <rajatja@...gle.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
"Busch, Keith" <keith.busch@...el.com>,
Vidya Sagar <vidyas@...dia.com>,
Philippe Ombredanne <pombredanne@...b.com>,
Kees Cook <keescook@...omium.org>,
"Gustavo A. R. Silva" <garsilva@...eddedor.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Frederick Lawler <fred@...dlawl.com>,
linux-pci <linux-pci@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Patel, Mayurkumar" <mayurkumar.patel@...el.com>
Cc: Rajat Jain <rajatxjain@...il.com>
Subject: Re: [PATCH v2] pci/aspm: Remove CONFIG_PCIEASPM_DEBUG
> On Thu, May 10, 2018 at 4:39 PM Rajat Jain <rajatja@...gle.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@...gle.com>
>> ---
>> v2: provide function definitions for !CONFIG_PCIEASPM case
Reviewed-by: Sinan Kaya <okaya@...eaurora.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.
Powered by blists - more mailing lists