From: Dan Carpenter <error27@gmail.com>
To: Aayush7352 <aayushdixit924@gmail.com>
Cc: linux-staging@lists.linux.dev, Marc Dietrich <marvin24@gmx.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] staging: nvec: fix power-off path to not depend on workqueue
Date: Tue, 21 Jul 2026 12:26:06 +0300 [thread overview]
Message-ID: <al87LpFW487A7DXH@stanley.mountain> (raw)
In-Reply-To: <20260721084727.79305-1-aayushdixit924@gmail.com>
On Tue, Jul 21, 2026 at 02:17:27PM +0530, Aayush7352 wrote:
You need to use your real name.
> nvec_power_off() uses nvec_write_async() which queues work via schedule_work().
> During system shutdown or reboot, workqueues may be frozen, so the
> AP_PWR_DOWN message never reaches the embedded controller and the
> system hangs instead of powering off.
>
> Fix by calling nvec_request_master() directly after queuing the power-off
> messages, processing the TX queue synchronously in the power-off context.
> Also add a NULL guard for nvec_power_handle.
>
> This addresses the TODO item "add atomic ops in order to fix shutoff/reboot
> problems" in drivers/staging/nvec/TODO.
Missing signed off by line.
> ---
^^^
This is a common thing where people ask the AI to fix the todo... You
need to say under the --- cut off line that the patch has not been
tested.
The TODO is kind of vague. "add atomic ops in order to fix
shutoff/reboot"... I suppose this could be the fix for it?? Anyway,
Marc wrote that todo so we'll see if that's what he meant.
regards,
dan carpenter
prev parent reply other threads:[~2026-07-21 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 8:47 [PATCH 1/1] staging: nvec: fix power-off path to not depend on workqueue Aayush7352
2026-07-21 9:26 ` Dan Carpenter [this message]
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=al87LpFW487A7DXH@stanley.mountain \
--to=error27@gmail.com \
--cc=aayushdixit924@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=marvin24@gmx.de \
/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