From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Davide Ciminaghi <ciminaghi@gnudd.com>,
davinci-linux-open-source@linux.davincidsp.com,
"Greg Kroah-Hartman" <gregkh@suse.de>,
linux-kernel@vger.kernel.org,
Raffaele Recalcati <raffaele.recalcati@bticino.it>,
linux-pm@lists.linux-foundation.org,
Raffaele Recalcati <lamiaposta71@gmail.com>
Subject: Re: [linux-pm] [PATCH 2/4] PM / Loss: power loss management
Date: Thu, 19 May 2011 22:52:46 +0200 [thread overview]
Message-ID: <201105192252.46836.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1105191021220.1900-100000@iolanthe.rowland.org>
On Thursday, May 19, 2011, Alan Stern wrote:
> On Thu, 19 May 2011, Davide Ciminaghi wrote:
>
> > I'm not completely sure about this. What we wanted to do was to avoid powering
> > down the mmc while it is physically writing data into its internal memory.
> > If we force a sync when the power loss warning event warning happens,
> > it is very difficult to be able to guarantee that all buffered data will be
> > written before power actually dies. So we preferred to follow another strategy:
> > let the mmc finish any running write operation, and then stop its request
> > queue. If power really goes down, then we hope that the file system journal
> > will fix things on next boot (yes, some data could get lost, but the fs should
> > still be mountable). On the other hand, if power resumes, nothing bad should
> > happen for user space processes.
>
> You could consider a totally different approach.
>
> Each platform will have a different set of high-power devices it wants
> to turn off when a power-loss warning occurs. So instead of changing
> the core PM interface, you could add a new "power_loss" notifier list.
> Only the most critical drivers would need to listen for notifications,
> and this could be different drivers on different platforms.
Moreover, it would allow not only drivers, but also filesystems (for
one example) to get notifications.
Thanks,
Rafael
next prev parent reply other threads:[~2011-05-19 20:52 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 17:11 pm loss development Raffaele Recalcati
2011-05-12 17:11 ` [PATCH 1/4] export bus_kset Raffaele Recalcati
2011-05-12 19:28 ` Rafael J. Wysocki
2011-05-13 17:11 ` Davide Ciminaghi
2011-05-15 14:13 ` [linux-pm] " Davide Ciminaghi
2011-05-17 23:04 ` Rafael J. Wysocki
2011-05-12 17:11 ` [PATCH 2/4] PM / Loss: power loss management Raffaele Recalcati
2011-05-12 19:57 ` Rafael J. Wysocki
2011-05-13 13:02 ` Davide Ciminaghi
2011-05-17 23:32 ` Rafael J. Wysocki
2011-05-19 9:26 ` Davide Ciminaghi
2011-05-19 14:25 ` [linux-pm] " Alan Stern
2011-05-19 20:52 ` Rafael J. Wysocki [this message]
2011-05-12 17:11 ` [PATCH 3/4] mmc: bus and block device drivers: support for pm_loss Raffaele Recalcati
2011-05-12 17:11 ` [PATCH 4/4] DaVinci: vpfe: " Raffaele Recalcati
2011-05-12 19:27 ` pm loss development Rafael J. Wysocki
2011-05-13 6:39 ` Raffaele Recalcati
2011-05-13 16:54 ` Rafael J. Wysocki
2011-05-14 16:35 ` [linux-pm] " mark gross
2011-05-17 23:07 ` Rafael J. Wysocki
2011-05-18 3:12 ` mark gross
2011-05-18 19:43 ` Rafael J. Wysocki
2011-05-18 22:17 ` Mark Brown
2011-05-19 12:45 ` mark gross
2011-06-02 22:21 ` Pavel Machek
2011-06-14 14:06 ` mark gross
2011-06-14 14:36 ` Alan Cox
2011-05-14 20:21 ` Raffaele Recalcati
2011-05-17 23:10 ` Rafael J. Wysocki
2011-05-14 18:53 ` [linux-pm] " Oliver Neukum
2011-05-14 20:34 ` Raffaele Recalcati
2011-05-17 23:06 ` Rafael J. Wysocki
2011-05-14 16:24 ` mark gross
2011-05-14 20:30 ` Raffaele Recalcati
2011-05-14 23:33 ` mark gross
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=201105192252.46836.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=ciminaghi@gnudd.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=gregkh@suse.de \
--cc=lamiaposta71@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=raffaele.recalcati@bticino.it \
--cc=stern@rowland.harvard.edu \
/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).