public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Tero Kristo <t-kristo@ti.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCHv4 9/9] OMAP3: PM: Disable / enable PRCM chain interrupts during wakeup from suspend
Date: Fri, 01 Jul 2011 13:10:03 -0700	[thread overview]
Message-ID: <87oc1dwyn8.fsf@ti.com> (raw)
In-Reply-To: <1309338303-2086-10-git-send-email-t-kristo@ti.com> (Tero Kristo's message of "Wed, 29 Jun 2011 12:05:03 +0300")

Tero Kristo <t-kristo@ti.com> writes:

> This prevents system hang while attempting to access suspended console.

Please add more detail.  Who is accessing console?   This sounds more
like it's masking a UART/console bug.

> Signed-off-by: Tero Kristo <t-kristo@ti.com>
> ---
>  arch/arm/mach-omap2/pm34xx.c |    6 ++++++
>  1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
> index e626a3d..dae0a8a 100644
> --- a/arch/arm/mach-omap2/pm34xx.c
> +++ b/arch/arm/mach-omap2/pm34xx.c
> @@ -418,6 +418,10 @@ void omap_sram_idle(void)
>  	pwrdm_post_transition();
>  
>  	clkdm_allow_idle(mpu_pwrdm->pwrdm_clkdms[0]);
> +	if (suspend_state != PM_SUSPEND_ON) {
> +		disable_irq(prcm_io_irq);
> +		disable_irq(prcm_wkup_irq);
> +	}

>  }
>  
>  int omap3_can_sleep(void)
> @@ -524,6 +528,8 @@ static void omap3_pm_end(void)
>  	suspend_state = PM_SUSPEND_ON;
>  	omap_uart_enable_irqs(1);
>  	enable_hlt();
> +	enable_irq(prcm_io_irq);
> +	enable_irq(prcm_wkup_irq);
>  	return;
>  }

The re-enable is in ->end(), shouldn't the disable be in ->begin() ?

Kevin



      reply	other threads:[~2011-07-01 20:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29  9:04 [PATCHv4 0/9] PRCM chain interrupt handling Tero Kristo
2011-06-29  9:04 ` [PATCHv4 1/9] omap: prcm: switch to a chained IRQ handler mechanism Tero Kristo
2011-06-29 16:53   ` Felipe Balbi
2011-06-29 16:54     ` Felipe Balbi
2011-06-30  5:51     ` Tero Kristo
2011-06-30  9:11       ` Felipe Balbi
2011-07-01 21:58   ` Kevin Hilman
2011-06-29  9:04 ` [PATCHv4 2/9] PRCM: Add support for PAD wakeup interrupts Tero Kristo
2011-06-30 17:10   ` Govindraj
2011-07-01 22:03   ` Kevin Hilman
2011-06-29  9:04 ` [PATCHv4 3/9] OMAP3: PM: remove serial resume / idle calls from idle path Tero Kristo
2011-06-30 16:50   ` Govindraj
2011-06-29  9:04 ` [PATCHv4 4/9] TEMP: OMAP3: Serial: Made serial to work properly with PRCM chain handler Tero Kristo
2011-06-29  9:04 ` [PATCHv4 5/9] TEMP: Serial: Added mux support Tero Kristo
2011-06-29  9:05 ` [PATCHv4 6/9] OMAP device: change pr_warnings to pr_debugs Tero Kristo
2011-07-01 22:05   ` Kevin Hilman
2011-06-29  9:05 ` [PATCHv4 7/9] OMAP: hwmod: enable / disable pad wakeups for a module dynamically Tero Kristo
2011-07-01 22:18   ` Kevin Hilman
2011-07-02 11:10     ` Govindraj
2011-06-29  9:05 ` [PATCHv4 8/9] TEMP: OMAP: serial: remove padconf hacks Tero Kristo
2011-06-29  9:05 ` [PATCHv4 9/9] OMAP3: PM: Disable / enable PRCM chain interrupts during wakeup from suspend Tero Kristo
2011-07-01 20:10   ` Kevin Hilman [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=87oc1dwyn8.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=t-kristo@ti.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