From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Subrahmanya Lingappa <l.subrahmanya@mobiveil.co.in>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com,
mingkai.hu@nxp.com, peter.newton@nxp.com, minghuan.lian@nxp.com,
rajesh.raina@nxp.com, rajan.kapoor@nxp.com,
prabhjot.singh@nxp.com
Subject: Re: [PATCH v4 2/2] PCI: mobiveil: Add Mobiveil PCIe Host Bridge IP driver
Date: Mon, 11 Dec 2017 15:56:51 +0000 [thread overview]
Message-ID: <20171211155651.GA6822@red-moon> (raw)
In-Reply-To: <20171208182634.GA1885@e107981-ln.cambridge.arm.com>
On Fri, Dec 08, 2017 at 06:26:34PM +0000, Lorenzo Pieralisi wrote:
[...]
> > +static int mobiveil_pcie_init_irq_domain(struct mobiveil_pcie *pcie)
> > +{
> > + struct device *dev = &pcie->pdev->dev;
> > + struct device_node *node = dev->of_node;
> > +
> > + /* setup INTx */
> > + pcie->intx_domain =
> > + irq_domain_add_linear(node, PCI_NUM_INTX + 1, &intx_domain_ops,
> > + pcie);
> > +
> > + if (!pcie->intx_domain) {
> > + dev_err(dev, "Failed to get a INTx IRQ domain\n");
> > + return -ENODEV;
> > + }
> > + /* setup MSI */
> > + if (IS_ENABLED(CONFIG_PCI_MSI)) {
> > + pcie->msi_domain =
> > + irq_domain_add_linear(node,
> > + PCI_NUM_MSI,
> > + &msi_domain_ops,
> > + &pcie->msi_chip);
> > + if (!pcie->msi_domain) {
> > + dev_err(dev, "Failed to get a MSI IRQ domain\n");
> > + return -ENODEV;
> > + }
> > +
> > + mobiveil_pcie_enable_msi(pcie);
>
> You need to rewrite the MSI support - I will review it then, see above.
Actually it would be good to split MSI support in a separate patch,
to simplify the review.
Thanks,
Lorenzo
next prev parent reply other threads:[~2017-12-11 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 14:18 [PATCH v4 2/2] PCI: mobiveil: Add Mobiveil PCIe Host Bridge IP driver Subrahmanya Lingappa
2017-12-08 18:26 ` Lorenzo Pieralisi
2017-12-11 15:56 ` Lorenzo Pieralisi [this message]
2017-12-13 9:19 ` Subrahmanya Lingappa
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=20171211155651.GA6822@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=l.subrahmanya@mobiveil.co.in \
--cc=linux-pci@vger.kernel.org \
--cc=minghuan.lian@nxp.com \
--cc=mingkai.hu@nxp.com \
--cc=peter.newton@nxp.com \
--cc=prabhjot.singh@nxp.com \
--cc=rajan.kapoor@nxp.com \
--cc=rajesh.raina@nxp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.