From: Shivendra Pratap <shivendra.pratap@oss.qualcomm.com>
To: sashiko-reviews@lists.linux.dev
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org,
lee@kernel.org, mfd@lists.linux.dev
Subject: Re: [PATCH v24 06/12] power: reset: Add psci-reboot-mode driver
Date: Mon, 3 Aug 2026 18:37:11 +0530 [thread overview]
Message-ID: <f18569ad-3e39-4d48-9ed0-968af4e31c40@oss.qualcomm.com> (raw)
In-Reply-To: <20260803101117.C91CF1F0155B@smtp.kernel.org>
On 8/3/2026 3:41 PM, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
> - [High] The `psci-reboot-mode` driver is completely unreachable and non-functional because it is never instantiated.
> - [High] Standard 'normal' reboot mode commands are entirely ignored by PSCI due to an incorrect `data` check in the restart handler.
> --
[snip..]
>> +static int psci_reboot_mode_write(struct reboot_mode_driver *reboot,
>> + const u32 *magic, u32 count)
>> +{
>> + (void)reboot;
>> +
>> + if (count < 1 || count > 3)
>> + return -EINVAL;
>> +
>> + return psci_set_reset_cmd(magic[0], psci_reboot_mode_get_cookie(magic, count));
>
> [Severity: High]
> Does this work for standard "normal" reboots?
>
> When a standard reboot is triggered without a specific command string, the
> reboot_mode framework translates the NULL command to "normal" mode and calls
> this write function to configure the reset command.
No, write can be called only if a mode entry is found that matches name
"normal". And there is no mode name defined here as "normal".
>
> However, in drivers/firmware/psci/psci.c, psci_sys_reset() skips applying
> the command because it checks for a non-NULL data argument:
> drivers/firmware/psci/psci.c:psci_sys_reset() {
> ...
> cmd = smp_load_acquire(&reset_cmd);
> if (data && cmd && !panic_in_progress())
> psci_handle_reset_cmd(cmd);
>
> psci_handle_reboot_mode();
> ...
> }
>
> Will this cause standard reboots mapped to vendor-specific commands to be
> silently ignored?
does not affects.
>
>> +}
> [ ... ]
>> +static struct platform_driver psci_reboot_mode_driver = {
>> + .probe = psci_reboot_mode_probe,
>> + .driver = {
>> + .name = "psci-reboot-mode",
>> + },
>> +};
>
> [Severity: High]
> Is this driver ever instantiated?
>
this is probed as psci-mfd child.
thanks,
Shivendra
next prev parent reply other threads:[~2026-08-03 13:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 9:43 [PATCH v24 00/12] Implement PSCI reboot mode driver for PSCI resets Shivendra Pratap
2026-08-03 9:43 ` [PATCH v24 01/12] power: reset: reboot-mode: Support up to 3 magic values per mode Shivendra Pratap
2026-08-03 9:56 ` sashiko-bot
2026-08-03 9:43 ` [PATCH v24 02/12] power: reset: reboot-mode: Add support for predefined reboot modes Shivendra Pratap
2026-08-03 9:59 ` sashiko-bot
2026-08-04 14:19 ` Shivendra Pratap
2026-08-03 9:43 ` [PATCH v24 03/12] firmware: psci: Introduce command-based resets Shivendra Pratap
2026-08-03 10:01 ` sashiko-bot
2026-08-04 14:38 ` Shivendra Pratap
2026-08-03 9:43 ` [PATCH v24 04/12] mfd: psci-mfd: Add PSCI MFD driver for cpuidle-psci-domain cell Shivendra Pratap
2026-08-03 10:00 ` sashiko-bot
2026-08-03 9:43 ` [PATCH v24 05/12] dt-bindings: arm: Document reboot mode magic Shivendra Pratap
2026-08-03 10:09 ` sashiko-bot
2026-08-03 11:44 ` Rob Herring (Arm)
2026-08-03 12:46 ` Shivendra Pratap
2026-08-03 14:02 ` Rob Herring
2026-08-03 14:21 ` Shivendra Pratap
2026-08-03 9:43 ` [PATCH v24 06/12] power: reset: Add psci-reboot-mode driver Shivendra Pratap
2026-08-03 10:11 ` sashiko-bot
2026-08-03 13:07 ` Shivendra Pratap [this message]
2026-08-03 9:43 ` [PATCH v24 07/12] mfd: core: Add firmware-node support to MFD cells Shivendra Pratap
2026-08-03 10:07 ` sashiko-bot
2026-08-03 9:43 ` [PATCH v24 08/12] mfd: psci-mfd: Add psci-reboot-mode child cell Shivendra Pratap
2026-08-03 10:07 ` sashiko-bot
2026-08-03 12:52 ` Shivendra Pratap
2026-08-03 9:43 ` [PATCH v24 09/12] arm64: dts: qcom: Add psci reboot-modes for kodiak boards Shivendra Pratap
2026-08-03 10:13 ` sashiko-bot
2026-08-03 9:43 ` [PATCH v24 10/12] arm64: dts: qcom: Add psci reboot-modes for lemans boards Shivendra Pratap
2026-08-03 10:15 ` sashiko-bot
2026-08-03 9:43 ` [PATCH v24 11/12] arm64: dts: qcom: Add psci reboot-modes for monaco boards Shivendra Pratap
2026-08-03 10:13 ` sashiko-bot
2026-08-03 9:43 ` [PATCH v24 12/12] arm64: dts: qcom: Add psci reboot-modes for talos boards Shivendra Pratap
2026-08-03 10:14 ` sashiko-bot
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=f18569ad-3e39-4d48-9ed0-968af4e31c40@oss.qualcomm.com \
--to=shivendra.pratap@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee@kernel.org \
--cc=mfd@lists.linux.dev \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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