linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marco <marco.stornelli@coritel.it>
To: Jamie Lokier <jamie@shareable.org>
Cc: David Woodhouse <dwmw2@infradead.org>, linux-embedded@vger.kernel.org
Subject: Re: Power cut in management
Date: Sat, 18 Oct 2008 18:01:21 +0200	[thread overview]
Message-ID: <48FA0851.4010209@coritel.it> (raw)
In-Reply-To: <20081018133801.GA30897@shareable.org>

Jamie Lokier ha scritto:
> David Woodhouse wrote:
>> On Sat, 2008-10-18 at 13:56 +0100, Jamie Lokier wrote:
>>> Trouble is, that's not suitable for a dashboard unit where users plug
>>> in their own media card.
>>>
>>> Marco didn't say if the SD card is for users to plug in their own
>>> media, or if it's internal storage for the device.
>> True, but the situation is different for a removable card. Firstly, it's
>> unlikely to be mission-critical; the device will still operate without
>> it. Secondly, even the most naïve of users knows that these things are
>> disposable.
>>
>> It's different if you're building a black box around them, with one of
>> these things inside.
> 
> I agree, this is very good advice.
> 
> -- Jamie
> 
Thank you very much for your response. The sdcard, however, it's for the
user so I haven't control on it, I think probably it will be FAT. Jamie
you said to manage the situation with an interrupt, I agree. My first
plan was (more or less) to have an application in user space that it
checks the interrupt (UIO driver ?) and simulates a console command to
do a clean shutdown. Then in the kernel routine I do something to cut
the power definitely. For my environment (about the time) it's possible
even in relation with the "emergency power". The only problem is: what
happens if before I install the irq handler the user turn off the
system? I mean I can't "loose" the interrupt. In this case it'd be like
a spurious interrupt from system point view. Let me know if I'm wrong.
Thanks.

  reply	other threads:[~2008-10-18 16:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-18 11:20 Power cut in management marco.stornelli
2008-10-18 11:49 ` Jamie Lokier
2008-10-18 12:04   ` David Woodhouse
2008-10-18 12:56     ` Jamie Lokier
2008-10-18 13:31       ` David Woodhouse
2008-10-18 13:38         ` Jamie Lokier
2008-10-18 16:01           ` Marco [this message]
2008-10-18 21:33             ` Ben Nizette

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=48FA0851.4010209@coritel.it \
    --to=marco.stornelli@coritel.it \
    --cc=dwmw2@infradead.org \
    --cc=jamie@shareable.org \
    --cc=linux-embedded@vger.kernel.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).