linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: R.Patil@mei-india.com
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [Solved] Interrupt handler not executed
Date: Mon, 14 Jan 2013 17:04:21 +0530	[thread overview]
Message-ID: <OFF2DB166D.6CFADCBA-ON65257AF3.003F9206-65257AF3.003F9210@LocalDomain> (raw)
In-Reply-To: <1357928171.5475.4@snotra>

Hello Scott,

Thanks for your immediate response. The problem has been resolved. Actually=
, I was wrong in pointing out the problem.=20

The problem was lying in interrupt handler. The first statement in interrup=
t handler was disable=5Firq() which was leading into a deadlock. I replaced=
 'disable=5Firq' with 'disable=5Firq=5Fnosync()' and it worked. =20

Thanks and Regards,
Rahul Patil

-----Scott Wood <scottwood@freescale.com> wrote: -----

To: <R.Patil@mei-india.com>
From: Scott Wood <scottwood@freescale.com>
Date: 01/11/2013 11:46PM
Cc: <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Interrupt handler not executed

On 01/11/2013 01:36:29 AM, R.Patil@mei-india.com wrote:
> Hello,
>=20
> We are working on board based on Freescale MPC8313ERDB. We have =20
> ported linux 3.0.46 kernel on it. In one of device driver written by =20
> us, we need to take some action upon asserting IRQ0 interrupt. For =20
> this we have written interrupt handler which takes care of this. We =20
> are able register interrupt handler successfully with the help of =20
> 'request=5Firq'. We confirmed this by checking respective entry in =20
> '/proc/interrupts'. We have also confirmed assertion of interrupt =20
> line (IRQ0) on oscilloscope. The problem is, interrupt handler does =20
> not execute upon asserting the interrupt line.

What IRQ number did you pass to request=5Firq()?  request=5Firq() takes =20
virtual interrupt numbers, not anything out of the chip manual.

If that's not the issue, is the interrupt configured properly for level =20
and sense?

-Scott

Email Disclaimer:
  ---------------------------

This e-mail and any files transmitted with it are for the sole use of the i=
ntended recipient(s) and may contain confidential and  privileged informati=
on. Computer viruses can be transmitted via email.The recipient should chec=
k this email and any  attachments for the presence of viruses. The company =
accepts no liability for any damage caused by any virus transmitted by this=
 email.

      reply	other threads:[~2013-01-14 11:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11  7:36 Interrupt handler not executed R.Patil
2013-01-11 18:16 ` Scott Wood
2013-01-14 11:34   ` R.Patil [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=OFF2DB166D.6CFADCBA-ON65257AF3.003F9206-65257AF3.003F9210@LocalDomain \
    --to=r.patil@mei-india.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=scottwood@freescale.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).