All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joao Pinto <Joao.Pinto@synopsys.com>
To: Murali Karicheri <m-karicheri2@ti.com>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Bjorn Helgaas <bhelgaas@google.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Minghuan Lian <minghuan.Lian@freescale.com>,
	Mingkai Hu <mingkai.hu@freescale.com>,
	"Roy Zang" <tie-fei.zang@freescale.com>,
	Richard Zhu <hongxing.zhu@nxp.com>,
	Lucas Stach <l.stach@pengutronix.de>,
	Niklas Cassel <niklas.cassel@axis.com>,
	Jesper Nilsson <jesper.nilsson@axis.com>,
	Zhou Wang <wangzhou1@hisilicon.com>,
	Gabriele Paoloni <gabriele.paoloni@huawei.com>,
	Stanimir Varbanov <svarbanov@mm-sol.com>,
	<Gustavo.Pimentel@synopsys.com>,
	linux-pci <linux-pci@vger.kernel.org>
Subject: Re-activate task to add MSI-X to pcie-designware
Date: Thu, 7 Dec 2017 15:14:22 +0000	[thread overview]
Message-ID: <647c9bb3-94f6-a138-fbde-e946c105d517@synopsys.com> (raw)

Hello to all,

I am sending this e-mail to request your opinion about the tasks needed to add
support for MSI-X for pcie-designware based solutions.

A few months ago I submited a patch-set that added support for MSI-X:

[v2,9/9] pci: remove limitation of the number of the available IRQs
https://patchwork.ozlabs.org/patch/771320/
[v2,8/9] pci: removing old irq api from pcie-designware
https://patchwork.ozlabs.org/patch/771360/
[v2,7/9] pci: keystone SoC driver adapted to new irq API
https://patchwork.ozlabs.org/patch/771361/
[v2,6/9] pci: qcom SoC driver adapted to new irq API
https://patchwork.ozlabs.org/patch/771362/
[v2,5/9] pci: generic PCIe DW driver adapted to new irq API
https://patchwork.ozlabs.org/patch/771365/
[v2,4/9] pci: artpec6 SoC driver adapted to new irq API
https://patchwork.ozlabs.org/patch/771364/
[v2,3/9] pci: imx6 SoC driver adapted to new irq API
https://patchwork.ozlabs.org/patch/771363/
[v2,2/9] pci: exynos SoC driver adapted to new irq API
https://patchwork.ozlabs.org/patch/771359/
[v2,1/9] pci: adding new irq api to pci-designware
https://patchwork.ozlabs.org/patch/771366/

The patch-set was globally accepted, but it broke the MSI mechanism for
Keystone, due to its specificity.

We are now going to resume this task and we would like to have your feedback
about our plan:

Task 1: Help TI to create a keystone_msi driver to isolate its custom msi mechanism
Task 2: Port the existing patches to the new kernel version (except the keystone
one)

If TI can do the keystone_msi implementation it would be easier. If it's not
possible, we volunteer to do it, but we will need testing & debug assistance.

I appreciate very much your attention and feedback.

Thanks and have a good day,
Joao Pinto

             reply	other threads:[~2017-12-07 15:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-07 15:14 Joao Pinto [this message]
2017-12-07 15:42 ` Re-activate task to add MSI-X to pcie-designware Lucas Stach
2017-12-07 15:53   ` Marc Zyngier
2017-12-08 11:04     ` Lorenzo Pieralisi
2017-12-08 11:02 ` Lorenzo Pieralisi
2017-12-11 13:23   ` Kishon Vijay Abraham I
2017-12-18 16:01     ` Gustavo Pimentel
2017-12-20 13:03       ` Kishon Vijay Abraham I
2017-12-21 14:08         ` Gustavo Pimentel
2017-12-23 10:16           ` Kishon Vijay Abraham I
2017-12-26 12:57             ` Kishon Vijay Abraham I
2017-12-27 14:25               ` Gustavo Pimentel
2017-12-28  8:53                 ` Kishon Vijay Abraham I
2017-12-28 14:58                 ` Kishon Vijay Abraham I
2017-12-29  9:48                   ` Gustavo Pimentel
2017-12-29 10:05                     ` Kishon Vijay Abraham I
2018-01-02 19:21                       ` Gustavo Pimentel
2018-01-04 11:12                         ` Kishon Vijay Abraham I
2018-01-09 10:32                       ` Gustavo Pimentel
2018-01-17 13:05                         ` Kishon Vijay Abraham I

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=647c9bb3-94f6-a138-fbde-e946c105d517@synopsys.com \
    --to=joao.pinto@synopsys.com \
    --cc=Gustavo.Pimentel@synopsys.com \
    --cc=bhelgaas@google.com \
    --cc=gabriele.paoloni@huawei.com \
    --cc=hongxing.zhu@nxp.com \
    --cc=jesper.nilsson@axis.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-pci@vger.kernel.org \
    --cc=m-karicheri2@ti.com \
    --cc=marc.zyngier@arm.com \
    --cc=minghuan.Lian@freescale.com \
    --cc=mingkai.hu@freescale.com \
    --cc=niklas.cassel@axis.com \
    --cc=svarbanov@mm-sol.com \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=tie-fei.zang@freescale.com \
    --cc=wangzhou1@hisilicon.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.