From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Florian Fainelli <f.fainelli@gmail.com>, computersforpeace@gmail.com
Cc: "Guilherme G. Piccoli" <kernel@gpiccoli.net>,
opendmb@gmail.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: Re: Question about the Broadcom Always On register panic handling
Date: Mon, 21 Mar 2022 15:04:34 -0300 [thread overview]
Message-ID: <307799df-fddd-6c46-7dd5-323ea5628892@igalia.com> (raw)
In-Reply-To: <781cafb0-8d06-8b56-907a-5175c2da196a@gmail.com>
On 21/03/2022 13:32, Florian Fainelli wrote:
> [...]
> The AON (standing for always-on) is a small domain in the SoC that can
> retain its state across various system wide sleep states and specific
> reset conditions. The AON DATA RAM is a small ram of a few words (< 1KB)
> which can store persistent information across such events.
>
> The purpose of this write was initially to help with indicating to the
> boot loader that a panic occurred and so that it should try its best to
> preserve the DRAM contents holding that buffer for recovery by the Linux
> kernel as opposed to wiping out DRAM clean again. I cannot go into the
> mechanics of what happens publicly unfortunately.
>
Thanks a lot Florian! This is very good information, it's enough for me
- I'd like to be sure it's not rebooting the board or something
"extreme" like that, so in the end...it's kinda the opposite, it's
preserving the DRAM.
>>
>> 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!
>
> Why are you asking specifically about this if I may ask? If you are a
> legitimate Broadcom STB customer you can reach out to our support and I
> am sure the question will come back for me to answer.
Oh I'm not a Broadcom STB customer, I'm just working in the panic
notifiers and was curious about this one. When I submit my series (soon)
it's likely that there will be a small refactor of this notifier plus a
comment, with your great explanation.
Regarding the full AON documentation, I just asked in case it's public
and I couldn't find - it's unfortunate that a lot of code in the kernel
is based on closed specifications, but I understand we can't do much
about that. Your response was very useful, and enough for my work =)
Cheers,
Guilherme
prev parent reply other threads:[~2022-03-21 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 16:15 Guilherme G. Piccoli
2022-03-21 16:32 ` Florian Fainelli
2022-03-21 18:04 ` Guilherme G. Piccoli [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=307799df-fddd-6c46-7dd5-323ea5628892@igalia.com \
--to=gpiccoli@igalia.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=f.fainelli@gmail.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®