Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758645AbbGHKsp (ORCPT ); Wed, 8 Jul 2015 06:48:45 -0400 Received: from www.linutronix.de ([62.245.132.108]:36565 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757238AbbGHKsn (ORCPT ); Wed, 8 Jul 2015 06:48:43 -0400 Date: Wed, 8 Jul 2015 12:48:34 +0200 (CEST) From: Thomas Gleixner To: Marc Zyngier cc: Bjorn Helgaas , Jiang Liu , Jason Cooper , linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Yijing Wang , Ma Jun , Lorenzo Pieralisi Subject: Re: [PATCH v3 09/15] irqchip: gicv3-its: Split PCI/MSI code from the core ITS driver In-Reply-To: <1436289485-28230-10-git-send-email-marc.zyngier@arm.com> Message-ID: References: <1436289485-28230-1-git-send-email-marc.zyngier@arm.com> <1436289485-28230-10-git-send-email-marc.zyngier@arm.com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 927 Lines: 33 On Tue, 7 Jul 2015, Marc Zyngier wrote: > +static int its_pci_msi_prepare(struct irq_domain *domain, struct device *dev, > + int nvec, msi_alloc_info_t *info) > +{ > + struct pci_dev *pdev; > + struct its_pci_alias dev_alias; > + > + if (!dev_is_pci(dev)) > + return -EINVAL; > + > + pdev = to_pci_dev(dev); > + dev_alias.pdev = pdev; > + dev_alias.count = nvec; > + > + pci_for_each_dma_alias(pdev, its_get_pci_alias, &dev_alias); > + > + return its_msi_prepare(domain, dev_alias.dev_id, dev_alias.count, info); I don't think you need its_msi_prepare() exposed to child drivers. Something like domain->parent->ops->msi_prepare() should do the trick. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/