From: Amelie DELAUNAY <amelie.delaunay@st.com>
To: Lee Jones <lee.jones@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@st.com>
Cc: <linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] STMFX power related fixes
Date: Mon, 25 May 2020 14:02:15 +0200 [thread overview]
Message-ID: <f5b3df45-a01a-7cb6-c158-e6edc0117f0f@st.com> (raw)
In-Reply-To: <20200422090833.9743-1-amelie.delaunay@st.com>
Hi,
Gentle reminder regarding this series sent one month ago.
Regards,
Amelie
On 4/22/20 11:08 AM, Amelie Delaunay wrote:
> With suspend/resume tests on STM32MP157C-EV1 board, on which STMFX is used by
> several devices, some errors could occurred: -6 when trying to restore STMFX
> registers, spurious interrupts after disabling supply...
> This patchset fixes all these issues and cleans IRQ init error path.
>
> Amelie Delaunay (3):
> mfd: stmfx: reset chip on resume as supply was disabled
> mfd: stmfx: fix stmfx_irq_init error path
> mfd: stmfx: disable irq in suspend to avoid spurious interrupt
>
> drivers/mfd/stmfx.c | 22 ++++++++++++++++++++--
> include/linux/mfd/stmfx.h | 1 +
> 2 files changed, 21 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2020-05-25 12:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 9:08 Amelie Delaunay
2020-04-22 9:08 ` [PATCH 1/3] mfd: stmfx: reset chip on resume as supply was disabled Amelie Delaunay
2020-05-26 7:57 ` Lee Jones
2020-04-22 9:08 ` [PATCH 2/3] mfd: stmfx: fix stmfx_irq_init error path Amelie Delaunay
2020-05-26 7:58 ` Lee Jones
2020-04-22 9:08 ` [PATCH 3/3] mfd: stmfx: disable irq in suspend to avoid spurious interrupt Amelie Delaunay
2020-05-26 7:59 ` Lee Jones
2020-05-25 12:02 ` Amelie DELAUNAY [this message]
2020-05-26 7:27 ` [PATCH 0/3] STMFX power related fixes Lee Jones
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=f5b3df45-a01a-7cb6-c158-e6edc0117f0f@st.com \
--to=amelie.delaunay@st.com \
--cc=alexandre.torgue@st.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@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®