linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eddie Dawydiuk <eddie@embeddedarm.com>
To: linuxppc-dev@ozlabs.org, Grant Likely <grant.likely@secretlab.ca>
Subject: FPGA IRQ design question
Date: Wed, 22 Apr 2009 07:49:38 -0700	[thread overview]
Message-ID: <49EF2E82.9080905@embeddedarm.com> (raw)

Hello,

I'm working on a board based on the Yosemite AMCC 440EP. We have an FPGA 
connected via the PCI bus, and has an IRQ line connected directly to the 440EP. 
The FPGA implements two registers to indicate which core generated the 
interrupt. So now the question is from a design standpoint is it preferable to 
setup the IRQ as a single external IRQ then have each driver request this same 
IRQ. In each ISR the driver is responsible for checking the FPGA registers to 
see if the interrupt is intended for itself. Or would it be preferable to modify 
the lower level irq routines such that multiple software/virtual(not sure what 
the right term is here) irqs are created corresponding to the single external 
IRQ. Then abstract the details of the FPGA interrupt registers from each driver. 
Such that each driver request the proper software/virtual IRQ and requires no 
knowledge of the fpga irq registers. Any comments would be appreciated.

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

             reply	other threads:[~2009-04-22 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 14:49 Eddie Dawydiuk [this message]
2009-04-22 14:57 ` FPGA IRQ design question Grant Likely
2009-04-22 18:05   ` Eddie Dawydiuk
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=49EF2E82.9080905@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).