linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: shannon.zhao@linaro.org (Shannon Zhao)
To: linux-arm-kernel@lists.infradead.org
Subject: [Discussion] how to implement external power down for ARM
Date: Thu, 30 Apr 2015 09:03:22 +0800	[thread overview]
Message-ID: <55417F5A.4040300@linaro.org> (raw)

Hi?

I am looking at adding support for external power down and reboot to
ARM VMs.  With ACPI this is fairly straight forward and requires only
adding a GPIO controller to the virt machine model and extending ACPI
appropriately (see code here [1]). In addition Linaro LEG also have
done a test that uses GPIO as power button to shutdown OS on fast model
(see detail here [2]).

However, we would like for this to work in systems that do not use
ACPI as well. Adding a GPIO controller will still work, but we would
need a generic way to tell Linux how to handle the GPIO events without
adding any board-specific code to the VIRT platform. And what guest
kernel driver do we need? Do we need another user-level daemon like acpid?

Note that external shutdown can also be accomplished using the qemu
guest agent [3], but maybe this is not a sufficiently stable approach.

Any input on the approach to take here is very welcome.

Thanks,
Shannon

[1] https://git.linaro.org/people/shannon.zhao/qemu.git/shortlog/refs/heads/PowerButton
[2] https://wiki.linaro.org/LEG/Engineering/Kernel/ACPI/GPIOPowerButton
[3] http://wiki.qemu.org/Features/QAPI/GuestAgent

             reply	other threads:[~2015-04-30  1:03 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-30  1:03 Shannon Zhao [this message]
2015-04-30  8:03 ` [Discussion] how to implement external power down for ARM Arnd Bergmann
2015-04-30  9:08   ` Peter Maydell
2015-04-30  9:19     ` Arnd Bergmann
2015-04-30  9:29     ` Mark Rutland
2015-04-30  9:56       ` Arnd Bergmann
2015-05-04  2:09         ` Shannon Zhao
2015-05-04 15:49           ` Arnd Bergmann
2015-05-05  2:57             ` Joel Stanley
2015-05-05  9:53               ` Arnd Bergmann
2015-05-05 10:51                 ` Christoffer Dall
2015-05-05 10:55                   ` Arnd Bergmann
2015-05-05 11:13                     ` Shannon Zhao
2015-05-06  6:56                       ` Shannon Zhao
2015-05-06  7:29                         ` Arnd Bergmann
2015-05-06  8:19                           ` Shannon Zhao
2015-05-06  8:37                             ` Arnd Bergmann
2015-05-06  8:41                               ` Shannon Zhao
2015-05-06 10:14                             ` Christoffer Dall
2015-05-07  2:39                           ` Shannon Zhao
2015-05-07  8:55                             ` Arnd Bergmann
2015-05-07  9:18                               ` Shannon Zhao
2015-05-07  9:43                                 ` Arnd Bergmann
2015-05-07 12:10                                   ` Shannon Zhao
2015-05-07 12:12                                     ` Peter Maydell
2015-05-07 12:18                                       ` Shannon Zhao
2015-05-07 12:34                                         ` Peter Maydell
2015-05-07 12:48                                           ` Arnd Bergmann
2015-05-07 13:02                                           ` Shannon Zhao
2015-04-30 13:38       ` Hanjun Guo
2015-05-04  1:55         ` Shannon Zhao

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=55417F5A.4040300@linaro.org \
    --to=shannon.zhao@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).