lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-Id: <20231227-topic-psci_fw_sus-v1-0-6910add70bf3@linaro.org> Date: Wed, 27 Dec 2023 23:15:29 +0100 From: Konrad Dybcio <konrad.dybcio@...aro.org> To: Mark Rutland <mark.rutland@....com>, Lorenzo Pieralisi <lpieralisi@...nel.org> Cc: Marijn Suijten <marijn.suijten@...ainline.org>, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, Bjorn Andersson <andersson@...nel.org>, Konrad Dybcio <konrad.dybcio@...aro.org> Subject: [PATCH 0/2] Advertise pm_resume/suspend_via_firmware with PSCI 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@...aro.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@...aro.org>
Powered by blists - more mailing lists