From: Steev Klimaszewski <threeway@gmail•com>
To: krishna.chundru@oss•qualcomm.com
Cc: bhelgaas@google•com, bjorn.andersson@oss•qualcomm.com,
jingoohan1@gmail•com, jonathanh@nvidia•com,
kwilczynski@kernel•org, linux-arm-kernel@lists•infradead.org,
linux-arm-msm@vger•kernel.org, linux-kernel@vger•kernel.org,
linux-pci@vger•kernel.org, lpieralisi@kernel•org,
mani@kernel•org, robh@kernel•org, threeway@gmail•com,
will@kernel•org
Subject: Re: PCI: qcom: Add D3cold support
Date: Sun, 3 May 2026 23:14:06 -0500 [thread overview]
Message-ID: <20260504041407.289464-1-threeway@gmail.com> (raw)
In-Reply-To: <dd4dc11e-338a-4d13-9830-095a93187f4c@oss.qualcomm.com>
On Sun, May 3, 2026 at 10:37 PM Krishna Chaitanya Chundru <krishna.chundru@oss•qualcomm.com> wrote:
>
> >
> > v4 of this patchset *boots* along with Mani's patchset, however, v5 does not,
> > and unfortunately, the machine does not seem to get to a point where I can even
> > get logs from it. Do you know what I might be missing? I have *not* attempted
> > to remove the nvme drive and boot off USB to test it.
> This series, will not have any impact on the boot, this series comes in to the
> picture only in case
> of suspend and resume. can you share your platform details and kernel you are
> booting with.
Oddly, it seems to, because if I simply go back to v4, the system boots. I'm
using a 7.0 kernel on the Thinkpad X13s (SC8280XP). The sources are at
https://github.com/steev/linux/tree/lenovo-x13s-linux-7.0.y (with the v5
applied). PCIE_QCOM is built-in to the kernel. Not sure what other information
is needed.
>
> - Krishna Chaitanya.
> >
> > -- steev
next prev parent reply other threads:[~2026-05-04 4:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 6:42 [PATCH v5 0/5] PCI: qcom: Add D3cold support Krishna Chaitanya Chundru
2026-04-29 6:42 ` [PATCH v5 1/5] PCI: host-common: Add helper to determine host bridge D3cold eligibility Krishna Chaitanya Chundru
2026-05-19 22:39 ` Bjorn Helgaas
2026-05-20 20:27 ` Bjorn Helgaas
2026-05-21 15:09 ` Manivannan Sadhasivam
2026-04-29 6:42 ` [PATCH v5 2/5] PCI: qcom: Add .get_ltssm() helper Krishna Chaitanya Chundru
2026-04-29 6:42 ` [PATCH v5 3/5] PCI: qcom: Power down PHY via PARF_PHY_CTRL before disabling rails/clocks Krishna Chaitanya Chundru
2026-04-29 6:42 ` [PATCH v5 4/5] PCI: dwc: Use common D3cold eligibility helper in suspend path Krishna Chaitanya Chundru
2026-05-13 13:20 ` Manivannan Sadhasivam
2026-05-20 0:01 ` Bjorn Helgaas
2026-05-22 22:48 ` Bjorn Helgaas
2026-04-29 6:42 ` [PATCH v5 5/5] PCI: qcom: Add D3cold support Krishna Chaitanya Chundru
2026-05-03 20:30 ` Steev Klimaszewski
2026-05-04 3:37 ` Krishna Chaitanya Chundru
2026-05-04 4:14 ` Steev Klimaszewski [this message]
2026-05-04 7:06 ` Krishna Chaitanya Chundru
2026-05-04 14:16 ` Steev Klimaszewski
2026-05-13 15:00 ` Manivannan Sadhasivam
2026-05-13 14:54 ` [PATCH v5 0/5] " Manivannan Sadhasivam
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=20260504041407.289464-1-threeway@gmail.com \
--to=threeway@gmail$(echo .)com \
--cc=bhelgaas@google$(echo .)com \
--cc=bjorn.andersson@oss$(echo .)qualcomm.com \
--cc=jingoohan1@gmail$(echo .)com \
--cc=jonathanh@nvidia$(echo .)com \
--cc=krishna.chundru@oss$(echo .)qualcomm.com \
--cc=kwilczynski@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-arm-msm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-pci@vger$(echo .)kernel.org \
--cc=lpieralisi@kernel$(echo .)org \
--cc=mani@kernel$(echo .)org \
--cc=robh@kernel$(echo .)org \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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