From: Esben Haabendal <esben@haabendal.dk>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Richard Weinberger <richard@nod.at>,
Sascha Hauer <s.hauer@pengutronix.de>,
sean@geanix.com, Boris Brezillon <boris.brezillon@collabora.com>,
linux-mtd@lists.infradead.org, martin@geanix.com,
Han Xu <han.xu@nxp.com>
Subject: Re: [PATCH 1/2] mtd: rawnand: gpmi: Fix suspend/resume problem
Date: Fri, 17 Jan 2020 20:48:19 +0100 [thread overview]
Message-ID: <871rrxx3ss.fsf@haabendal.dk> (raw)
In-Reply-To: <20200115094638.1847f475@xps13> (Miquel Raynal's message of "Wed, 15 Jan 2020 09:46:38 +0100")
Miquel Raynal <miquel.raynal@bootlin.com> writes:
> Hi Esben,
>
> Sascha Hauer <s.hauer@pengutronix.de> wrote on Wed, 15 Jan 2020
> 08:46:22 +0100:
>
>> Hi Esben,
>>
>> On Thu, Jan 02, 2020 at 02:08:25PM +0100, Esben Haabendal wrote:
>> > On system resume, the gpmi clock must be enabled before accessing gpmi
>> > block. Without this, resume causes something like
>> >
>> > [ 661.348790] gpmi_reset_block(5cbb0f7e): module reset timeout
>> > [ 661.348889] gpmi-nand 1806000.gpmi-nand: Error setting GPMI : -110
>> > [ 661.348928] PM: dpm_run_callback(): platform_pm_resume+0x0/0x44 returns -110
>> > [ 661.348961] PM: Device 1806000.gpmi-nand failed to resume: error -110
>> >
>> > Signed-off-by: Esben Haabendal <esben@geanix.com>
>> > ---
>> > drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c | 6 ++++++
>> > 1 file changed, 6 insertions(+)
>> >
>> > diff --git a/drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c b/drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c
>> > index 334fe3130285..7ac8c8b95afc 100644
>> > --- a/drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c
>> > +++ b/drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c
>> > @@ -148,6 +148,10 @@ static int gpmi_init(struct gpmi_nand_data *this)
>> > struct resources *r = &this->resources;
>> > int ret;
>> >
>> > + ret = pm_runtime_get_sync(this->dev);
>> > + if (ret < 0)
>> > + return ret;
>>
>> This increases the devices usage counter...
>
> I'm dropping the two patches for now, please resend with this fixed and
> the Fixes/Cc:stable tags added.
>
> I'll freeze the PR at the end of the week.
I will send out revised patches tonight.
/Esben
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2020-01-17 19:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 13:08 [PATCH 1/2] mtd: rawnand: gpmi: Fix suspend/resume problem Esben Haabendal
2020-01-02 13:08 ` [PATCH 2/2] mtd: rawnand: gpmi: Restore nfc timing setup after suspend/resume Esben Haabendal
2020-01-13 17:34 ` Han Xu
2020-01-14 17:03 ` Miquel Raynal
2020-01-07 19:31 ` [PATCH 1/2] mtd: rawnand: gpmi: Fix suspend/resume problem Han Xu
2020-01-09 15:15 ` Miquel Raynal
2020-01-09 17:11 ` Han Xu
2020-01-13 17:32 ` Han Xu
2020-01-14 17:03 ` Miquel Raynal
2020-01-14 17:09 ` Fabio Estevam
2020-01-14 17:25 ` Miquel Raynal
2020-01-14 17:29 ` Fabio Estevam
2020-01-15 7:46 ` Sascha Hauer
2020-01-15 8:46 ` Miquel Raynal
2020-01-17 19:48 ` Esben Haabendal [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=871rrxx3ss.fsf@haabendal.dk \
--to=esben@haabendal.dk \
--cc=boris.brezillon@collabora.com \
--cc=han.xu@nxp.com \
--cc=linux-mtd@lists.infradead.org \
--cc=martin@geanix.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=s.hauer@pengutronix.de \
--cc=sean@geanix.com \
--cc=vigneshr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.