linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dirac3000@gmail.com (dirac3000)
To: linux-arm-kernel@lists.infradead.org
Subject: DMA: PL330: support for multiple irqs?
Date: Tue, 03 Jan 2012 18:13:14 +0100	[thread overview]
Message-ID: <4F03372A.6050809@gmail.com> (raw)

Hi,

I have noticed the current PL330 driver does not provide any support for
multiples interrupts, even if the controller allows such implementation
(e.g.: one interrupt line for channel).

So far the driver takes the first element of the IRQ field in the
amba_device structure and makes a request on that IRQ, but I am working
on a PL330 with 7 different IRQ lines (6 for events + 1 for irq_abort).

A possibility would be to change the driver to loop over the
amba_device->irq array, but this is limited to max 2 IRQs, and I don't
understand this limitation.

Has anybody worked on a similar configuration?

             reply	other threads:[~2012-01-03 17:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 17:13 dirac3000 [this message]
2012-01-03 17:25 ` DMA: PL330: support for multiple irqs? Russell King - ARM Linux

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=4F03372A.6050809@gmail.com \
    --to=dirac3000@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).