Received-SPF: pass (google.com: domain of linux-kernel+bounces-12282-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
From: Konrad Dybcio <konrad.dybcio@linaro.org>
Subject: [PATCH 0/2] Advertise pm_resume/suspend_via_firmware with PSCI
Date: Wed, 27 Dec 2023 23:15:29 +0100
Message-Id: <20231227-topic-psci_fw_sus-v1-0-6910add70bf3@linaro.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: Mark Rutland <mark.rutland@arm.com>, 
 Lorenzo Pieralisi <lpieralisi@kernel.org>
Cc: Marijn Suijten <marijn.suijten@somainline.org>, 
 linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, 
 Bjorn Andersson <andersson@kernel.org>, 
 Konrad Dybcio <konrad.dybcio@linaro.org>

Some device drivers are curious to know if "the firmware" (which to many
just means ACPI, because x86/ibm_pc is clearly the only arch on this
planet :P) is responsible for suspending/resuming the platform, altering
their behavior if that's the case.

The same flag makes sense regardless of the type of firmware used. PSCI
also happens to be the suspend handler on many platforms even without
ACPI, so it's only natural to report such capabilities as well.

Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
---
Konrad Dybcio (2):
      firmware/psci: Set pm_set_resume/suspend_via_firmware() for SYSTEM_SUSPEND
      firmware/psci: Set pm_set_resume/suspend_via_firmware() on qcom

 drivers/firmware/psci/psci.c | 67 +++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 66 insertions(+), 1 deletion(-)
---
base-commit: 39676dfe52331dba909c617f213fdb21015c8d10
change-id: 20231227-topic-psci_fw_sus-a0b0206dc876

Best regards,
-- 
Konrad Dybcio <konrad.dybcio@linaro.org>