linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Raffaele Recalcati <lamiaposta71@gmail.com>
Cc: Oliver Neukum <oliver@neukum.org>,
	linux-pm@lists.linux-foundation.org,
	davinci-linux-open-source@linux.davincidsp.com,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-pm] pm loss development
Date: Wed, 18 May 2011 01:06:56 +0200	[thread overview]
Message-ID: <201105180106.57147.rjw@sisk.pl> (raw)
In-Reply-To: <BANLkTikEJoV1JHMDZODvv40-8-jmvYMbgg@mail.gmail.com>

On Saturday, May 14, 2011, Raffaele Recalcati wrote:
> On Sat, May 14, 2011 at 8:53 PM, Oliver Neukum <oliver@neukum.org> wrote:
> > Am Donnerstag, 12. Mai 2011, 21:27:44 schrieb Rafael J. Wysocki:
> >> On Thursday, May 12, 2011, Raffaele Recalcati wrote:
> >> > What happen normally in runtime pm implementation is that every devices
> >> > are switched off and are enabled only when needed.
> >> > In our case instead we have a completely functional embedded system and,
> >> > when an asyncrhonous event appear, we have only some tens milliseconds
> >> > before the actual power failure takes place.
> >> > This patchset add a support in order to switch off not vital part of the system,
> >> > in order to allow the board to survive longer.
> >> > This allow the possibility to save important data.
> >>
> >> OK, so first, who decides what parts of the system are vital and what aren't?
> >
> > If you know that power is failing in a few miliseconds, only stuff that can lead to data
> > corruption is vital. In that timeframe you can't even flush buffers.
> 
> Remember that if you switch off some peripherals this timeframe
> becomes longer, so maybe you have enough time to sync some storage
> devices.

However, switching off peripherals _also_ takes time.  So, it may be more
useful to take care of the stuff leading to data corruption along with the
switching off peripherals.

Thanks,
Rafael

  reply	other threads:[~2011-05-17 23:06 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
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 [this message]
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=201105180106.57147.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=lamiaposta71@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=oliver@neukum.org \
    /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).