All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
To: "devicetree-spec@vger.kernel.org" <devicetree-spec@vger.kernel.org>
Subject: [RFC] Pass reset reason to Linux via FDT
Date: Tue, 12 May 2026 07:27:17 +0000	[thread overview]
Message-ID: <579fcbc186ad2aeea3c206aebc901b64fc665db1.camel@siemens.com> (raw)

Dear Device Tree Spec Team!

I would like to receive your opinion on the new /chosen/reset-reason property
I would like to introduce in the spec and consequently in the U-Boot.

I've posted an U-Boot patchset [1] with the proposed implementation which
would work on TI K3 SoCs initially.

- Do you think I need to send a formal patch to device tree spec?
- Do you think /chosen/reset-reason is the proper location for the SoC/platform
  agnostic reset cause information?
- Do you think having an opaque string there is OK, bearing in mind that there
  is no standard approach up to now to this topic, neither in Linux nor in
  U-Boot, taking into account different SoCs and vendors provide very different
  information regarding reset cause, which is barely possible to unify?

The proposed change would look like following:

diff --git a/dtschema/schemas/chosen.yaml b/dtschema/schemas/chosen.yaml
index 63f3c12..d908426 100644
--- a/dtschema/schemas/chosen.yaml
+++ b/dtschema/schemas/chosen.yaml
@@ -183,6 +183,20 @@ properties:
       will assign devices in its usual manner, otherwise it will not try to
       assign devices and instead use them as they are configured already.
 
+  reset-reason:
+    $ref: types.yaml#/definitions/string
+    description:
+      This property is set by the bootloader to indicate the reason for the
+      most recent system reset, e.g. "POR" (power-on reset), "WDOG" (watchdog),
+      "PIN" (external reset pin), "RST" (software warm reset), "THERMAL", etc.
+      The set of possible values is platform-specific.
+
+      / {
+              chosen {
+                      reset-reason = "WDOG";
+              };
+      };
+
   smbios3-entrypoint:
     $ref: types.yaml#/definitions/address
     maxItems: 1

[1] https://www.mail-archive.com/u-boot@lists.denx.de/msg573811.html

-- 
Alexander Sverdlin
Siemens AG
www.siemens.com

             reply	other threads:[~2026-05-12  7:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12  7:27 Sverdlin, Alexander [this message]
2026-05-12 15:29 ` [RFC] Pass reset reason to Linux via FDT Quentin Schulz
2026-05-13  8:53   ` Sverdlin, Alexander

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=579fcbc186ad2aeea3c206aebc901b64fc665db1.camel@siemens.com \
    --to=alexander.sverdlin@siemens.com \
    --cc=devicetree-spec@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.