From: Eddie Dawydiuk <eddie@embeddedarm.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: FPGA IRQ design question
Date: Wed, 22 Apr 2009 11:05:01 -0700 [thread overview]
Message-ID: <49EF5C4D.6040402@embeddedarm.com> (raw)
In-Reply-To: <fa686aa40904220757u1bcf1693oc2329c67209249ac@mail.gmail.com>
Grant,
> However, if you're writing one-off custom drivers and there is no
> common coded needed for acking irqs, then I would probably just use
> the external IRQ.
Thanks for the suggestions I think going to just use the external IRQ. As a
result I've been reading through a few different dts files to try to understand
how/where to specify this in the dts file. I see in the Yosemite dts file the
PCI bus device node has an interrupt-map-mask and an interrupt-map.
e.g.
PCI0: pci@ec000000 {
device_type = "pci";
...
/* Bamboo has all 4 IRQ pins tied together per slot */
interrupt-map-mask = <0xf800 0x0 0x0 0x0>;
interrupt-map = <
/* IDSEL 1 */
0x800 0x0 0x0 0x0 &UIC0 0x1c 0x8
...
};
As far as I can tell this appears to be the proper location to specify that the
PCI device(FPGA) connects an the IRQ to an external IRQ on the AMCC 440EP. I see
where the interrupt controller(e.g. &UIC0), the interrupt number(0x1C), and the
sense(0x8) of the external interrupt is specified. But I'm a bit puzzled by some
of the other information.
Is this the proper place in the dts file to specify that the FPGA connects and
external interrupt to the SoC? Can you point me to a document explaining the
interrupt-map-mask and interrupt-map arguments?
Thanks for any pointers.
--
Best Regards,
________________________________________________________________
Eddie Dawydiuk, Technologic Systems | voice: (480) 837-5200
16525 East Laser Drive | fax: (480) 837-5300
Fountain Hills, AZ 85268 | web: www.embeddedARM.com
next prev parent reply other threads:[~2009-04-22 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 14:49 FPGA IRQ design question Eddie Dawydiuk
2009-04-22 14:57 ` Grant Likely
2009-04-22 18:05 ` Eddie Dawydiuk [this message]
2009-04-22 18:07 ` Wolfgang Grandegger
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=49EF5C4D.6040402@embeddedarm.com \
--to=eddie@embeddedarm.com \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@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).