From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: hs@denx.de
Cc: Steve deRosier <derosier@gmail.com>,
linux-embedded@vger.kernel.org, Wolfgang Denk <wd@denx.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: GPIO triggers kernel reboot
Date: Mon, 27 Jan 2014 09:08:49 +0100 [thread overview]
Message-ID: <8761p5hmni.fsf@lebrac.rtp-net.org> (raw)
In-Reply-To: <52E5FB1A.2020205@denx.de> (Heiko Schocher's message of "Mon, 27 Jan 2014 07:22:18 +0100")
Heiko Schocher <hs@denx.de> writes:
> Hello Steve,
>
> Thanks for your answer!
>
> Am 25.01.2014 20:39, schrieb Steve deRosier:
>> Hi Heiko,
>>
>> It's certainly possible, and it's also easily done from user-space.
>> Something like this is more policy than function. It's also a potential
>> security issue. As such I'd expect it highly unlikely that the kernel
>> maintainers would allow it to go upstream. Give it a try though.
>
> Ok, thats what I also think ...
>
>> I'd approach this from user-space. Add in the gpio-keys driver and use the
>> input-event-daemon to trigger a reboot. Super easy.
>
> Yes, that was also my suggestion, but is there a way to do this without
> user space usage in a generic way?
I think that you can register an input handler for that. iirc, there was
a driver doing something similar for apm.
Arnaud
next prev parent reply other threads:[~2014-01-27 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 16:02 GPIO triggers kernel reboot Heiko Schocher
2014-01-25 19:11 ` Mehaffey, John
2014-01-25 20:24 ` Mehaffey, John
2014-01-27 6:17 ` Heiko Schocher
2014-01-26 2:54 ` Florian Fainelli
[not found] ` <CALLGbRKK_ZcOB6nAiV67njrphXMQXN7Y2s81n5k3PWoSVrsrUw@mail.gmail.com>
2014-01-27 6:22 ` Heiko Schocher
2014-01-27 8:08 ` Arnaud Patard [this message]
2014-01-27 8:25 ` Geert Uytterhoeven
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=8761p5hmni.fsf@lebrac.rtp-net.org \
--to=arnaud.patard@rtp-net.org \
--cc=derosier@gmail.com \
--cc=hs@denx.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-embedded@vger.kernel.org \
--cc=wd@denx.de \
/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).