From: slash.tmp@free.fr (Mason)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] PCI: Add tango MSI controller support
Date: Wed, 29 Mar 2017 17:50:52 +0200 [thread overview]
Message-ID: <e8076081-545c-4c20-2d80-b66e9d3c8d9a@free.fr> (raw)
In-Reply-To: <0541e62a-c87a-2e69-a7d1-28f886ad04c2@free.fr>
On 29/03/2017 15:16, Mason wrote:
> But I don't understand how to get my pcie pointer back in irq_ack
> or irq_unmask, or the relevant msi. Can you throw me a clue?
Let's see... the irq_chip call-backs receive an irq_data pointer.
struct irq_data - per irq chip data passed down to chip functions
struct irq_chip - hardware interrupt chip descriptor
irq_data contains a void *chip_data member.
Can I use chip_data to stash a struct tango_pcie pointer?
/**
* irq_set_chip_data - set irq chip data for an irq
* @irq: Interrupt number
* @data: Pointer to chip specific data
*
* Set the hardware irq chip data for an irq
*/
int irq_set_chip_data(unsigned int irq, void *data)
But where would I call it? And for which irq?
Otherwise, I found by trial-and-error that I can reach pcie through
data->domain->parent->host_data
data->domain == msi_dom
msi_dom->parent == irq_dom
irq_dom->host_data == pcie
But data->irq and data->hwirq don't hold the MSI index :-(
I suppose I have to ask for some mapping?
Regards.
next prev parent reply other threads:[~2017-03-29 15:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 11:11 [PATCH v3 0/2] Tango PCIe controller support Marc Gonzalez
2017-03-29 11:29 ` [PATCH v3 1/2] PCI: Add tango MSI " Marc Gonzalez
2017-03-29 12:29 ` Marc Zyngier
2017-03-29 13:16 ` Mason
2017-03-29 15:50 ` Mason [this message]
2017-03-29 11:34 ` [PATCH v3 2/2] PCI: Add tango PCIe host bridge support Marc Gonzalez
2017-03-29 12:19 ` Robin Murphy
2017-03-29 12:53 ` Mason
2017-03-29 14:33 ` Robin Murphy
2017-03-29 14:38 ` David Laight
2017-03-30 12:09 ` kbuild test robot
2017-04-03 14:51 ` Rob Herring
2017-04-09 13:09 ` Mason
2017-03-30 20:56 ` [PATCH v3 0/2] Tango PCIe controller support Mason
2017-03-31 22:05 ` Mason
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=e8076081-545c-4c20-2d80-b66e9d3c8d9a@free.fr \
--to=slash.tmp@free.fr \
--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