summaryrefslogtreecommitdiff
path: root/drivers/sysreset/sysreset_qcom-psci.c
diff options
context:
space:
mode:
authorQuentin Schulz <[email protected]>2026-07-03 18:43:32 +0200
committerTom Rini <[email protected]>2026-07-03 13:45:58 -0600
commitc480bbd92b3273ecff5396da9221e7bcb08774ba (patch)
treee93449cf48dc80949df0bf2953da347af217ec00 /drivers/sysreset/sysreset_qcom-psci.c
parentf605dcee103c897b6f1a8873549a36949bd4e2a1 (diff)
drivers: sysreset: revert support for args in request
This reverts: - commit e49c84f7bb7b ("doc: usage: cmd: reset: specify when the -edl option is available") - commit 1076feb8a3f9 ("cmd: boot: fix edl being shown when not supported") - commit 63c806ba0e12 ("qcom_defconfig: enable psci based sysreset") - commit ef06c5d76ff4 ("cmd: boot: Add '-edl' option to reset command documentation") - commit 32825eaddc37 ("sysreset: Implement PSCI based reset to EDL mode for QCOM SoCs") - commit fcb48b89813b ("drivers: sysreset: Add sysreset op that can take arguments") There was a conflict reverting commit 63c806ba0e12 ("qcom_defconfig: enable psci based sysreset") due to commit 02ef1859b44f ("configs: Resync with savedefconfig"), but the conflict resolution was trivial. The args support for the sysreset uclass contains a logic bug. The first sysreset device implementing the request_arg callback will consume the args, not support the specified arg and thus return -EPROTONOSUPPORT which will stop the iteration over all sysreset devices. This is an issue if one has multiple sysreset devices and each with support for different (valid) args. If a sysreset device implements a -dummy argument and another -foo and a user calls reset -dummy from the U-Boot CLI, it'll depend on which sysreset device will be attempted first. If it is the one implementing -foo, it'll return it doesn't support the argument with -EPROTONOSUPPORT in which case the device implementing -dummy will never be attempted and instead we'll do a cold reset which is very likely not what's expected from the user. Casey suggested[1] we revert this and start from scratch again with a different implementation instead. [1] https://lore.kernel.org/u-boot/[email protected]/ Acked-by: Casey Connolly <[email protected]> Signed-off-by: Quentin Schulz <[email protected]>
Diffstat (limited to 'drivers/sysreset/sysreset_qcom-psci.c')
-rw-r--r--drivers/sysreset/sysreset_qcom-psci.c45
1 files changed, 0 insertions, 45 deletions
diff --git a/drivers/sysreset/sysreset_qcom-psci.c b/drivers/sysreset/sysreset_qcom-psci.c
deleted file mode 100644
index 3627bbf5c82..00000000000
--- a/drivers/sysreset/sysreset_qcom-psci.c
+++ /dev/null
@@ -1,45 +0,0 @@
-// SPDX-License-Identifier: GPL-2.0+
-/*
- * Copyright (C) 2017 Masahiro Yamada <[email protected]>
- * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
- */
-
-#include <dm.h>
-#include <sysreset.h>
-#include <asm/system.h>
-#include <linux/errno.h>
-#include <linux/psci.h>
-#include <asm/psci.h>
-
-static int qcom_psci_sysreset_get_status(struct udevice *dev, char *buf, int size)
-{
- return -EOPNOTSUPP;
-}
-
-static int qcom_psci_sysreset_request_arg(struct udevice *dev, int argc,
- char * const argv[])
-{
- if (!strncasecmp(argv[1], "-edl", 4)) {
- /* Supported in qcs9100, qcs8300, sc7280, qcs615 */
- if (psci_features(ARM_PSCI_1_1_FN64_SYSTEM_RESET2) ==
- ARM_PSCI_RET_SUCCESS) {
- psci_system_reset2(0, 1);
- return -EINPROGRESS;
- }
- printf("PSCI SYSTEM_RESET2 not supported\n");
- }
-
- return -EPROTONOSUPPORT;
-}
-
-static struct sysreset_ops qcom_psci_sysreset_ops = {
- .request_arg = qcom_psci_sysreset_request_arg,
- .get_status = qcom_psci_sysreset_get_status,
-};
-
-U_BOOT_DRIVER(qcom_psci_sysreset) = {
- .name = "qcom_psci-sysreset",
- .id = UCLASS_SYSRESET,
- .ops = &qcom_psci_sysreset_ops,
- .flags = DM_FLAG_PRE_RELOC,
-};