All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
	Boris Brezillon <boris.brezillon@collabora.com>,
	linux-mtd@lists.infradead.org, kernel@pengutronix.de,
	Miquel Raynal <miquel.raynal@bootlin.com>
Subject: Re: Prevent Nand page writes on Power failure
Date: Thu, 21 Feb 2019 10:28:30 +0100	[thread overview]
Message-ID: <1827693.m7yXcEqR8t@blindfold> (raw)
In-Reply-To: <20190221083914.dq4kzyx4t4fgoo46@pengutronix.de>

Am Donnerstag, 21. Februar 2019, 09:39:14 CET schrieb Sascha Hauer:
> > Regarding important data, users that care need to use fsync() anyway, so
> > there is no need to trigger whatever writeback upon power failure.
> > Or what else important data do you have in mind?
> 
> What you want to do on a power failure probably depends on the time
> you have left. When you have a second left then you get other ideas than
> when you have just a few milliseconds. If you have enough time then you
> maybe even want to do an ordered shutdown which would include writing to
> the nand.

Well, these are two distinct use cases. Both are sane but have different goals.
If you have a signal that tells "I'm out of power supply and have plenty of time"
you can notify/wake userspace and it is no big deal if the userspace action takes too
long and the board browns out.

But for the NAND stuff you need something that tells you "I'm out of of power
and you need to take action immediately".
Here the action needs to happen in any case because the hardware requires so.

Thanks,
//richard




______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2019-02-21  9:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 13:58 Prevent Nand page writes on Power failure Sascha Hauer
2019-02-21  0:05 ` Richard Weinberger
2019-02-21  8:39   ` Sascha Hauer
2019-02-21  9:28     ` Richard Weinberger [this message]
2019-02-21  8:10 ` Boris Brezillon
2019-02-21 10:17   ` Sascha Hauer
2019-02-21 10:36     ` Boris Brezillon
2019-02-21 11:21       ` Sascha Hauer
2019-02-21 11:37         ` Boris Brezillon
2019-02-21 12:17           ` Richard Weinberger
2019-02-21 13:27           ` Sascha Hauer
2019-02-25  8:56 ` Sascha Hauer
2019-02-25 11:28   ` Richard Weinberger
2019-02-26  9:10     ` Sascha Hauer

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=1827693.m7yXcEqR8t@blindfold \
    --to=richard@nod.at \
    --cc=boris.brezillon@collabora.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard.weinberger@gmail.com \
    --cc=s.hauer@pengutronix.de \
    /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.