From: Fabien Dessenne <fabien.dessenne@st.com>
To: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
<devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>
Cc: Fabien Dessenne <fabien.dessenne@st.com>,
Loic Pallardy <loic.pallardy@st.com>,
Arnaud Pouliquen <arnaud.pouliquen@st.com>
Subject: [PATCH 0/2] remoteproc: stm32: allow wdg irq to be a wakeup source
Date: Mon, 26 Aug 2019 17:38:41 +0200 [thread overview]
Message-ID: <1566833923-16718-1-git-send-email-fabien.dessenne@st.com> (raw)
The watchdog IRQ which notifies the remote processor crash is used by the
remoteproc framework to perform a recovery procedure.
Since this IRQ may be fired when the Linux system is suspended, this IRQ may
be configured to wake up the system.
Fabien Dessenne (2):
dt-bindings: remoteproc: stm32: add wakeup-source
remoteproc: stm32: wakeup the system by wdg irq
.../devicetree/bindings/remoteproc/stm32-rproc.txt | 3 ++
drivers/remoteproc/stm32_rproc.c | 47 ++++++++++++++++++++++
2 files changed, 50 insertions(+)
--
2.7.4
next reply other threads:[~2019-08-26 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 15:38 Fabien Dessenne [this message]
2019-08-26 15:38 ` [PATCH 1/2] dt-bindings: remoteproc: stm32: add wakeup-source Fabien Dessenne
2019-08-29 22:57 ` Rob Herring
2019-08-26 15:38 ` [PATCH 2/2] remoteproc: stm32: wakeup the system by wdg irq Fabien Dessenne
2019-10-10 15:16 ` [PATCH 0/2] remoteproc: stm32: allow wdg irq to be a wakeup source Fabien DESSENNE
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=1566833923-16718-1-git-send-email-fabien.dessenne@st.com \
--to=fabien.dessenne@st.com \
--cc=alexandre.torgue@st.com \
--cc=arnaud.pouliquen@st.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=loic.pallardy@st.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=ohad@wizery.com \
--cc=robh+dt@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 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®