From: Kevin Hilman <khilman@deeprootsystems.com>
To: Tero Kristo <tero.kristo@nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAP3: Fixed crash bug with serial + suspend
Date: Tue, 03 Mar 2009 08:57:56 -0800 [thread overview]
Message-ID: <874oya7dd7.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1236073539-21607-1-git-send-email-tero.kristo@nokia.com> (Tero Kristo's message of "Tue\, 3 Mar 2009 11\:45\:39 +0200")
Tero Kristo <tero.kristo@nokia.com> writes:
> It was possible for an unhandled interrupt to occur if there was incoming
> serial traffic during wakeup from suspend. This was caused by the code
> in arch-arm/mach-omap2/serial.c keeping interrupt enabled all the time,
> but not acking its interrupts. Applies on top of PM branch.
>
> Signed-off-by: Tero Kristo <tero.kristo@nokia.com>
> ---
> arch/arm/mach-omap2/pm34xx.c | 15 +++++++++++++++
> arch/arm/mach-omap2/serial.c | 18 ++++++++++++++++++
> arch/arm/plat-omap/include/mach/serial.h | 1 +
> 3 files changed, 34 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
> index 9102cee..5a627db 100644
> --- a/arch/arm/mach-omap2/pm34xx.c
> +++ b/arch/arm/mach-omap2/pm34xx.c
> @@ -629,7 +629,22 @@ static void omap3_pm_finish(void)
> pm_idle = saved_idle;
> }
>
> +/* Hooks to enable / disable UART interrupts during suspend */
> +static int omap3_pm_begin(suspend_state_t state)
> +{
> + omap_uart_enable_irqs(0);
> + return 0;
> +}
> +
> +static void omap3_pm_end(void)
> +{
> + omap_uart_enable_irqs(1);
> + return;
> +}
> +
> static struct platform_suspend_ops omap_pm_ops = {
> + .begin = omap3_pm_begin,
> + .end = omap3_pm_end,
> .prepare = omap3_pm_prepare,
> .enter = omap3_pm_enter,
> .finish = omap3_pm_finish,
I think this functionality is more appropriate for the prepare/finish
hooks than the begin/end hooks. serial.c already has
omap_uart_prepare_suspend() hook where the interrupt disable could be
added., and a omap_uart_prepare_resume() call could be added to the
omap3_pm_finish.
> diff --git a/arch/arm/mach-omap2/serial.c b/arch/arm/mach-omap2/serial.c
> index 90f1c67..952da79 100644
> --- a/arch/arm/mach-omap2/serial.c
> +++ b/arch/arm/mach-omap2/serial.c
> @@ -432,6 +432,24 @@ static void omap_uart_idle_init(struct omap_uart_state *uart)
> WARN_ON(ret);
> }
>
> +void omap_uart_enable_irqs(int enable)
> +{
> + int i, ret;
> +
> + for (i = 0; i < OMAP_MAX_NR_PORTS; i++) {
> + struct plat_serial8250_port *p = serial_platform_data + i;
> + struct omap_uart_state *uart = &omap_uart[i];
> +
Can you use the "list_for_each_entry(uart, &uart_list, node)"
construct instead of a for loop? Or was there a reason to enable/ack
all serial interrupts, even those that have not been enabled.
> + if (!p->membase)
> + continue;
> + if (enable)
> + ret = request_irq(p->irq, omap_uart_interrupt,
> + IRQF_SHARED, "serial idle", (void *)uart);
> + else
> + free_irq(p->irq, (void *)uart);
> + }
> +}
> +
> static ssize_t sleep_timeout_show(struct kobject *kobj,
> struct kobj_attribute *attr,
> char *buf)
> diff --git a/arch/arm/plat-omap/include/mach/serial.h b/arch/arm/plat-omap/include/mach/serial.h
> index 8e89585..7ca1f27 100644
> --- a/arch/arm/plat-omap/include/mach/serial.h
> +++ b/arch/arm/plat-omap/include/mach/serial.h
> @@ -47,6 +47,7 @@ extern void omap_uart_check_wakeup(void);
> extern void omap_uart_prepare_suspend(void);
> extern void omap_uart_prepare_idle(int num);
> extern void omap_uart_resume_idle(int num);
> +extern void omap_uart_enable_irqs(int enable);
> #endif
>
> #endif
> --
> 1.5.4.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-03-03 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 9:45 [PATCH] OMAP3: Fixed crash bug with serial + suspend Tero Kristo
2009-03-03 16:57 ` Kevin Hilman [this message]
2009-03-04 8:52 ` Tero.Kristo
2009-03-04 20:47 ` Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2009-03-05 14:32 Tero Kristo
2009-03-05 17:10 ` Kevin Hilman
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=874oya7dd7.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=tero.kristo@nokia.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