[Buildroot] /etc//init.d init scripts in buildroot

[Buildroot] /etc//init.d init scripts in buildroot

[Oscar Gomez Fuente]

Hi everyone,

I'm trying to use init scripts from /etc/init.d to activate one gpio just
before to halt my HW platform (a raspberry Pi): S00gpioff

I've created a script like this:

#!/bin/sh
#
# S00gpioff
#

GPIO_CMD_OFF=13

case "$1" in
start)
        echo $GPIO_CMD_OFF > /sys/class/gpio/export
        ;;
stop)
        echo "Activated CMD OFF output"
        echo 1 > /sys/class/gpio$GPIO_CMD_OFF/value
        ;;
*)
exit 1
;;

esac

The problem is I need to activate the gpio just before halt:

# halt
# Stopping dropbear sshd: OK
Stopping network...[  419.714234] smsc95xx 1-1.1:1.0 eth0: hardware isn't
capable of remote wakeup
ifdown: interface wlan0 not configured
Saving random seed... done.
Stopping logging: OK
Activated CMD OFF output <--------------------------------------------
umount: tmpfs busy - remounted read-only
umount: devpts busy - remounted read-only
umount: devtmpfs busy - remounted read-only
[  420.807391] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
The system is g[  420.816829] watchdog watchdog0: Watchdog timer stopped
oing down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system halt
[  422.818879] watchdog watchdog0: Watchdog timer stopped
[  422.824050] reboot: System halted

Does anyone how to delay a bit the activation of the GPIO?


Best regards.

Oscar Gomez Fuente.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170714/13266866/attachment.html>

[Buildroot] /etc//init.d init scripts in buildroot

[Peter Korsgaard]

>>>>> "Oscar" == Oscar Gomez Fuente <oscargomezf@gmail.com> writes:

 > Hi everyone,
 > I'm trying to use init scripts from /etc/init.d to activate one gpio just
 > before to halt my HW platform (a raspberry Pi): S00gpioff

 > I've created a script like this:

 > #!/bin/sh
 > #
 > # S00gpioff
 > #

 > GPIO_CMD_OFF=13

 > case "$1" in
 > start)
 >         echo $GPIO_CMD_OFF > /sys/class/gpio/export
 >         ;;
 > stop)
 >         echo "Activated CMD OFF output"
 >         echo 1 > /sys/class/gpio$GPIO_CMD_OFF/value
 >         ;;
 > *)
 > exit 1
 > ;;

 > esac

 > The problem is I need to activate the gpio just before halt:

How late does this need to happen? You cannot do much later than this in
user space. E.G. the default inittab is:

# Stuff to do before rebooting
::shutdown:/etc/init.d/rcK
::shutdown:/sbin/swapoff -a
::shutdown:/bin/umount -a -r

rcK calls you init script (as the very last one because of S00), and
then only swapoff + umount gets executed before the kernel is asked to
power down.

If this is not good enough then you need to handle the gpio in a kernel
driver instead by registering a reboot notifier.

-- 
Bye, Peter Korsgaard

[Buildroot] /etc//init.d init scripts in buildroot

[Thomas Petazzoni]

Hello,

On Fri, 14 Jul 2017 14:38:18 +0200, Peter Korsgaard wrote:

> If this is not good enough then you need to handle the gpio in a kernel
> driver instead by registering a reboot notifier.

What about using the gpio-poweroff driver, which already exists in the
kernel ?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

[Buildroot] /etc//init.d init scripts in buildroot

[Peter Korsgaard]

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 > Hello,
 > On Fri, 14 Jul 2017 14:38:18 +0200, Peter Korsgaard wrote:

 >> If this is not good enough then you need to handle the gpio in a kernel
 >> driver instead by registering a reboot notifier.

 > What about using the gpio-poweroff driver, which already exists in the
 > kernel ?

Ahh yes, even better - I wasn't aware of that driver.

-- 
Bye, Peter Korsgaard

[Buildroot] /etc//init.d init scripts in buildroot

[Oscar Gomez Fuente]

Hi Peter,


Thanks in advance for your help and quick reply.

I've designed a Back Up System [BUS: DC-DC converter + Voltage monitor +
Boost + Battery] in order to avoid problems when there is a lack of power,
a problem very common in systems with SDs and eMMCs (As you know, I'm
working with a raspberry pi platform). The system detects a failure in the
input power and immediately the boost with the battery is activated. At the
same time, a signal is detected in the raspberry pi (an input) that after 5
minutes, if the failure continuos it'll activate an output called nKILL.

This output (nKILL) is going to be used to power off the power supply of my
device. So I would like to make ensure that I power off your system in a
good way to avoid that the file system could be damaged.

Before activating the signal nKILL that it's going to command the Back Up
System to switch off my system, I execute sync to make sure that all files
are saved.

Do you know if this way is good enough to make sure that the file system is
going to keep the integrity?


Best regards,

Oscar Gomez Fuente

On 14 July 2017 at 14:38, Peter Korsgaard <peter@korsgaard.com> wrote:

> >>>>> "Oscar" == Oscar Gomez Fuente <oscargomezf@gmail.com> writes:
>
>  > Hi everyone,
>  > I'm trying to use init scripts from /etc/init.d to activate one gpio
> just
>  > before to halt my HW platform (a raspberry Pi): S00gpioff
>
>  > I've created a script like this:
>
>  > #!/bin/sh
>  > #
>  > # S00gpioff
>  > #
>
>  > GPIO_CMD_OFF=13
>
>  > case "$1" in
>  > start)
>  >         echo $GPIO_CMD_OFF > /sys/class/gpio/export
>  >         ;;
>  > stop)
>  >         echo "Activated CMD OFF output"
>  >         echo 1 > /sys/class/gpio$GPIO_CMD_OFF/value
>  >         ;;
>  > *)
>  > exit 1
>  > ;;
>
>  > esac
>
>  > The problem is I need to activate the gpio just before halt:
>
> How late does this need to happen? You cannot do much later than this in
> user space. E.G. the default inittab is:
>
> # Stuff to do before rebooting
> ::shutdown:/etc/init.d/rcK
> ::shutdown:/sbin/swapoff -a
> ::shutdown:/bin/umount -a -r
>
> rcK calls you init script (as the very last one because of S00), and
> then only swapoff + umount gets executed before the kernel is asked to
> power down.
>
> If this is not good enough then you need to handle the gpio in a kernel
> driver instead by registering a reboot notifier.
>
> --
> Bye, Peter Korsgaard
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170714/9ed9bc06/attachment.html>

[Buildroot] /etc//init.d init scripts in buildroot

[Oscar Gomez Fuente]

Hi Thomas,

I've just sent my response to Peter. I'm sorry I didn't see your email.

So Does the kernel have a mechanism for this purpose? Interesting...

I've found this dts file (The gpio output I'm using is 13):

/dts-v1/;
/plugin/;

/ {
    compatible = "brcm,bcm2709";
    fragment at 0 {
        target-path = "/";
        __overlay__ {
            power_ctrl: power_ctrl {
                compatible = "gpio-poweroff";
                gpios = <&gpio 13 0>;
            };
        };
    };

};

I understand that when I execute:

# halt

At the end of the process, this gpio witl be activated, won't it? and Will
it be enough with this method for a safety power off?


Best regards,

Oscar Gomez Fuente.

On 14 July 2017 at 15:31, Oscar Gomez Fuente <oscargomezf@gmail.com> wrote:

> Hi Peter,
>
>
> Thanks in advance for your help and quick reply.
>
> I've designed a Back Up System [BUS: DC-DC converter + Voltage monitor +
> Boost + Battery] in order to avoid problems when there is a lack of power,
> a problem very common in systems with SDs and eMMCs (As you know, I'm
> working with a raspberry pi platform). The system detects a failure in the
> input power and immediately the boost with the battery is activated. At the
> same time, a signal is detected in the raspberry pi (an input) that after 5
> minutes, if the failure continuos it'll activate an output called nKILL.
>
> This output (nKILL) is going to be used to power off the power supply of
> my device. So I would like to make ensure that I power off your system in a
> good way to avoid that the file system could be damaged.
>
> Before activating the signal nKILL that it's going to command the Back Up
> System to switch off my system, I execute sync to make sure that all files
> are saved.
>
> Do you know if this way is good enough to make sure that the file system
> is going to keep the integrity?
>
>
> Best regards,
>
> Oscar Gomez Fuente
>
> On 14 July 2017 at 14:38, Peter Korsgaard <peter@korsgaard.com> wrote:
>
>> >>>>> "Oscar" == Oscar Gomez Fuente <oscargomezf@gmail.com> writes:
>>
>>  > Hi everyone,
>>  > I'm trying to use init scripts from /etc/init.d to activate one gpio
>> just
>>  > before to halt my HW platform (a raspberry Pi): S00gpioff
>>
>>  > I've created a script like this:
>>
>>  > #!/bin/sh
>>  > #
>>  > # S00gpioff
>>  > #
>>
>>  > GPIO_CMD_OFF=13
>>
>>  > case "$1" in
>>  > start)
>>  >         echo $GPIO_CMD_OFF > /sys/class/gpio/export
>>  >         ;;
>>  > stop)
>>  >         echo "Activated CMD OFF output"
>>  >         echo 1 > /sys/class/gpio$GPIO_CMD_OFF/value
>>  >         ;;
>>  > *)
>>  > exit 1
>>  > ;;
>>
>>  > esac
>>
>>  > The problem is I need to activate the gpio just before halt:
>>
>> How late does this need to happen? You cannot do much later than this in
>> user space. E.G. the default inittab is:
>>
>> # Stuff to do before rebooting
>> ::shutdown:/etc/init.d/rcK
>> ::shutdown:/sbin/swapoff -a
>> ::shutdown:/bin/umount -a -r
>>
>> rcK calls you init script (as the very last one because of S00), and
>> then only swapoff + umount gets executed before the kernel is asked to
>> power down.
>>
>> If this is not good enough then you need to handle the gpio in a kernel
>> driver instead by registering a reboot notifier.
>>
>> --
>> Bye, Peter Korsgaard
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170714/13e90a96/attachment.html>

[Buildroot] /etc//init.d init scripts in buildroot

[Oscar Gomez Fuente]

Hi everyone,

I need goes high pin 26 at the end of the halt command. I've tried with
this .dts:

/dts-v1/;
/plugin/;

/ {
    compatible = "brcm,bcm2709";
    fragment at 0 {
        target-path = "/";
        __overlay__ {
            power_ctrl: power_ctrl {
                compatible = "gpio-poweroff";
                gpios = <&gpio 26 1>;
            };
        };
    };

};

But it doesn't work and I get this error:

...
[    0.576179] mousedev: PS/2 mouse device common for all mice
-->[    0.576225] poweroff-gpio power_ctrl: gpio_poweroff_probe:
pm_power_off function already registered
-->[    0.576237] poweroff-gpio: probe of power_ctrl failed with error -16
[    0.576632] bcm2835-cpufreq: min=1200000 max=1200000
[    0.576799] sdhci: Secure Digital Host Controller Interface driver
...

I have activated in the kernel config file: CONFIG_POWER_RESET=y and
CONFIG_POWER_RESET_GPIO=y

Does anyone any suggestion?

Best regards,

Oscar Gomez Fuente.

On 14 July 2017 at 15:42, Oscar Gomez Fuente <oscargomezf@gmail.com> wrote:

> Hi Thomas,
>
> I've just sent my response to Peter. I'm sorry I didn't see your email.
>
> So Does the kernel have a mechanism for this purpose? Interesting...
>
> I've found this dts file (The gpio output I'm using is 13):
>
> /dts-v1/;
> /plugin/;
>
> / {
>     compatible = "brcm,bcm2709";
>     fragment at 0 {
>         target-path = "/";
>         __overlay__ {
>             power_ctrl: power_ctrl {
>                 compatible = "gpio-poweroff";
>                 gpios = <&gpio 13 0>;
>             };
>         };
>     };
>
> };
>
> I understand that when I execute:
>
> # halt
>
> At the end of the process, this gpio witl be activated, won't it? and Will
> it be enough with this method for a safety power off?
>
>
> Best regards,
>
> Oscar Gomez Fuente.
>
> On 14 July 2017 at 15:31, Oscar Gomez Fuente <oscargomezf@gmail.com>
> wrote:
>
>> Hi Peter,
>>
>>
>> Thanks in advance for your help and quick reply.
>>
>> I've designed a Back Up System [BUS: DC-DC converter + Voltage monitor +
>> Boost + Battery] in order to avoid problems when there is a lack of power,
>> a problem very common in systems with SDs and eMMCs (As you know, I'm
>> working with a raspberry pi platform). The system detects a failure in the
>> input power and immediately the boost with the battery is activated. At the
>> same time, a signal is detected in the raspberry pi (an input) that after 5
>> minutes, if the failure continuos it'll activate an output called nKILL.
>>
>> This output (nKILL) is going to be used to power off the power supply of
>> my device. So I would like to make ensure that I power off your system in a
>> good way to avoid that the file system could be damaged.
>>
>> Before activating the signal nKILL that it's going to command the Back Up
>> System to switch off my system, I execute sync to make sure that all files
>> are saved.
>>
>> Do you know if this way is good enough to make sure that the file system
>> is going to keep the integrity?
>>
>>
>> Best regards,
>>
>> Oscar Gomez Fuente
>>
>> On 14 July 2017 at 14:38, Peter Korsgaard <peter@korsgaard.com> wrote:
>>
>>> >>>>> "Oscar" == Oscar Gomez Fuente <oscargomezf@gmail.com> writes:
>>>
>>>  > Hi everyone,
>>>  > I'm trying to use init scripts from /etc/init.d to activate one gpio
>>> just
>>>  > before to halt my HW platform (a raspberry Pi): S00gpioff
>>>
>>>  > I've created a script like this:
>>>
>>>  > #!/bin/sh
>>>  > #
>>>  > # S00gpioff
>>>  > #
>>>
>>>  > GPIO_CMD_OFF=13
>>>
>>>  > case "$1" in
>>>  > start)
>>>  >         echo $GPIO_CMD_OFF > /sys/class/gpio/export
>>>  >         ;;
>>>  > stop)
>>>  >         echo "Activated CMD OFF output"
>>>  >         echo 1 > /sys/class/gpio$GPIO_CMD_OFF/value
>>>  >         ;;
>>>  > *)
>>>  > exit 1
>>>  > ;;
>>>
>>>  > esac
>>>
>>>  > The problem is I need to activate the gpio just before halt:
>>>
>>> How late does this need to happen? You cannot do much later than this in
>>> user space. E.G. the default inittab is:
>>>
>>> # Stuff to do before rebooting
>>> ::shutdown:/etc/init.d/rcK
>>> ::shutdown:/sbin/swapoff -a
>>> ::shutdown:/bin/umount -a -r
>>>
>>> rcK calls you init script (as the very last one because of S00), and
>>> then only swapoff + umount gets executed before the kernel is asked to
>>> power down.
>>>
>>> If this is not good enough then you need to handle the gpio in a kernel
>>> driver instead by registering a reboot notifier.
>>>
>>> --
>>> Bye, Peter Korsgaard
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170719/18befc40/attachment.html>

[Buildroot] /etc//init.d init scripts in buildroot

[Thomas Petazzoni]

Hello,

On Wed, 19 Jul 2017 17:00:19 +0200, Oscar Gomez Fuente wrote:

> I need goes high pin 26 at the end of the halt command. I've tried with
> this .dts:
> 
> /dts-v1/;
> /plugin/;
> 
> / {
>     compatible = "brcm,bcm2709";
>     fragment at 0 {
>         target-path = "/";
>         __overlay__ {
>             power_ctrl: power_ctrl {
>                 compatible = "gpio-poweroff";
>                 gpios = <&gpio 26 1>;
>             };
>         };
>     };
> 
> };
> 
> But it doesn't work and I get this error:
> 
> ...
> [    0.576179] mousedev: PS/2 mouse device common for all mice
> -->[    0.576225] poweroff-gpio power_ctrl: gpio_poweroff_probe:  
> pm_power_off function already registered
> -->[    0.576237] poweroff-gpio: probe of power_ctrl failed with error -16  
> [    0.576632] bcm2835-cpufreq: min=1200000 max=1200000
> [    0.576799] sdhci: Secure Digital Host Controller Interface driver
> ...
> 
> I have activated in the kernel config file: CONFIG_POWER_RESET=y and
> CONFIG_POWER_RESET_GPIO=y
> 
> Does anyone any suggestion?

This is no longer a Buildroot question, so not very appropriate on this
mailing list.

Some other driver or architecture code is registering a pm_power_off
hook, so you'd have to find which one.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com