From: Haojian Zhuang <haojian.zhuang@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: dsaxena@laptop.org, alan@linux.intel.com, gregkh@suse.de,
Daniel Mack <daniel@caiaq.de>,
linux-arm-kernel@lists.infradead.org,
Eric <eric.y.miao@gmail.com>,
Haojian Zhuang <haojian.zhuang@marvell.com>,
rpurdie@rpsys.net, lenz@cs.wisc.edu,
kernel list <linux-kernel@vger.kernel.org>,
Dirk@opfer-online.de, arminlitzel@web.de,
Cyril Hrubis <metan@ucw.cz>,
thommycheck@gmail.com, dbaryshkov@gmail.com, omegamoon@gmail.com,
utx@penguin.cz, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: Possible suspend/resume regression in .32-rc?
Date: Mon, 2 Nov 2009 07:18:02 -0400 [thread overview]
Message-ID: <771cded00911020318u3939a06dq75cd3504d6c0eb50@mail.gmail.com> (raw)
In-Reply-To: <20091102105141.GB11426@elf.ucw.cz>
On Mon, Nov 2, 2009 at 6:51 AM, Pavel Machek <pavel@ucw.cz> wrote:
> On Mon 2009-11-02 06:48:28, Haojian Zhuang wrote:
>> On Mon, Nov 2, 2009 at 5:38 AM, Pavel Machek <pavel@ucw.cz> wrote:
>> > On Mon 2009-11-02 05:22:30, Haojian Zhuang wrote:
>> >> On Sun, Nov 1, 2009 at 6:03 PM, Pavel Machek <pavel@ucw.cz> wrote:
>> >>
>> >> Em, it's not caused by the IRQ patch.
>> >>
>> >> The kernel is blocked in resume path. When console is resumed, IRQ is
>> >> already disabled and system is blocked. Actually, IRQ shouldn't be
>> >> disabled at here. Up to now, I only find which patch will cause this
>> >> issue. But I can't find the best solution on it. The patch with issue
>> >> is pasted in below.
>> >>
>> >> So this issue is only occused when console suspend is enabled. If you
>> >> enable no_console_suspend in command, you won't meet this issue. It
>> >> seems that it's caused by removing termios setting in
>> >> uart_resume_port() in the below patch. If I add these code back, the
>> >> issue doesn't occur any more.
>> >
>> > Given that it hangs very early, in arch_suspend_enable_irqs() (see my
>> > other mail), I don't trust your analysis.
>> >
>> > I'm not using serial console on spitz, and I have never had successful
>> > resume with the patch applied.
>>
>> It seems that we're talking on different issue with similar symptom.
>> Please check my test method. While I'm testing suspend with devices
>> level, kernel is blocked in console resume. In this level, it won't
>> call arch_suspend_enable_irqs(). This function call is only invoked in
>> processor level or below.
>
> For me, everything but real suspend works. I do _not_ have serial
> console for spitz.
>
>> Up to now, I can't reproduce the issue you're talking on my platform
>> yet. I'll check this issue continuously. I also want to know your
>> hardware information.
>
> Spitz, aka Sharp Zaurus c3000.
>
I see. You can chech my patch in below. I need to save IPRs in suspend
resume routine.
Thanks
Haojian
>From 1764e836424d42a0654b8b73c402a2dddb118dc4 Mon Sep 17 00:00:00 2001
From: Haojian Zhuang <haojian.zhuang@marvell.com>
Date: Mon, 2 Nov 2009 14:02:21 -0500
Subject: [PATCH] pxa: fix system resume issue on pxa27x and pxa3xx
Since interrupt handler is changed to use interrupt priority, we also need to
save and restore these interrupt controller registers in suspend/resume
routine.
Signed-off-by: Haojian Zhuang <haojian.zhuang@marvell.com>
---
arch/arm/mach-pxa/irq.c | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-pxa/irq.c b/arch/arm/mach-pxa/irq.c
index d694ce2..cdc272b 100644
--- a/arch/arm/mach-pxa/irq.c
+++ b/arch/arm/mach-pxa/irq.c
@@ -150,6 +150,7 @@ void __init pxa_init_irq(int irq_nr, set_wake_t fn)
#ifdef CONFIG_PM
static unsigned long saved_icmr[2];
+static unsigned long saved_ipr[128];
static int pxa_irq_suspend(struct sys_device *dev, pm_message_t state)
{
@@ -159,6 +160,10 @@ static int pxa_irq_suspend(struct sys_device
*dev, pm_message_t state)
saved_icmr[i] = _ICMR(irq);
_ICMR(irq) = 0;
}
+ if (pxa_internal_irq_nr > 128)
+ BUG();
+ for (i = 0; i < pxa_internal_irq_nr; i++)
+ saved_ipr[i] = IPR(i);
return 0;
}
@@ -171,6 +176,8 @@ static int pxa_irq_resume(struct sys_device *dev)
_ICMR(irq) = saved_icmr[i];
_ICLR(irq) = 0;
}
+ for (i = 0; i < pxa_internal_irq_nr; i++)
+ IPR(i) = saved_ipr[i];
ICCR = 1;
return 0;
--
1.5.6.5
next prev parent reply other threads:[~2009-11-02 11:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091031013427.GL14091@buzzloop.caiaq.de>
[not found] ` <20091101205449.GT14091@buzzloop.caiaq.de>
2009-11-01 21:33 ` Pavel Machek
2009-11-01 22:03 ` Pavel Machek
2009-11-02 9:22 ` Haojian Zhuang
2009-11-02 9:29 ` Daniel Mack
2009-11-02 9:38 ` Pavel Machek
2009-11-02 9:54 ` Eric Miao
2009-11-02 10:48 ` Haojian Zhuang
2009-11-02 10:51 ` Pavel Machek
2009-11-02 11:18 ` Haojian Zhuang [this message]
2009-11-02 11:27 ` Daniel Mack
2009-11-02 12:22 ` Pavel Machek
2009-11-02 9:57 ` Stanislav Brabec
2009-11-03 3:31 ` Haojian Zhuang
2009-11-03 9:50 ` Stanislav Brabec
2009-11-05 5:06 ` Haojian Zhuang
2010-01-13 11:46 ` Daniel Mack
2010-01-13 13:42 ` Stanislav Brabec
2010-01-13 15:33 ` Greg KH
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=771cded00911020318u3939a06dq75cd3504d6c0eb50@mail.gmail.com \
--to=haojian.zhuang@gmail.com \
--cc=Dirk@opfer-online.de \
--cc=alan@linux.intel.com \
--cc=arminlitzel@web.de \
--cc=daniel@caiaq.de \
--cc=dbaryshkov@gmail.com \
--cc=dsaxena@laptop.org \
--cc=eric.y.miao@gmail.com \
--cc=gregkh@suse.de \
--cc=haojian.zhuang@marvell.com \
--cc=lenz@cs.wisc.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=metan@ucw.cz \
--cc=omegamoon@gmail.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=rpurdie@rpsys.net \
--cc=thommycheck@gmail.com \
--cc=utx@penguin.cz \
/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
all inboxes | Powered by JetHome®