linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Daniel Mack <daniel@zonque.org>
Cc: Robert Jarzmik <robert.jarzmik@free.fr>,
	Boris Brezillon <boris.brezillon@bootlin.com>,
	David Woodhouse <dwmw2@infradead.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: marvell_nand driver fails to suspend
Date: Mon, 2 Jul 2018 09:20:14 +0200	[thread overview]
Message-ID: <20180702092014.0006fee0@xps13> (raw)
In-Reply-To: <9de339a6-01f9-d3a9-0271-f33933ede35b@zonque.org>

Hi Daniel,

Daniel Mack <daniel@zonque.org> wrote on Sun, 1 Jul 2018 21:04:58 +0200:

> Hi,
> 
> On Sunday, July 01, 2018 12:18 PM, Daniel Mack wrote:
> > I'm seeing the below error when trying to suspend and resume a PXA3xx
> > machine booted from devicetree with the new nand driver. This used to
> > work fine with the old driver, but admittedly, the only kernel I
> > currently have for reference testing is very old (3.0.4), and many other
> > things regarding nand/mtd have also changed since then.  
> > > The suspend/resume implementation in the old driver used to call into  
> > the ->suspend() and ->resume() functions of its mtd_info children
> > directly, but looking at other drivers, it seems this is no longer
> > needed or wanted. It also cleared all interrupts during resume, but that
> > alone doesn't fix it in my tests.  
> > > I haven't followed the development in that area, so I'd appreciate any  
> > hint on how to fix this regression. I'm happy to test patches.  
> 
> I think I figured it out. Will send a patch.

Good to see you figured it out. Indeed there are no more suspend/resume
callbacks, waiting for your patches to fix this.

Thanks,
Miquèl

  reply	other threads:[~2018-07-02  7:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-01 10:18 marvell_nand driver fails to suspend Daniel Mack
2018-07-01 19:04 ` Daniel Mack
2018-07-02  7:20   ` Miquel Raynal [this message]
2018-07-02  7:48     ` Daniel Mack
2018-07-03  7:05       ` Miquel Raynal
2018-07-05  8:22         ` Daniel Mack
2018-07-06  8:27           ` Miquel Raynal
2018-07-06  8:41             ` Daniel Mack
2018-07-06  9:02               ` Miquel Raynal
2018-07-06 20:07                 ` 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=20180702092014.0006fee0@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=boris.brezillon@bootlin.com \
    --cc=daniel@zonque.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).