From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Faruque Ansari <faruque.ansari@oss.qualcomm.com>,
Sebastian Reichel <sre@kernel.org>,
Benson Leung <bleung@chromium.org>,
Tzung-Bi Shih <tzungbi@kernel.org>,
Guenter Roeck <groeck@chromium.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Matti Vaittinen <mazziesaccount@gmail.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, chrome-platform@lists.linux.dev,
avaneesh.dwivedi@oss.qualcomm.com,
Umang Chheda <umang.chheda@oss.qualcomm.com>,
Ulf Hansson <ulfh@kernel.org>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Bradley Morgan <brads@mainlining.org>
Subject: Re: [PATCH v17 4/6] reboot: extend psc_reason with power-on and reset causes
Date: Mon, 19 Oct 2026 09:58:54 +0200 [thread overview]
Message-ID: <707c12dd-6e03-485e-a913-d7f0c719c126@oss.qualcomm.com> (raw)
In-Reply-To: <20261019-pscrr-framework-v17-4-69ea6cdf4731@oss.qualcomm.com>
On 10/19/26 09:38, Faruque Ansari wrote:
> psc_reason covered only the protection reasons. Extend it to mirror the
> full POWER_ON_REASON_* vocabulary - power-on, watchdog, software,
> external, RTC, reset button, CPU clock and crystal failures - so a
> provider can report why the system last powered on, not only why it was
> shut down. New values are appended to keep the existing numeric ABI.
>
> Co-developed-by: Oleksij Rempel <o.rempel@pengutronix.de>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> Reviewed-by: Matti Vaittinen <mazziesaccount@gmail.com>
> Reviewed-by: Bradley Morgan <brads@mainlining.org>
> Signed-off-by: Faruque Ansari <faruque.ansari@oss.qualcomm.com>
>
> changes v16:
> - Add Reviewed-by tag from Bradley Morgan.
> changes v15:
> - add a static_assert() tying ARRAY_SIZE(psc_reason_descs) to
> PSCR_REASON_COUNT, so a future enum addition without a matching
> table entry fails the build instead of silently reading a hole
> (Matti Vaittinen)
> - Add Reviewed-by tags from Matti Vaittinen.
> changes v12:
> - new patch
> ---
Reviewed-by: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
next prev parent reply other threads:[~2026-10-19 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 7:38 [PATCH v17 0/6] power: reset: Introduce the Power State Change Reasons Recording (PSCRR) framework Faruque Ansari
2026-10-19 7:38 ` [PATCH v17 1/6] power: Extend power_on_reason.h for upcoming PSCRR framework Faruque Ansari
2026-10-19 7:38 ` [PATCH v17 2/6] reboot: hw_protection_trigger: use standardized numeric shutdown/reboot reasons instead of strings Faruque Ansari
2026-10-19 7:38 ` [PATCH v17 3/6] reboot: add parsable tokens for power state change reasons Faruque Ansari
2026-10-19 7:38 ` [PATCH v17 4/6] reboot: extend psc_reason with power-on and reset causes Faruque Ansari
2026-10-19 7:58 ` Daniel Lezcano [this message]
2026-10-19 7:38 ` [PATCH v17 5/6] power: reset: Introduce PSCR Recording Framework for Non-Volatile Storage Faruque Ansari
2026-10-19 7:38 ` [PATCH v17 6/6] Documentation: Add sysfs documentation for PSCRR Faruque Ansari
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=707c12dd-6e03-485e-a913-d7f0c719c126@oss.qualcomm.com \
--to=daniel.lezcano@oss.qualcomm.com \
--cc=avaneesh.dwivedi@oss.qualcomm.com \
--cc=bleung@chromium.org \
--cc=brads@mainlining.org \
--cc=broonie@kernel.org \
--cc=chrome-platform@lists.linux.dev \
--cc=daniel.lezcano@kernel.org \
--cc=faruque.ansari@oss.qualcomm.com \
--cc=groeck@chromium.org \
--cc=kernel@pengutronix.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mazziesaccount@gmail.com \
--cc=o.rempel@pengutronix.de \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=sebastian.reichel@collabora.com \
--cc=sre@kernel.org \
--cc=tzungbi@kernel.org \
--cc=ulfh@kernel.org \
--cc=umang.chheda@oss.qualcomm.com \
/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
all inboxes | Powered by JetHome®