From: "Mark Chambers" <markc@mail.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: Re: Handling power failure - MPC5200
Date: Fri, 5 Nov 2004 10:09:18 -0500 [thread overview]
Message-ID: <005a01c4c349$7949b8c0$0301a8c0@chuck2> (raw)
In-Reply-To: 065ACD8E84315E4394C835E398C8D5EB9E97EB@COSSMGMBX02.email.corp.tld
> > > Capacitors on the supply provide me with some
> milliseconds to repond
> to
> > > power failure, which I would
> > > like to use to do as much cleanup as possible before power is
> > > totally gone. In particular, I am concerned
> >
>What I've seen is marketing bullet points saying the cards can survive a
power loss event with no loss of data, but when I read the >detailed CF
specification, the disclaimer was that power had to be held up for X mSec (I
forgot what X was, 2mSec or 10mSec most >likely) after the last write
operation. The marketing bullet point was exactly that: marketing. The
real requirement levied on the user
>(you) was that you had to have X mSec power hold up after the last write
operation (i.e. a X mSec power fail warning with no write >operations after
the PF warning). The hold-up requirement gave the CF internals enough time
to complete a flash write cycle.
One simple use for the power fail interrupt would be to just turn off
interrupts and loop until power fail.
This would insure that a write or erase operation completed fully.
P.S. Don't forget to cover the situation where power comes back rather than
going all the way down!
Mark Chambers
wvcomputronics.com
next prev parent reply other threads:[~2004-11-05 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 14:48 Handling power failure - MPC5200 VanBaren, Gerald (AGRE)
2004-11-05 15:09 ` Mark Chambers [this message]
2004-11-05 20:47 ` Wolfgang Denk
2004-11-05 21:26 ` Mark Chambers
2004-11-06 0:52 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2004-11-04 12:32 Jón Benediktsson
2004-11-04 16:22 ` Wolfgang Denk
2004-11-05 14:13 ` Jón Benediktsson
2004-11-05 14:32 ` Wolfgang Denk
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='005a01c4c349$7949b8c0$0301a8c0@chuck2' \
--to=markc@mail.com \
--cc=linuxppc-embedded@ozlabs.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).