linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* 440 PCI adapter card interupt handling question
@ 2002-06-13 22:10 Khai Trinh
  2002-06-15 15:21 ` Matt Porter
  0 siblings, 1 reply; 4+ messages in thread
From: Khai Trinh @ 2002-06-13 22:10 UTC (permalink / raw)
  To: linuxppc-embedded


Our custom board is a IBM 440GP based pci slave
adapter card, we will configure it to use the Simple
Message Passing Unit to allow interrupt generation to
the 440 from the Host. My question are Where in the
Linux kernel code can I initialize the 440 onboard
interrupt controller to enable this interrupt to
happen? And how do I register my interrupt handling
routine to service inbound interrupt from the Host?

Regards,
--Khai


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: 440 PCI adapter card interupt handling question
  2002-06-13 22:10 440 PCI adapter card interupt handling question Khai Trinh
@ 2002-06-15 15:21 ` Matt Porter
  2002-06-17 17:32   ` Khai Trinh
  0 siblings, 1 reply; 4+ messages in thread
From: Matt Porter @ 2002-06-15 15:21 UTC (permalink / raw)
  To: Khai Trinh; +Cc: linuxppc-embedded


On Thu, Jun 13, 2002 at 03:10:11PM -0700, Khai Trinh wrote:
>
> Our custom board is a IBM 440GP based pci slave
> adapter card, we will configure it to use the Simple
> Message Passing Unit to allow interrupt generation to
> the 440 from the Host. My question are Where in the
> Linux kernel code can I initialize the 440 onboard
> interrupt controller to enable this interrupt to
> happen? And how do I register my interrupt handling
> routine to service inbound interrupt from the Host?

You don't use the UICs to generate an outbound message
interrupt so there is no "initialization".  There is a
hardwired UIC interrupt generated by inbound message
interrupts.

Since you are talking about writing a basic Linux
device driver, I suggest you see one of the many
books on the topic to learn some of the basics.
request_irq(), for example, is explained with many
examples.

Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: 440 PCI adapter card interupt handling question
  2002-06-15 15:21 ` Matt Porter
@ 2002-06-17 17:32   ` Khai Trinh
  2002-06-17 17:58     ` Matt Porter
  0 siblings, 1 reply; 4+ messages in thread
From: Khai Trinh @ 2002-06-17 17:32 UTC (permalink / raw)
  To: Matt Porter; +Cc: linuxppc-embedded


But Matt,

request_irq() is used to register the ISR with an irq#
between 0-12 (for the 440). However, the inbound
message interrupt is hardwire as you stated. How can I
use request_irq() to register hardwire interrupt
signal to the UIC? Or is there another kernel call to
handle such services?

Regards,
--Khai
--- Matt Porter <porter@cox.net> wrote:
>
> On Thu, Jun 13, 2002 at 03:10:11PM -0700, Khai Trinh
> wrote:
> >
> > Our custom board is a IBM 440GP based pci slave
> > adapter card, we will configure it to use the
> Simple
> > Message Passing Unit to allow interrupt generation
> to
> > the 440 from the Host. My question are Where in
> the
> > Linux kernel code can I initialize the 440 onboard
> > interrupt controller to enable this interrupt to
> > happen? And how do I register my interrupt
> handling
> > routine to service inbound interrupt from the
> Host?
>
> You don't use the UICs to generate an outbound
> message
> interrupt so there is no "initialization".  There is
> a
> hardwired UIC interrupt generated by inbound message
> interrupts.
>
> Since you are talking about writing a basic Linux
> device driver, I suggest you see one of the many
> books on the topic to learn some of the basics.
> request_irq(), for example, is explained with many
> examples.
>
> Regards,
> --
> Matt Porter
> porter@cox.net
> This is Linux Country. On a quiet night, you can
> hear Windows reboot.
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: 440 PCI adapter card interupt handling question
  2002-06-17 17:32   ` Khai Trinh
@ 2002-06-17 17:58     ` Matt Porter
  0 siblings, 0 replies; 4+ messages in thread
From: Matt Porter @ 2002-06-17 17:58 UTC (permalink / raw)
  To: Khai Trinh; +Cc: linuxppc-embedded


On Mon, Jun 17, 2002 at 10:32:11AM -0700, Khai Trinh wrote:
> But Matt,
>
> request_irq() is used to register the ISR with an irq#
> between 0-12 (for the 440). However, the inbound
> message interrupt is hardwire as you stated. How can I
> use request_irq() to register hardwire interrupt
> signal to the UIC? Or is there another kernel call to
> handle such services?

You've lost me, request_irq() isn't limited to Linux interrupt
numbers 0-12 on 440.  Everything on the cascaded UICs has been
populated in the irq_desc and is therefore available.

Regards,
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2002-06-17 17:58 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-06-13 22:10 440 PCI adapter card interupt handling question Khai Trinh
2002-06-15 15:21 ` Matt Porter
2002-06-17 17:32   ` Khai Trinh
2002-06-17 17:58     ` Matt Porter

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).