From: Daniel Mack <daniel@zonque.org>
To: Boris Brezillon <boris.brezillon@bootlin.com>
Cc: miquel.raynal@bootlin.com, robert.jarzmik@free.fr,
dwmw2@infradead.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH 3/3] mtd: rawnand: marvell: add suspend and resume hooks
Date: Sat, 7 Jul 2018 00:15:50 +0200 [thread overview]
Message-ID: <c7a90dd5-e474-bca4-cd35-c8ccce05edcc@zonque.org> (raw)
In-Reply-To: <20180706232239.269a8d61@bbrezillon>
Hi,
On 07/06/2018 11:22 PM, Boris Brezillon wrote:
> On Fri, 6 Jul 2018 22:14:15 +0200
> Daniel Mack <daniel@zonque.org> wrote:
>
>> This patch restores the suspend and resume hooks that the old driver used
>> to have. Apart from stopping and starting the clocks, the resume callback
>> also nullifies the selected_chip pointer, so the next command that is issued
>> will re-select the chip and thereby restore the timing registers.
>>
>> Without this patch, a PXA3xx based system would cough up an error similar to
>> the one below after resume.
>>
>> [ 44.660162] marvell-nfc 43100000.nand-controller: Timeout waiting for RB signal
>> [ 44.671492] ubi0 error: ubi_io_write: error -110 while writing 2048 bytes to PEB 102:38912, written 0 bytes
>> [ 44.682887] CPU: 0 PID: 1417 Comm: remote-control Not tainted 4.18.0-rc2+ #344
>> [ 44.691197] Hardware name: Marvell PXA3xx (Device Tree Support)
>> [ 44.697111] Backtrace:
>> [ 44.699593] [<c0106458>] (dump_backtrace) from [<c0106718>] (show_stack+0x18/0x1c)
>> [ 44.708931] r7:00000800 r6:00009800 r5:00000066 r4:c6139000
>> [ 44.715833] [<c0106700>] (show_stack) from [<c0678a60>] (dump_stack+0x20/0x28)
>> [ 44.724206] [<c0678a40>] (dump_stack) from [<c0456cbc>] (ubi_io_write+0x3d4/0x630)
>> [ 44.732925] [<c04568e8>] (ubi_io_write) from [<c0454428>] (ubi_eba_write_leb+0x690/0x6fc)
>> ...
>>
>> Signed-off-by: Daniel Mack <daniel@zonque.org>
>
> You probably want patch 2 and 3 backported to stable.
Given that nobody has cared so far and the only board that depends on
proper PM that seems to be using this driver has bitrot quite badly in
the past and is undergoing a major rewrite currently, I'm not sure
whether it's worth it really.
I can do it if you insist though.
Thanks,
Daniel
next prev parent reply other threads:[~2018-07-06 22:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 20:14 [PATCH 1/3] mtd: rawnand: marvell: remove bogus comment in marvell_nfc_select_chip() Daniel Mack
2018-07-06 20:14 ` [PATCH 2/3] mtd: rawnand: marvell: set reg_clk to NULL if it can't be obtained Daniel Mack
2018-07-06 20:14 ` [PATCH 3/3] mtd: rawnand: marvell: add suspend and resume hooks Daniel Mack
2018-07-06 21:22 ` Boris Brezillon
2018-07-06 22:15 ` Daniel Mack [this message]
2018-07-06 22:26 ` Daniel Mack
2018-07-07 6:07 ` Boris Brezillon
2018-07-07 6:14 ` Boris Brezillon
2018-07-07 6:23 ` Daniel Mack
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=c7a90dd5-e474-bca4-cd35-c8ccce05edcc@zonque.org \
--to=daniel@zonque.org \
--cc=boris.brezillon@bootlin.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=robert.jarzmik@free.fr \
/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.