public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Percival <matthew@capgo.com>
To: Linux OMAP Open Source <linux-omap-open-source@linux.omap.com>
Subject: Re: Regarding McBSP Int ...help needed...
Date: Fri, 16 Dec 2005 09:31:40 +1100	[thread overview]
Message-ID: <1134685901.8910.3.camel@localhost.localdomain> (raw)
In-Reply-To: <D8595042F3765A4285B848A78A2C2ED101E3A3EA@bsdmsg002.corp.satyam.ad>

G'Day,

> Void McBSPRxInterrupt(Void)
> {   
>       Uns McBSP1Data;
>      Uns InterruptStatus; 
>       
>       //code to check if the interrupt is from McBSP1 or McBSP3
>      InterruptStatus = inw(_LEV2_SIR_FIQ);
>      
>      if(InterruptStatus & 0x0002)
>      {
>       
> 	  McBSP1Data = inw(_MCBSP1_DRR1); // copy contents of McBSP
> receive
> //register to variable
>       
> 	}
> 	
> }

	It looks like you have the start right, but the end is missing
something.  Here is an ISR from my DSP code:

void level21_handler(Arg arg)
{
	MdUns irq = read_reg(DSP_L21_SIR_FIQ);
	timer_handler();
	write_reg(read_reg(DSP_L21_CONTROL) | NEW_FIQ_AGR, DSP_L21_CONTROL);
}

	You need to write NEW_FIQ_AGR to DSP_L20_CONTROL (L2.0 for McBSP; L2.1
here because it is a GPTimer) at the end of your ISR.  If I am
remembering correctly, this tells the Interrupt module that you have
completed servicing the current interrupt, and for it to calculate the
next interrupt to be serviced.  This is in a 5912, but there should be
something equivalent in the 5910.

	-- Matthew

      reply	other threads:[~2005-12-15 22:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-15 12:42 Regarding McBSP Int ...help needed Raghu_Mallya
2005-12-15 22:31 ` Matthew Percival [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=1134685901.8910.3.camel@localhost.localdomain \
    --to=matthew@capgo.com \
    --cc=linux-omap-open-source@linux.omap.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