From: Boris Brezillon <boris.brezillon@collabora.com>
To: Sean Nyekjaer <sean@geanix.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Boris Brezillon <bbrezillon@kernel.org>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] mtd: mtdconcat: add suspend lock handling
Date: Mon, 11 Oct 2021 15:27:03 +0200 [thread overview]
Message-ID: <20211011152703.0086d990@collabora.com> (raw)
In-Reply-To: <20211011151501.48cc9289@collabora.com>
On Mon, 11 Oct 2021 15:15:01 +0200
Boris Brezillon <boris.brezillon@collabora.com> wrote:
> On Mon, 11 Oct 2021 13:52:53 +0200
> Sean Nyekjaer <sean@geanix.com> wrote:
>
> > Use new suspend lock handling for this special case for concatenated
> > MTD devices.
> >
> > Fixes: 013e6292aaf5 ("mtd: rawnand: Simplify the locking")
> > Signed-off-by: Sean Nyekjaer <sean@geanix.com>
> > ---
> > drivers/mtd/mtdconcat.c | 11 +++++++++--
> > 1 file changed, 9 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/mtd/mtdconcat.c b/drivers/mtd/mtdconcat.c
> > index f685a581df48..c497c851481f 100644
> > --- a/drivers/mtd/mtdconcat.c
> > +++ b/drivers/mtd/mtdconcat.c
> > @@ -561,25 +561,32 @@ static void concat_sync(struct mtd_info *mtd)
> >
> > static int concat_suspend(struct mtd_info *mtd)
> > {
> > + struct mtd_info *master = mtd_get_master(mtd);
> > struct mtd_concat *concat = CONCAT(mtd);
> > int i, rc = 0;
> >
> > for (i = 0; i < concat->num_subdev; i++) {
> > struct mtd_info *subdev = concat->subdev[i];
> > - if ((rc = mtd_suspend(subdev)) < 0)
> > +
> > + down_write(&master->master.suspend_lock);
> > + if ((rc = __mtd_suspend(subdev)) < 0)
> > return rc;
> > + up_write(&master->master.suspend_lock);
> > }
> > return rc;
> > }
> >
> > static void concat_resume(struct mtd_info *mtd)
> > {
> > + struct mtd_info *master = mtd_get_master(mtd);
> > struct mtd_concat *concat = CONCAT(mtd);
> > int i;
> >
> > for (i = 0; i < concat->num_subdev; i++) {
> > struct mtd_info *subdev = concat->subdev[i];
> > - mtd_resume(subdev);
> > + down_write(&master->master.suspend_lock);
> > + __mtd_resume(subdev);
> > + up_write(&master->master.suspend_lock);
> > }
> > }
> >
>
> Why do we need to implement the _suspend/_resume() hooks here? The
> underlying MTD devices should be suspended at some point (when the
> class ->suspend() method is called on those device), and there's
> nothing mtdconcat-specific to do here. Looks like implementing this
> suspend-all-subdevs loop results in calling mtd->_suspend()/_resume()
> twice, which is useless. The only issue I see is if the subdevices
> haven't been registered to the device model, but that happens, I
> believe we have bigger issues (those devices won't be suspended when
> mtdconcat is not used).
Uh, just had a look at mtd_concat_create() callers, and they indeed
don't register the subdevices, so I guess the suspend-all-subdevs loop
is needed. I really thought mtdconcat was something more generic
aggregating already registered devices...
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <boris.brezillon@collabora.com>
To: Sean Nyekjaer <sean@geanix.com>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Boris Brezillon <bbrezillon@kernel.org>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] mtd: mtdconcat: add suspend lock handling
Date: Mon, 11 Oct 2021 15:27:03 +0200 [thread overview]
Message-ID: <20211011152703.0086d990@collabora.com> (raw)
In-Reply-To: <20211011151501.48cc9289@collabora.com>
On Mon, 11 Oct 2021 15:15:01 +0200
Boris Brezillon <boris.brezillon@collabora.com> wrote:
> On Mon, 11 Oct 2021 13:52:53 +0200
> Sean Nyekjaer <sean@geanix.com> wrote:
>
> > Use new suspend lock handling for this special case for concatenated
> > MTD devices.
> >
> > Fixes: 013e6292aaf5 ("mtd: rawnand: Simplify the locking")
> > Signed-off-by: Sean Nyekjaer <sean@geanix.com>
> > ---
> > drivers/mtd/mtdconcat.c | 11 +++++++++--
> > 1 file changed, 9 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/mtd/mtdconcat.c b/drivers/mtd/mtdconcat.c
> > index f685a581df48..c497c851481f 100644
> > --- a/drivers/mtd/mtdconcat.c
> > +++ b/drivers/mtd/mtdconcat.c
> > @@ -561,25 +561,32 @@ static void concat_sync(struct mtd_info *mtd)
> >
> > static int concat_suspend(struct mtd_info *mtd)
> > {
> > + struct mtd_info *master = mtd_get_master(mtd);
> > struct mtd_concat *concat = CONCAT(mtd);
> > int i, rc = 0;
> >
> > for (i = 0; i < concat->num_subdev; i++) {
> > struct mtd_info *subdev = concat->subdev[i];
> > - if ((rc = mtd_suspend(subdev)) < 0)
> > +
> > + down_write(&master->master.suspend_lock);
> > + if ((rc = __mtd_suspend(subdev)) < 0)
> > return rc;
> > + up_write(&master->master.suspend_lock);
> > }
> > return rc;
> > }
> >
> > static void concat_resume(struct mtd_info *mtd)
> > {
> > + struct mtd_info *master = mtd_get_master(mtd);
> > struct mtd_concat *concat = CONCAT(mtd);
> > int i;
> >
> > for (i = 0; i < concat->num_subdev; i++) {
> > struct mtd_info *subdev = concat->subdev[i];
> > - mtd_resume(subdev);
> > + down_write(&master->master.suspend_lock);
> > + __mtd_resume(subdev);
> > + up_write(&master->master.suspend_lock);
> > }
> > }
> >
>
> Why do we need to implement the _suspend/_resume() hooks here? The
> underlying MTD devices should be suspended at some point (when the
> class ->suspend() method is called on those device), and there's
> nothing mtdconcat-specific to do here. Looks like implementing this
> suspend-all-subdevs loop results in calling mtd->_suspend()/_resume()
> twice, which is useless. The only issue I see is if the subdevices
> haven't been registered to the device model, but that happens, I
> believe we have bigger issues (those devices won't be suspended when
> mtdconcat is not used).
Uh, just had a look at mtd_concat_create() callers, and they indeed
don't register the subdevices, so I guess the suspend-all-subdevs loop
is needed. I really thought mtdconcat was something more generic
aggregating already registered devices...
next prev parent reply other threads:[~2021-10-11 13:27 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 11:52 [PATCH 0/3] mtd: core: protect access to mtd devices while in suspend Sean Nyekjaer
2021-10-11 11:52 ` Sean Nyekjaer
2021-10-11 11:52 ` [PATCH 1/3] mtd: core: protect access to MTD " Sean Nyekjaer
2021-10-11 11:52 ` Sean Nyekjaer
2021-10-11 13:37 ` Boris Brezillon
2021-10-11 13:37 ` Boris Brezillon
2021-10-14 6:50 ` [mtd] d3ff51cfa9: WARNING:at_kernel/locking/rwsem.c:#down_read kernel test robot
2021-10-14 6:50 ` kernel test robot
2021-10-14 6:50 ` kernel test robot
2021-10-15 6:55 ` [PATCH 1/3] mtd: core: protect access to MTD devices while in suspend Boris Brezillon
2021-10-15 6:55 ` Boris Brezillon
2021-10-11 11:52 ` [PATCH 2/3] mtd: rawnand: remove suspended check Sean Nyekjaer
2021-10-11 11:52 ` Sean Nyekjaer
2021-10-11 11:52 ` [PATCH 3/3] mtd: mtdconcat: add suspend lock handling Sean Nyekjaer
2021-10-11 11:52 ` Sean Nyekjaer
2021-10-11 13:15 ` Boris Brezillon
2021-10-11 13:15 ` Boris Brezillon
2021-10-11 13:27 ` Boris Brezillon [this message]
2021-10-11 13:27 ` Boris Brezillon
2021-10-11 13:35 ` Sean Nyekjaer
2021-10-11 13:35 ` Sean Nyekjaer
2021-10-11 13:49 ` Boris Brezillon
2021-10-11 13:49 ` Boris Brezillon
2021-10-11 13:58 ` Boris Brezillon
2021-10-11 13:58 ` Boris Brezillon
2021-10-11 14:05 ` [PATCH 0/3] mtd: core: protect access to mtd devices while in suspend Boris Brezillon
2021-10-11 14:05 ` Boris Brezillon
2021-10-15 6:22 ` Miquel Raynal
2021-10-15 6:22 ` Miquel Raynal
2021-10-19 18:08 ` Sean Nyekjaer
2021-10-19 18:08 ` Sean Nyekjaer
2021-10-20 6:52 ` Boris Brezillon
2021-10-20 6:52 ` Boris Brezillon
2021-10-20 7:00 ` Boris Brezillon
2021-10-20 7:00 ` Boris Brezillon
2021-10-20 7:12 ` Miquel Raynal
2021-10-20 7:12 ` Miquel Raynal
2021-10-20 7:23 ` Sean Nyekjaer
2021-10-20 7:23 ` Sean Nyekjaer
2021-10-20 7:47 ` Boris Brezillon
2021-10-20 7:47 ` Boris Brezillon
2021-10-20 7:12 ` Sean Nyekjaer
2021-10-20 7:12 ` Sean Nyekjaer
2021-10-20 7:23 ` Miquel Raynal
2021-10-20 7:23 ` Miquel Raynal
2021-10-20 7:30 ` Boris Brezillon
2021-10-20 7:30 ` Boris Brezillon
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=20211011152703.0086d990@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=bbrezillon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--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.