From: Bjorn Helgaas <bhelgaas@google.com>
To: Pratyush Anand <pratyush.anand@gmail.com>
Cc: Lucas Stach <l.stach@pengutronix.de>,
Jingoo Han <jingoohan1@gmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
patchwork-lst@pengutronix.de
Subject: Re: [PATCH v2 2/2] PCI: designware: implement multivector MSI irq setup
Date: Mon, 10 Aug 2015 17:38:57 -0500 [thread overview]
Message-ID: <20150810223857.GC13982@google.com> (raw)
In-Reply-To: <CAHM4w1=Sz1xJ1OGc9xAMVCv8hMLwnWmGrkRLHdqpdC7EgzEbpQ@mail.gmail.com>
On Tue, Aug 04, 2015 at 08:41:15PM +0530, Pratyush Anand wrote:
> On Thu, Jul 23, 2015 at 8:19 PM, Lucas Stach <l.stach@pengutronix.de> wrote:
> > Allows to set up and use multiple MSI irqs per device.
> >
> > Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Thanks Lucas, I'm hoping for a little refactoring as Pratyush suggests
and maybe a third patch to fill in the upper bytes of the message? Or
do those look not feasible?
Bjorn
> > ---
> > The ifdef is needed to avoid a compile error on
> > !CONFIG_PCI_MSI, as msi_list is only part of pci_dev
> > when the kernel is compiled with MSI support.
> >
> > v2: move ifdeffery inside single function
> > ---
> > drivers/pci/host/pcie-designware.c | 43 ++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 43 insertions(+)
> >
> > diff --git a/drivers/pci/host/pcie-designware.c b/drivers/pci/host/pcie-designware.c
> > index 69486be7181e..52c600327805 100644
> > --- a/drivers/pci/host/pcie-designware.c
> > +++ b/drivers/pci/host/pcie-designware.c
> > @@ -286,6 +286,9 @@ static int assign_irq(int no_irqs, struct msi_desc *desc, int *pos)
> > }
> >
> > *pos = pos0;
> > + desc->nvec_used = no_irqs;
> > + desc->msi_attrib.multiple = order_base_2(no_irqs);
> > +
> > return irq;
> >
> > no_valid_irq:
> > @@ -323,6 +326,45 @@ static int dw_msi_setup_irq(struct msi_controller *chip, struct pci_dev *pdev,
> > return 0;
> > }
> >
> > +static int dw_msi_setup_irqs(struct msi_controller *chip, struct pci_dev *pdev,
> > + int nvec, int type)
> > +{
> > +#ifdef CONFIG_PCI_MSI
> > + int irq, pos;
> > + struct msi_desc *desc;
> > + struct msi_msg msg;
> > + struct pcie_port *pp = sys_to_pcie(pdev->bus->sysdata);
> > +
> > + /* MSI-X interrupts are not supported */
> > + if (type == PCI_CAP_ID_MSIX)
> > + return -EINVAL;
> > +
> > + WARN_ON(!list_is_singular(&pdev->msi_list));
> > + desc = list_entry(pdev->msi_list.next, struct msi_desc, list);
> > +
>
> Probably existing function dw_msi_setup_irq() can be re-factored and code after
> this line can be reused from refactored function, as they are almost same.
>
> > + irq = assign_irq(nvec, desc, &pos);
> > + if (irq < 0)
> > + return irq;
> > +
> > + if (pp->ops->get_msi_addr)
> > + msg.address_lo = pp->ops->get_msi_addr(pp);
> > + else
> > + msg.address_lo = virt_to_phys((void *)pp->msi_data);
> > + msg.address_hi = 0x0;
> > +
>
> Although, not specific to this patch, but since we are now going to have
> ARM64 support for DW as well, so it would be nice to fill msg.address_hi
> with upper bytes rather hard-coding as 0.
>
> > + if (pp->ops->get_msi_data)
> > + msg.data = pp->ops->get_msi_data(pp, pos);
> > + else
> > + msg.data = pos;
> > +
> > + pci_write_msi_msg(irq, &msg);
> > +
> > + return 0;
>
> ~Pratyush
next prev parent reply other threads:[~2015-08-10 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 14:49 [PATCH v2 1/2] PCI: allow MSI chip providers to implement their own multivector MSI setup Lucas Stach
2015-07-23 14:49 ` [PATCH v2 2/2] PCI: designware: implement multivector MSI irq setup Lucas Stach
2015-08-04 15:11 ` Pratyush Anand
2015-08-10 22:38 ` Bjorn Helgaas [this message]
2015-08-11 7:56 ` Lucas Stach
2015-08-11 14:43 ` Bjorn Helgaas
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=20150810223857.GC13982@google.com \
--to=bhelgaas@google.com \
--cc=jingoohan1@gmail.com \
--cc=l.stach@pengutronix.de \
--cc=linux-pci@vger.kernel.org \
--cc=patchwork-lst@pengutronix.de \
--cc=pratyush.anand@gmail.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 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).