From: Sebastian Reichel <sre@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: openwrt-devel@openwrt.org,
Florian Fainelli <f.fainelli@gmail.com>,
Paulius Zaleckas <paulius.zaleckas@gmail.com>,
linux-pm@vger.kernel.org,
Hans Ulli Kroll
<ulli.kroll@googlemail.com>inux-pm@vger.kernel.org,
Janos Laube <janos.dev@gmail.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2 RESEND] power: reset: Add a driver for the Gemini poweroff
Date: Wed, 15 Mar 2017 22:11:49 +0100 [thread overview]
Message-ID: <20170315211149.of3xvrnlq7ne7r5w@earth> (raw)
In-Reply-To: <20170312223621.3010-1-linus.walleij@linaro.org>
[-- Attachment #1.1: Type: text/plain, Size: 2132 bytes --]
Hi Linus,
On Sun, Mar 12, 2017 at 11:36:21PM +0100, Linus Walleij wrote:
> The Gemini (SL3516) SoC has a special power controller block
> that only deal with shutting down the system.
>
> If you do not register a driver and activate the block, the
> power button on the systems utilizing this SoC will do an
> uncontrolled power cut, which is why it is important to have
> a special poweroff driver.
>
> The most basic functionality is to just shut down the system
> by writing a special bit in the control register after the
> system has reached pm_poweroff.
>
> It also handles the poweroff from a button or other sources:
>
> When the poweroff button is pressed, or a signal is sent to
> poweroff from an infrared remote control, or when the RTC
> fires a special alarm (!) the system emits an interrupt.
> At this point, Linux must acknowledge the interrupt and
> proceed to do an orderly shutdown of the system.
>
> After adding this driver, pressing the poweroff button gives
> this dmesg:
>
> root@gemini:/
> root@gemini:/ gemini-poweroff 4b000000.power-controller:
> poweroff button pressed
>
> calling shutdown scripts..
> setting /dev/rtc0 from system time
> unmounting file systems...
> umount: tmpfs busy - remounted read-only
> umount: can't unmount /: Invalid argument
> The system is going down NOW!
> Sent SIGTERM to all processes
> Sent SIGKILL to all processes
> Requesting system poweroff
> uhci_hcd 0000:00:09.1: HCRESET not completed yet!
> uhci_hcd 0000:00:09.0: HCRESET not completed yet!
> reboot: Power down
> gemini-poweroff 4b000000.power-controller: Gemini power off
>
> Cc: Janos Laube <janos.dev@gmail.com>
> Cc: Paulius Zaleckas <paulius.zaleckas@gmail.com>
> Cc: Hans Ulli Kroll <ulli.kroll@googlemail.com>
> Cc: Florian Fainelli <f.fainelli@gmail.com>
> Cc: linux-pm@vger.kernel.org
> Cc: Sebastian Reichel <sre@kernel.org>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> Sebastian: please just merge this when your are pleased
> with it. I will funnel the ARM parts through the ARM SoC tree.
DONE.
-- Sebastian
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2017-03-15 21:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 22:36 [PATCH 2/2 RESEND] power: reset: Add a driver for the Gemini poweroff Linus Walleij
2017-03-15 21:11 ` Sebastian Reichel [this message]
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=20170315211149.of3xvrnlq7ne7r5w@earth \
--to=sre@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=openwrt-devel@openwrt.org \
--cc=paulius.zaleckas@gmail.com \
--cc=ulli.kroll@googlemail.com \
/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