From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: computersforpeace@gmail.com, f.fainelli@gmail.com
Cc: gpiccoli@igalia.com, "Guilherme G. Piccoli" <kernel@gpiccoli.net>,
opendmb@gmail.com, gpowell@broadcom.com, justinpopo6@gmail.com,
mmayer@broadcom.com, bcm-kernel-feedback-list@broadcom.com,
kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Question about the Broadcom Always On register panic handling
Date: Mon, 21 Mar 2022 13:15:41 -0300 [thread overview]
Message-ID: <6dac422b-d509-b863-0b31-98a07808ac0d@igalia.com> (raw)
Hi Brian and Florian, I'm studying the panic notifiers and found one
added by you in the commit 0b741b8234c ("soc: bcm: brcmstb: Add support
for S2/S3/S5 suspend states (ARM)". Basically, the handler is very
simple and the only thing it does is:
/* from drivers/soc/bcm/brcmstb/pm/aon_defs.h */
#define AON_REG_PANIC 0x20
#define BRCMSTB_PANIC_MAGIC 0x512E115E
/* from drivers/soc/bcm/brcmstb/pm/pm-arm.c*/
brcmstb_pm_panic_notify() {
writel_relaxed(BRCMSTB_PANIC_MAGIC, ctrl.aon_sram + AON_REG_PANIC);
}
This write happens on panic time, but I couldn't find any
information/documentation about the AON register and what effectively
happens when this write is completed. Does the SoC reboots or anything
like that?
Any information that helps me to document such panic event is very
welcome, and in case you have AON documentation, it'd be also pretty great!
Thanks in advance,
Guilherme
next reply other threads:[~2022-03-21 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 16:15 Guilherme G. Piccoli [this message]
2022-03-21 16:32 ` Florian Fainelli
2022-03-21 18:04 ` Guilherme G. Piccoli
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=6dac422b-d509-b863-0b31-98a07808ac0d@igalia.com \
--to=gpiccoli@igalia.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=gpowell@broadcom.com \
--cc=justinpopo6@gmail.com \
--cc=kernel@gpiccoli.net \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmayer@broadcom.com \
--cc=opendmb@gmail.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®