linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Turquette <mturquette@ti.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "Gopinath, Thara" <thara@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] OMAP3: PRCM interrupt: only check for enabled PRCM IRQs
Date: Tue, 27 Apr 2010 11:52:21 -0500	[thread overview]
Message-ID: <4BD71645.8070804@ti.com> (raw)
In-Reply-To: <878w89rl6w.fsf@deeprootsystems.com>

Kevin Hilman wrote:
> commit cfabe8a950e252d26cdeb4a9bb11e2cabb2a50c6
> Author: Kevin Hilman <khilman@deeprootsystems.com>
> Date:   Mon Apr 26 14:59:09 2010 -0700
> 
>     OMAP3: PRCM interrupt: only check and clear enabled PRCM IRQs
>     
>     While handling PRCM IRQs, mask out interrupts that are not enabled in
>     PRM_IRQENABLE_MPU.  If these are not masked out, non-enabled
>     interrupts are caught, a WARN() is printed due to no 'handler' and the
>     events are cleared.  In addition to being noisy, this can also
>     interfere with independent polling of this register by SR/VP code.
>     
>     This was noticed using SmartReflex transitions which cause the VPx_*
>     interrupts to be handled since they are set in PRM_IRQSTATUS_MPU even
>     but not enabled in PRM_IRQENABLE_MPU.
>     
>     Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>

ACK.

Mike

> diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
> index fee2efb..c38016b 100644
> --- a/arch/arm/mach-omap2/pm34xx.c
> +++ b/arch/arm/mach-omap2/pm34xx.c
> @@ -266,13 +266,16 @@ static int _prcm_int_handle_wakeup(void)
>   */
>  static irqreturn_t prcm_interrupt_handler (int irq, void *dev_id)
>  {
> -	u32 irqstatus_mpu;
> +	u32 irqenable_mpu, irqstatus_mpu;
>  	int c = 0;
>  
> -	do {
> -		irqstatus_mpu = prm_read_mod_reg(OCP_MOD,
> -					OMAP3_PRM_IRQSTATUS_MPU_OFFSET);
> +	irqenable_mpu = prm_read_mod_reg(OCP_MOD,
> +					 OMAP3_PRM_IRQENABLE_MPU_OFFSET);
> +	irqstatus_mpu = prm_read_mod_reg(OCP_MOD,
> +					 OMAP3_PRM_IRQSTATUS_MPU_OFFSET);
> +	irqstatus_mpu &= irqenable_mpu;
>  
> +	do {
>  		if (irqstatus_mpu & (OMAP3430_WKUP_ST | OMAP3430_IO_ST)) {
>  			c = _prcm_int_handle_wakeup();
>  
> @@ -291,7 +294,11 @@ static irqreturn_t prcm_interrupt_handler (int irq, void *dev_id)
>  		prm_write_mod_reg(irqstatus_mpu, OCP_MOD,
>  					OMAP3_PRM_IRQSTATUS_MPU_OFFSET);
>  
> -	} while (prm_read_mod_reg(OCP_MOD, OMAP3_PRM_IRQSTATUS_MPU_OFFSET));
> +		irqstatus_mpu = prm_read_mod_reg(OCP_MOD,
> +					OMAP3_PRM_IRQSTATUS_MPU_OFFSET);
> +		irqstatus_mpu &= irqenable_mpu;
> +
> +	} while (irqstatus_mpu);
>  
>  	return IRQ_HANDLED;
>  }


      reply	other threads:[~2010-04-27 16:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 22:23 [PATCH] OMAP3: PRCM interrupt: only check for enabled PRCM IRQs Kevin Hilman
2010-04-27  0:37 ` Mike Turquette
2010-04-27  0:40   ` Mike Turquette
2010-04-27 15:04   ` Kevin Hilman
2010-04-27 16:52     ` Mike Turquette [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=4BD71645.8070804@ti.com \
    --to=mturquette@ti.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=thara@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;
as well as URLs for NNTP newsgroup(s).