mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
To: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"vigneshr@ti.com" <vigneshr@ti.com>
Cc: "s-vadapalli@ti.com" <s-vadapalli@ti.com>,
	"afd@ti.com" <afd@ti.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"j-choudhary@ti.com" <j-choudhary@ti.com>
Subject: Re: [PATCH v2 3/3] soc: ti: k3-socinfo: Provide reset reason information
Date: Tue, 17 Mar 2026 06:59:22 +0000	[thread overview]
Message-ID: <9dfc175b64964919480d8f7c9867ba0110bd4033.camel@siemens.com> (raw)
In-Reply-To: <7ff12e4d-a1c4-4a7f-b80c-62b68f698672@ti.com>

Hi Vignesh!

On Tue, 2026-03-17 at 11:18 +0530, Vignesh Raghavendra wrote:
> > and later SoCs of K3 family. Textual representation of the bits was taken
> > from the AM62x Processors Technical Reference Manual, except the POR, which
> > is not signalled explicitly by the reset module.
> > 
> > Signed-off-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>
> 
> 
> There is support dumping reset reason in U-Boot for AM64x:
> https://elixir.bootlin.com/u-boot/v2026.01/source/arch/arm/mach-k3/am64x/boot.c#L107
> 
> This conflicts with kernel as U-Boot currently clears the RST_SRC after read (Its
> necessary to do so, to detect additional resets at bootloader level). So, this
> information would be lost by the time kernel driver comes up.
> 
> Is there a usecase where kernel can make use of reset reason information exposed
> via this driver? If so, the driver should at least take a cmdline param from 
> bootloader in order to overcome above issue.

Thanks for the hint!
Too bad my U-Boot is that old I didn't notice it! ;-)

But your point makes the whole series pointless of course. We do need this
info for diagnostics, but seems that I need to look into U-Boot for the
implementation...

> > ---
> > Changelog:
> > v2: no changes
> > 
> >   drivers/soc/ti/k3-socinfo.c | 88 +++++++++++++++++++++++++++++++++++++
> >   1 file changed, 88 insertions(+)
> > 
> > diff --git a/drivers/soc/ti/k3-socinfo.c b/drivers/soc/ti/k3-socinfo.c
> > index 676041879eca3..3736c982fd0c8 100644
> > --- a/drivers/soc/ti/k3-socinfo.c
> > +++ b/drivers/soc/ti/k3-socinfo.c

-- 
Alexander Sverdlin
Siemens AG
www.siemens.com

      reply	other threads:[~2026-03-17  6:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16  7:04 [PATCH v2 0/3] ARM: soc: ti: k3: Provide reset cause information A. Sverdlin
2026-03-16  7:04 ` [PATCH v2 1/3] dt-bindings: mfd: syscon: add binding for TI K3 platforms reset registers A. Sverdlin
2026-03-16  8:21   ` Rob Herring (Arm)
2026-03-16  7:04 ` [PATCH v2 2/3] arm64: dts: ti: k3-*: Add am64x and newer " A. Sverdlin
2026-03-16  7:04 ` [PATCH v2 3/3] soc: ti: k3-socinfo: Provide reset reason information A. Sverdlin
2026-03-17  5:48   ` Vignesh Raghavendra
2026-03-17  6:59     ` Sverdlin, Alexander [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=9dfc175b64964919480d8f7c9867ba0110bd4033.camel@siemens.com \
    --to=alexander.sverdlin@siemens.com \
    --cc=afd@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=j-choudhary@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s-vadapalli@ti.com \
    --cc=vigneshr@ti.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®