From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
linux-arm-kernel@vger.kernel.org
Cc: drv@mailo.com, ssengar@microsoft.com,
kumarpraveen@linux.microsoft.com, christophe.jaillet@wanadoo.fr,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Nick Desaulniers <ndesaulniers@google.com>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
Arnd Bergmann <arnd@arndb.de>, Miaoqian Lin <linmq006@gmail.com>,
Liang He <windhl@126.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Julia Lawall <Julia.Lawall@inria.fr>,
open list <linux-kernel@vger.kernel.org>,
"moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] soc: bcm: brcmstb: Remove bare-metal ARM suspend/resume code
Date: Mon, 27 Feb 2023 15:43:16 -0300 [thread overview]
Message-ID: <f4c440ef-e0ec-ea07-71b2-3fd3c4d52088@igalia.com> (raw)
In-Reply-To: <35dc0b00-0de4-f1b4-8d43-7efd181e7dbf@gmail.com>
On 27/02/2023 15:38, Florian Fainelli wrote:
> [...]
>>> -static int brcmstb_pm_panic_notify(struct notifier_block *nb,
>>> - unsigned long action, void *data)
>>> -{
>>> - writel_relaxed(BRCMSTB_PANIC_MAGIC, ctrl.aon_sram + AON_REG_PANIC);
>>> -
>>> - return NOTIFY_DONE;
>>> [...]
>>
>> Hi Florian, thanks for the clean-up!
>>
>> I'm curious with the above panic notifier - is it not necessary when
>> PSCI is used?
>
> This is a bit of long story, but no, it is not necessary.
OK then heh
Glad for the clean-up!
next prev parent reply other threads:[~2023-02-27 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 21:52 Florian Fainelli
2023-02-27 18:36 ` Guilherme G. Piccoli
2023-02-27 18:38 ` Florian Fainelli
2023-02-27 18:43 ` Guilherme G. Piccoli [this message]
2023-03-14 21:12 ` Florian Fainelli
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=f4c440ef-e0ec-ea07-71b2-3fd3c4d52088@igalia.com \
--to=gpiccoli@igalia.com \
--cc=Julia.Lawall@inria.fr \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=drv@mailo.com \
--cc=f.fainelli@gmail.com \
--cc=kumarpraveen@linux.microsoft.com \
--cc=linmq006@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-kernel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=ssengar@microsoft.com \
--cc=windhl@126.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®