[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <57460EAA.9040705@codeaurora.org>
Date: Wed, 25 May 2016 16:44:26 -0400
From: Sinan Kaya <okaya@...eaurora.org>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Ocean HY1 He <hehy1@...ovo.com>,
"bhelgaas@...gle.com" <bhelgaas@...gle.com>,
"wangyijing@...wei.com" <wangyijing@...wei.com>,
"luto@...nel.org" <luto@...nel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"prarit@...hat.com" <prarit@...hat.com>,
"jcm@...hat.com" <jcm@...hat.com>,
Nagananda Chumbalkar <nchumbalkar@...ovo.com>
Subject: Re: [PATCH] PCI/ASPM: fix reverse ASPM L0s assignment of upstream and
downstream
On 5/25/2016 2:33 PM, Bjorn Helgaas wrote:
> It looks like the code enforces this by clearing bits in
> link->aspm_capable (effectively pretending L0s or L1 are unsupported)
> if the latency is too high.
Yes, this is what I was referring to. I think what Linux does is
the right thing.
--
Sinan Kaya
Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
Powered by blists - more mailing lists