From: clemens.gruber@pqgruber.com (Clemens Gruber)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Implementing a driver that listen to a GPIO
Date: Thu, 02 Oct 2014 19:01:01 +0200 [thread overview]
Message-ID: <542D84CD.70403@pqgruber.com> (raw)
Hi,
I am just trying to solve a similar problem as Luca described. I have a
TQMa28 board running Linux 3.17-rc7 though.
The capacitors keep the system up for about 1500 more milliseconds after
the power fails. A GPIO line is set to high as soon as the main power is
lost.
So I have not much time to quit an important user space process and to
clean up the ext4 root filesystem before the power fails.
At the moment I pass rootflags=data=journal,commit=1 in the kernel
commandline to lower the risk of data loss.
In the user space application I open important files using the O_SYNC flag.
Is there something else I should do to avoid data loss?
How would you implement the "emergency cleanup on power-failure" logic?
Dedicated driver (similar to the mentioned gpio-event driver?),
implement it with UIO, let a userspace application running as root
select /dev/uioX and cleaning up?
Or should I create a separate partition on my eMMC just for this user
space application data and use a readonly rootfs for the rest?
Thanks for your help!
Best regards,
Clemens
next reply other threads:[~2014-10-02 17:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 17:01 Clemens Gruber [this message]
2014-10-03 0:33 ` Implementing a driver that listen to a GPIO Jinqiang Zeng
2014-10-03 9:37 ` Luca Ellero
-- strict thread matches above, loose matches on Subject: below --
2014-10-02 8:03 Luca Ellero
2014-10-02 12:52 ` Greg KH
2014-10-02 14:39 ` Luca Ellero
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=542D84CD.70403@pqgruber.com \
--to=clemens.gruber@pqgruber.com \
--cc=kernelnewbies@lists.kernelnewbies.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 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.