From: Jon Hunter <jonathanh@nvidia.com>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>,
mark.rutland@arm.com, lpieralisi@kernel.org,
bjorn.andersson@oss.qualcomm.com, konrad.dybcio@oss.qualcomm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Konrad Dybcio <konradybcio@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Sudeep Holla <sudeep.holla@arm.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] firmware: psci: Set pm_set_resume/suspend_via_firmware() for SYSTEM_SUSPEND
Date: Thu, 7 May 2026 11:54:08 +0100 [thread overview]
Message-ID: <49a68039-3a59-4b4c-acbd-0fa917d0e456@nvidia.com> (raw)
In-Reply-To: <4ympdtnpqrydnjmapuswsnig7ymuopy4kpxqclyxnoaqgpdmxl@eywcfbu3avtg>
On 06/05/2026 18:18, Manivannan Sadhasivam wrote:
> On Tue, May 05, 2026 at 02:47:08PM +0100, Jon Hunter wrote:
>> Hi Mani,
>>
>> On 06/04/2026 15:29, Manivannan Sadhasivam wrote:
>>
>> ...
>>
>>> Sure. It makes logical sense to relate this API behavior with the state of CX.
>>> I'll send v2 with the updated commit message.
>>
>> Did you ever send a V2? I am not sure if I missed it and so wanted to check.
>>
>
> No, I didn't. I had some offline discussions with Bjorn and concluded that it
> might not be appropriate to set pm_set_resume/suspend_via_firmware() for all
> firmware flavors that our Qcom SoCs support.
>
> Then I found out a limitation with our Root Complex IPs in exiting L1ss if the
> platform is suspended. So sent out a series to fix that and that allowed me to
> get past the NVMe issue coincidentally.
>
> But since this patch applies to other ARM64 SoCs, it logically makes sense to
> apply it IMO. So, I'll leave it to PSCI maintainers to decide.
I am not sure I follow the above. Sounds like you don't want to apply
this because it may not work for all Qualcomm SoCs, but regardless of
that you will leave to the PSCI maintainers to decide?
Anyway, I have resumed the discussion on the original thread [0] because
this has been broken now for the last two kernel releases.
Jon
[0]
https://lore.kernel.org/linux-tegra/8d8b2244-2bf0-48cf-8fb8-9e47e197a62d@nvidia.com/T/#t
--
nvpublic
next prev parent reply other threads:[~2026-05-07 10:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 16:21 [PATCH] firmware: psci: Set pm_set_resume/suspend_via_firmware() for SYSTEM_SUSPEND Manivannan Sadhasivam
2026-03-12 19:00 ` Jon Hunter
2026-03-23 10:10 ` Jon Hunter
2026-03-24 8:45 ` Lorenzo Pieralisi
2026-03-30 20:15 ` Jon Hunter
2026-03-24 8:44 ` Lorenzo Pieralisi
2026-05-07 11:48 ` Manivannan Sadhasivam
2026-03-30 20:48 ` Bjorn Andersson
2026-03-31 6:39 ` Manivannan Sadhasivam
2026-04-06 13:48 ` Bjorn Andersson
2026-04-06 14:29 ` Manivannan Sadhasivam
2026-05-05 13:47 ` Jon Hunter
2026-05-06 17:18 ` Manivannan Sadhasivam
2026-05-07 10:54 ` Jon Hunter [this message]
2026-05-07 11:44 ` Manivannan Sadhasivam
2026-04-02 7:15 ` Maulik Shah (mkshah)
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=49a68039-3a59-4b4c-acbd-0fa917d0e456@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=andersson@kernel.org \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=konrad.dybcio@linaro.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=manivannan.sadhasivam@oss.qualcomm.com \
--cc=mark.rutland@arm.com \
--cc=sudeep.holla@arm.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