[Buildroot] Lightweight method for handling external power-down request

* [Buildroot] Lightweight method for handling external power-down request
@ 2016-04-19 18:15 Patrick Doyle
  2016-04-19 19:04 ` Thomas Petazzoni
  0 siblings, 1 reply; 3+ messages in thread
From: Patrick Doyle @ 2016-04-19 18:15 UTC (permalink / raw)
  To: buildroot

Hello all,
I found this discussion:

http://lists.infradead.org/pipermail/linux-arm-kernel/2015-April/339919.html

on the Linux Arm Kernel mailing list archive.  It is from April of
2015.  Sannon Zhao started a discussion regarding how to implement
external power down for ARM.  The consensus seemed to be to use ACPI.
I am wondering if there is a lighter weight (smaller code and
mindshare footprint) method for handling this.

I would like to initiate an orderly shutdown of my buildroot based
system when a GPIO signal is toggled high.  I think could add
something like the following to my device tree:

    gpio-keys {
        compatible = "gpio-keys";
        pinctrl-names = "default";
        pinctrl-0 = <&pinctrl_gpio_poweroff>;
        power {
                label = "Power-Key";
            gpios = <&pioA 103 GPIO_ACTIVE_HIGH>;
            linux,code = <KEY_POWER>;
            debounce-interval = <10>;
        };
    };

and I believe that would result in a KEY_POWER event(?)/input key(?)
getting delivered to user-land.  But I am not sure how to handle that
in user-land.  So it seems that I could install acpid to handle that
somehow, but I feel this is getting more complicated than it should
be.

Alternatively, I could code up a shell script that polls my GPIO pin
and shuts down the processor when that signal goes high, but I hate
the idea of polling; I'm not thrilled about the lack of debounce
support; and I would much rather respond to the event immediately,
than have to wait the 500 to 1000ms I might have to wait for my
polling process to notice the signal.

So, how do ARM folks in Buildroot-land handle this?

--wpd

^ permalink raw reply	[flat|nested] 3+ messages in thread