From: Eugene Surovegin <ebs@ebshome.net>
To: Daniel Ann <ktdann@gmail.com>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: openpic_init() functionality
Date: Sun, 31 Jul 2005 20:44:28 -0700 [thread overview]
Message-ID: <20050801034428.GA1713@gate.ebshome.net> (raw)
In-Reply-To: <9b7ca6570507311900212f0179@mail.gmail.com>
On Mon, Aug 01, 2005 at 11:00:29AM +0900, Daniel Ann wrote:
> Hi folks,
>
> Just been reading openpic_init() function and found something weird,
> so I thought I might turn to pro.
> It's a part where it initialises all external sources. Code goes
> something like this,
> [begin]
> /* Init all external sources, including possibly the cascade. */
> for (i = 0; i < NumSources; i++) {
> int sense;
>
> if (ISR[i] == 0)
> continue;
> [snip]
> openpic_initirq(i, 8, i+offset, (sense & IRQ_POLARITY_MASK),
> (sense & IRQ_SENSE_MASK));
> [end]
>
> I can see what openpic_initirq does. But what I dont see is enable
> part. openpic_initirq only configures interrupt but does not enable
> it. And going thru the rest of the code, nothing calls
> openpic_enable_irq().
> Can somebody tell me how should these interrupts get enabled ?
>
> Reason is, if I dont force openpic_enable_irq() after
> openpic_initirq(), then at the end of booting, I see none of my
> interrupts enabled. Im sure somewhere down the line it should get
> enabled, but where ?
It's enabled when somebody calls request_irq, for example.
Generic IRQ code is linked to OpenPIC implementation through
'struct hw_interrupt_type open_pic'.
Next time, try adding printk to a function at question and you'll
easily see that it's being called.
--
Eugene
prev parent reply other threads:[~2005-08-01 3:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-01 2:00 openpic_init() functionality Daniel Ann
2005-08-01 3:44 ` Eugene Surovegin [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=20050801034428.GA1713@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=ktdann@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
/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).