From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Return-Path: Subject: Re: [PATCH v2] pci/aspm: Remove CONFIG_PCIEASPM_DEBUG To: Bjorn Helgaas Cc: Rajat Jain , Bjorn Helgaas , Keith Busch , Vidya Sagar , Philippe Ombredanne , Kees Cook , "Gustavo A. R. Silva" , Ard Biesheuvel , Sinan Kaya , Frederick Lawler , linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, mayurkumar.patel@intel.com, rajatxjain@gmail.com, Richard Hughes , Carlos Garnacho , "Rafael J. Wysocki" , Pali Rohar , Takashi Iwai , Andy Whitcroft , Colin Ian King References: <20180508230148.121852-1-rajatja@google.com> <20180510233912.96454-1-rajatja@google.com> <20180727202619.GD173328@bhelgaas-glaptop.roam.corp.google.com> <5a102163-73bc-c596-8266-186e222e7ceb@kernel.org> <20180730141428.GK173328@bhelgaas-glaptop.roam.corp.google.com> From: Sinan Kaya Message-ID: <2fbc0d1b-0d14-6bab-74c5-a9dd2ae417bb@kernel.org> Date: Mon, 30 Jul 2018 09:08:18 -0700 MIME-Version: 1.0 In-Reply-To: <20180730141428.GK173328@bhelgaas-glaptop.roam.corp.google.com> Content-Type: text/plain; charset=utf-8; format=flowed List-ID: On 7/30/2018 7:14 AM, Bjorn Helgaas wrote: > However, the end of sec 5.4.1 does make it clear that the functions > need not have the same ASPM configuration, and it gives rules for how > those different settings should affect the shared link. Since it > mentions different ASPM Control fields for the different functions, I > assume the policy combining those per-function settings into the > single link behavior must be implemented in the hardware. Very interesting. This is news for me.