From: Eugene Surovegin <ebs@ebshome.net>
To: Sanjay Bajaj <sbajaj@tsi-telsys.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Unable to capture device interrupts on ppc440gx?
Date: Mon, 18 Apr 2005 09:14:20 -0700 [thread overview]
Message-ID: <20050418161420.GA25352@gate.ebshome.net> (raw)
In-Reply-To: <0007F077BB3476449151699150E8FEA20592C8@exchange.tsi-telsys.com>
On Mon, Apr 18, 2005 at 12:02:52PM -0400, Sanjay Bajaj wrote:
> In the device driver open function, I call request_irq() to register
> my interrupt handler function to a specified IRQ number. It
> succeeds.
> But when I enable the interrupt (and we can detect the hardware line
> is active) on the hardware, the interrupt handler in NOT invoked. Is
> there something I am missing? Any help or pointers are appreciated.
Did you configure polarity and triggering settings for this IRQ
source? If not, look for example at ebony.c (ppc4xx_uic_ext_irq_cfg)
keeping in mind, that Ebony has 440GP CPU. 440GX has 5 additional
IRQ lines.
--
Eugene
next prev parent reply other threads:[~2005-04-18 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 16:02 Unable to capture device interrupts on ppc440gx? Sanjay Bajaj
2005-04-18 16:14 ` Eugene Surovegin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-18 17:02 Sanjay Bajaj
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=20050418161420.GA25352@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=linuxppc-embedded@ozlabs.org \
--cc=sbajaj@tsi-telsys.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