From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Keith Busch <kbusch@kernel.org>, Konrad Dybcio <konradybcio@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
Marijn Suijten <marijn.suijten@somainline.org>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvme-pci: Force NVME_QUIRK_SIMPLE_SUSPEND on Qualcomm hosts
Date: Fri, 25 Oct 2024 18:40:23 +0200 [thread overview]
Message-ID: <867d7b15-6861-4300-83aa-55a6cdf87f58@oss.qualcomm.com> (raw)
In-Reply-To: <ZxvDZVKtM9qGYBP_@kbusch-mbp.dhcp.thefacebook.com>
On 25.10.2024 6:12 PM, Keith Busch wrote:
> On Thu, Oct 24, 2024 at 07:33:07PM +0200, Konrad Dybcio wrote:
>> From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>>
>> The Qualcomm SC8280XP SoC requires that all PCIe hosts are powered down
>> before the platform can reach S3-like sleep states. This is very much
>> similar in nature to the issue described in [1].
>
> The "SIMPLE" quirk is only supposed to affect kernel managed runtime
> suspend states, s2idle or s0ix. Shouldn't s3 already be using the simple
> suspend?
So on these platforms, all system sleep states (incl. S3) are entered
through what Linux sees as s2idle, with a separate MCU doing a lot
behind the scenes. s2idle of course also covers the runtime cpuidle
cases.
All but the deepest state (which Linux doesn't differentiate as of
today) are effectively somewhat like s0ix.
It's a bit hard to draw accurate lines between Intel terminology and
what we have here, as there's way more things onboard than just the CPU
cluster that may be operating independently..
Konrad
next prev parent reply other threads:[~2024-10-25 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 17:33 [PATCH] nvme-pci: Force NVME_QUIRK_SIMPLE_SUSPEND on Qualcomm hosts Konrad Dybcio
2024-10-25 11:35 ` Christoph Hellwig
2024-10-25 15:30 ` Konrad Dybcio
2024-10-28 9:19 ` Christoph Hellwig
2024-10-28 13:15 ` Konrad Dybcio
2024-10-25 16:12 ` Keith Busch
2024-10-25 16:40 ` Konrad Dybcio [this message]
2024-10-25 16:57 ` Keith Busch
2024-10-25 17:20 ` Konrad Dybcio
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=867d7b15-6861-4300-83aa-55a6cdf87f58@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=axboe@kernel.dk \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=marijn.suijten@somainline.org \
--cc=sagi@grimberg.me \
/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