From: Vidya Sagar <vidyas@nvidia.com>
To: "Kenneth R. Crudup" <kenny@panix.com>,
Bjorn Helgaas <helgaas@kernel.org>
Cc: <bhelgaas@google.com>, <lorenzo.pieralisi@arm.com>,
<hkallweit1@gmail.com>, <wangxiongfeng2@huawei.com>,
<mika.westerberg@linux.intel.com>, <kai.heng.feng@canonical.com>,
<chris.packham@alliedtelesis.co.nz>, <yangyicong@hisilicon.com>,
<treding@nvidia.com>, <jonathanh@nvidia.com>,
<abhsahu@nvidia.com>, <sagupta@nvidia.com>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kthota@nvidia.com>, <mmaddireddy@nvidia.com>,
<sagar.tv@gmail.com>
Subject: Re: [PATCH V1] PCI/ASPM: Save/restore L1SS Capability for suspend/resume
Date: Wed, 16 Feb 2022 18:41:39 +0530 [thread overview]
Message-ID: <0d8cc8c0-31a1-0290-5aa5-0c7b16db1edb@nvidia.com> (raw)
In-Reply-To: <75a48fb6-3913-ccaf-3c-6d41bbbda533@panix.com>
On 2/16/2022 11:30 AM, Kenneth R. Crudup wrote:
> External email: Use caution opening links or attachments
>
>
> On Wed, 16 Feb 2022, Vidya Sagar wrote:
>
>> I see that the ASPM-L1 state of Realtek NIC which was in disabled state before
>> hibernate got enabled after hibernate.
>
> That's actually my SD-Card reader; there's a good chance the BIOS does "something"
> to it at boot time, as it's possible to boot from SD-Card on my laptop.
>
>> This patch doesn't do anything to LnkCtl register which has control for ASPM L1
>> state.
>
>> Could you please check why ASPM L1 got enabled post hibernation?
>
> I wouldn't know how to do that; if you're still interested in that let me know
> what to do to determine that.
I would like Bjorn to take a call on it.
At this point, there are contradictions in observations.
Just to summarize,
- The root ports in your laptop don't have support for L1SS
- With the same old code base with which the errors were observed plus
my patch on top of it, I see that ASPM-L1 state getting enabled for one
of the endpoints (Realtek SD-Card reader) after system comes out of
hibernation even though ASPM-L1 was disabled before the system enter
into hibernation. No errors are reported now.
- With the linux-next top of the tree plus my patch, no change in the
ASPM states and no errors also reported.
This points to BIOS being buggy (both old and new with new one being
less problematic)
Bjorn, what are your comments on it?
>
> -Kenny
>
> --
> Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange County CA
>
next prev parent reply other threads:[~2022-02-16 13:11 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 12:35 Vidya Sagar
2022-02-01 13:54 ` Kenneth R. Crudup
2022-02-01 18:53 ` Kenneth R. Crudup
2022-02-01 19:03 ` Kenneth R. Crudup
2022-02-01 19:05 ` Kenneth R. Crudup
2022-02-01 19:10 ` Kenneth R. Crudup
2022-02-01 19:24 ` Vidya Sagar
2022-02-01 22:25 ` Kenneth R. Crudup
2022-02-02 4:17 ` Vidya Sagar
2022-02-04 1:18 ` Kenneth R. Crudup
2022-02-04 5:37 ` Vidya Sagar
2022-02-04 23:02 ` Bjorn Helgaas
2022-02-04 23:17 ` Kenneth R. Crudup
2022-02-05 16:44 ` Vidya Sagar
2022-02-05 17:30 ` Kenneth R. Crudup
2022-02-05 17:32 ` Kenneth R. Crudup
2022-02-05 17:33 ` Kenneth R. Crudup
2022-02-07 16:33 ` Bjorn Helgaas
2022-02-07 18:20 ` Kenneth R. Crudup
2022-02-15 13:10 ` Kenneth R. Crudup
2022-02-16 4:40 ` Vidya Sagar
2022-02-16 6:00 ` Kenneth R. Crudup
2022-02-16 13:11 ` Vidya Sagar [this message]
2022-04-12 22:50 ` Bjorn Helgaas
2022-04-13 0:19 ` Kai-Heng Feng
2022-04-14 16:41 ` Bjorn Helgaas
2022-04-15 14:26 ` Kai-Heng Feng
2022-04-15 21:25 ` Bjorn Helgaas
2022-04-21 6:16 ` Kai-Heng Feng
2022-04-21 20:36 ` Bjorn Helgaas
2022-04-21 20:40 ` Kenneth R. Crudup
2022-04-21 21:11 ` Bjorn Helgaas
2022-04-21 21:21 ` Kenneth R. Crudup
2022-04-13 13:26 ` Bjorn Helgaas
2022-11-23 21:44 ` Matthias Kaehlcke
2022-11-23 22:01 ` Kenneth R. Crudup
2022-11-24 0:07 ` Matthias Kaehlcke
2022-02-15 13:12 ` Kenneth R. Crudup
2022-02-04 11:23 ` Abhishek Sahu
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=0d8cc8c0-31a1-0290-5aa5-0c7b16db1edb@nvidia.com \
--to=vidyas@nvidia.com \
--cc=abhsahu@nvidia.com \
--cc=bhelgaas@google.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=helgaas@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kai.heng.feng@canonical.com \
--cc=kenny@panix.com \
--cc=kthota@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=mmaddireddy@nvidia.com \
--cc=sagar.tv@gmail.com \
--cc=sagupta@nvidia.com \
--cc=treding@nvidia.com \
--cc=wangxiongfeng2@huawei.com \
--cc=yangyicong@hisilicon.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®