From: Krzysztof Kozlowski <krzk@kernel.org>
To: Eric Blake <eblake@redhat.com>
Cc: "Igor Mitsyanko" <i.mitsyanko@gmail.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH 3/3] hw/arm/exynos: Add support for system poweroff
Date: Mon, 8 May 2017 20:22:24 +0200 [thread overview]
Message-ID: <20170508182224.dfbvmfb4fxfbe3ys@kozik-lap> (raw)
In-Reply-To: <f8b021fa-e3f8-50d7-8013-d67e66e25ce6@redhat.com>
On Mon, May 08, 2017 at 09:21:40AM -0500, Eric Blake wrote:
> On 05/07/2017 06:35 AM, Krzysztof Kozlowski wrote:
> > On all Exynos-based boards, the system powers down itself by driving
> > PS_HOLD signal low. Handle writing to respective PMU register to fix
> > power off failure:
> >
> > reboot: Power down
> > Unable to poweroff system
> > shutdown: 31 output lines suppressed due to ratelimiting
> > Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000
> >
> > CPU: 0 PID: 1 Comm: shutdown Not tainted 4.11.0-rc8 #846
> > Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
> > [<c031050c>] (unwind_backtrace) from [<c030ba6c>] (show_stack+0x10/0x14)
> > [<c030ba6c>] (show_stack) from [<c05b2800>] (dump_stack+0x88/0x9c)
> > [<c05b2800>] (dump_stack) from [<c03d3140>] (panic+0xdc/0x268)
> > [<c03d3140>] (panic) from [<c0343614>] (do_exit+0xa90/0xab4)
> > [<c0343614>] (do_exit) from [<c035f2dc>] (SyS_reboot+0x164/0x1d0)
> > [<c035f2dc>] (SyS_reboot) from [<c0307c80>] (ret_fast_syscall+0x0/0x3c)
> >
> > Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> > ---
> > hw/misc/exynos4210_pmu.c | 14 ++++++++++++++
> > 1 file changed, 14 insertions(+)
>
> > @@ -397,6 +398,12 @@ typedef struct Exynos4210PmuState {
> > uint32_t reg[PMU_NUM_OF_REGISTERS];
> > } Exynos4210PmuState;
> >
> > +static void exynos4210_pmu_poweroff(void)
> > +{
> > + PRINT_DEBUG("QEMU PMU: PS_HOLD bit down, powering off\n");
> > + qemu_system_shutdown_request();
>
> Depending on whether your patch lands before or after mine, we'll have
> to update this. It sounds like it is a guest-triggered reset, so my
> patch would have this use SHUTDOWN_CAUSE_GUEST_SHUTDOWN.
>
> https://lists.gnu.org/archive/html/qemu-devel/2017-05/msg01380.html
Sure, I can rebase and fix the difference once your patchset gets in.
Best regards,
Krzysztof
next prev parent reply other threads:[~2017-05-08 18:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 11:35 [Qemu-devel] [PATCH 0/3] hw/arm/exynos: Fix poweroff Krzysztof Kozlowski
2017-05-07 11:35 ` [Qemu-devel] [PATCH 1/3] hw/arm/exynos: Use type define instead of hard-coded a9mpcore_priv string Krzysztof Kozlowski
2017-05-07 18:16 ` [Qemu-devel] [Qemu-arm] " Philippe Mathieu-Daudé
2017-05-07 11:35 ` [Qemu-devel] [PATCH 2/3] hw/intc/exynos: Constify array of combiner interrupts Krzysztof Kozlowski
2017-05-07 18:15 ` [Qemu-devel] [Qemu-arm] " Philippe Mathieu-Daudé
2017-05-07 11:35 ` [Qemu-devel] [PATCH 3/3] hw/arm/exynos: Add support for system poweroff Krzysztof Kozlowski
2017-05-08 14:21 ` Eric Blake
2017-05-08 18:22 ` Krzysztof Kozlowski [this message]
2017-05-30 15:45 ` Peter Maydell
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=20170508182224.dfbvmfb4fxfbe3ys@kozik-lap \
--to=krzk@kernel.org \
--cc=eblake@redhat.com \
--cc=f4bug@amsat.org \
--cc=i.mitsyanko@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).