[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211129101908.6f1aa715@xps13>
Date: Mon, 29 Nov 2021 10:19:08 +0100
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Boris Brezillon <boris.brezillon@...labora.com>
Cc: Sean Nyekjaer <sean@...nix.com>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
Boris Brezillon <bbrezillon@...nel.org>,
linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 3/4] mtd: core: protect access to MTD devices while
in suspend
Hi Sean,
boris.brezillon@...labora.com wrote on Tue, 23 Nov 2021 14:07:15 +0100:
> On Tue, 23 Nov 2021 13:50:12 +0100
> Sean Nyekjaer <sean@...nix.com> wrote:
>
> > @Boris do we need to do something similar here to what we did with the
> > mtdconcat stuff?
>
> Absolutely, physmasp subdevices are never initialized/registered, so
> you can't call any of the mtd helpers taking the suspend lock on those.
> I guess it'd be better to call mtd_suspend/resume() on the concat device
> in though:
Any chance that you will come up with a fix or v6 of the series anytime
soon?
>
> static void physmap_flash_shutdown(struct platform_device *dev)
> {
> struct physmap_flash_info *info = platform_get_drvdata(dev);
>
> mtd_suspend(info->cmtd);
> }
Thanks,
Miquèl
Powered by blists - more mailing lists