From: ddaney.cavm@gmail.com (David Daney)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/3] irqchip/gicv3-its: Handle OF device tree "msi-map" properties.
Date: Tue, 22 Sep 2015 17:00:06 -0700 [thread overview]
Message-ID: <1442966406-13198-4-git-send-email-ddaney.cavm@gmail.com> (raw)
In-Reply-To: <1442966406-13198-1-git-send-email-ddaney.cavm@gmail.com>
From: David Daney <david.daney@cavium.com>
Call of_msi_map_rid() to handle mapping of the requester id.
Signed-off-by: David Daney <david.daney@cavium.com>
---
drivers/irqchip/irq-gic-v3-its-pci-msi.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/irqchip/irq-gic-v3-its-pci-msi.c b/drivers/irqchip/irq-gic-v3-its-pci-msi.c
index cf351c6..8b1c938 100644
--- a/drivers/irqchip/irq-gic-v3-its-pci-msi.c
+++ b/drivers/irqchip/irq-gic-v3-its-pci-msi.c
@@ -86,7 +86,8 @@ static int its_pci_msi_prepare(struct irq_domain *domain, struct device *dev,
pci_for_each_dma_alias(pdev, its_get_pci_alias, &dev_alias);
/* ITS specific DeviceID, as the core ITS ignores dev. */
- info->scratchpad[0].ul = dev_alias.dev_id;
+ info->scratchpad[0].ul = of_msi_map_rid(dev, domain->of_node,
+ dev_alias.dev_id);
return msi_info->ops->msi_prepare(domain->parent,
dev, dev_alias.count, info);
--
1.9.1
next prev parent reply other threads:[~2015-09-23 0:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 0:00 [PATCH v2 0/3] of, irqchip/gicv3-its: Handle "msi-map" properties David Daney
2015-09-23 0:00 ` [PATCH v2 1/3] Docs: dt: Add PCI MSI map bindings David Daney
2015-09-23 16:37 ` Marc Zyngier
2015-09-23 0:00 ` [PATCH v2 2/3] of/irq: Add new function of_msi_map_rid() David Daney
2015-09-23 16:52 ` Marc Zyngier
2015-09-23 16:59 ` David Daney
2015-09-23 17:07 ` Rob Herring
2015-09-23 17:12 ` David Daney
2015-09-23 0:00 ` David Daney [this message]
2015-09-23 17:01 ` [PATCH v2 3/3] irqchip/gicv3-its: Handle OF device tree "msi-map" properties Marc Zyngier
2015-09-23 17:08 ` David Daney
2015-09-23 17:52 ` Will Deacon
2015-09-23 18:18 ` Marc Zyngier
2015-09-23 19:23 ` Robin Murphy
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=1442966406-13198-4-git-send-email-ddaney.cavm@gmail.com \
--to=ddaney.cavm@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).