linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Gustavo Pimentel <gustavo.pimentel@synopsys.com>
Cc: "marc.zyngier@arm.com" <marc.zyngier@arm.com>,
	"Joao.Pinto@synopsys.com" <Joao.Pinto@synopsys.com>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"jingoohan1@gmail.com" <jingoohan1@gmail.com>,
	"kishon@ti.com" <kishon@ti.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"m-karicheri2@ti.com" <m-karicheri2@ti.com>,
	"thomas.petazzoni@free-electrons.com"
	<thomas.petazzoni@free-electrons.com>,
	"minghuan.Lian@freescale.com" <minghuan.Lian@freescale.com>,
	"mingkai.hu@freescale.com" <mingkai.hu@freescale.com>,
	"tie-fei.zang@freescale.com" <tie-fei.zang@freescale.com>,
	"hongxing.zhu@nxp.com" <hongxing.zhu@nxp.com>,
	"niklas.cassel@axis.com" <niklas.cassel@axis.com>,
	"jesper.nilsson@axis.com" <jesper.nilsson@axis.com>,
	"wangzhou1@hisilicon.com" <wangzhou1@hisilicon.com>,
	"gabriele.paoloni@huawei.com" <gabriele.paoloni@huawei.com>,
	"svarbanov@mm-sol.com" <svarbanov@mm-sol.com>,
	"nsekhar@ti.com" <nsekhar@ti.com>
Subject: Re: [PATCH v6 0/9] PCI: dwc: MSI-X feature
Date: Tue, 13 Feb 2018 13:36:35 +0100	[thread overview]
Message-ID: <1518525395.2744.14.camel@pengutronix.de> (raw)
In-Reply-To: <20180213122920.GB8981@e107981-ln.cambridge.arm.com>

Am Dienstag, den 13.02.2018, 12:29 +0000 schrieb Lorenzo Pieralisi:
> On Mon, Feb 12, 2018 at 06:14:29PM +0000, Gustavo Pimentel wrote:
> > Hi Lorenzo,
> > 
> > On 12/02/2018 12:23, Lorenzo Pieralisi wrote:
> > > On Fri, Jan 26, 2018 at 04:35:35PM +0000, Gustavo Pimentel wrote:
> > > > Replaces the use of IRQ domain hierarchy by the IRQ chained
> > > > used by
> > > > pcie-designware and each SoC specific driver in order to allow
> > > > new and
> > > > complex features like MSI-X.
> > > > 
> > > > Adds Synopsys Root Complex support for MSI-X feature.
> > > 
> > > Hi Gustavo,
> > > 
> > > please CC me for future patch versions. I have a question for
> > > you,
> > > the series definitely looks like it is going in the right
> > > direction
> > > but I do not understand the cover letter.
> > > 
> > > - You are not replacing the IRQ domain hierarchy, you are
> > > actually
> > >   introducing it properly. It may be just nomenclature but I
> > > though
> > >   I would mention that.
> > > - I really do not understand why this series is advertised as
> > >   "implementing MSI-X". I want to understand why MSI-X it is not
> > >   currently supported and why this series would enable it, I
> > >   honestly do not understand the reasoning behind this, it looks
> > >   a bit fuzzy.
> > > 
> > > Please note I am just asking clarifications on the $SUBJECT for
> > > my own
> > > understanding, the series is definitely the right thing to do and
> > > I am
> > > happy to target v4.17 for it.
> > 
> > Marc Zyngier also pointed out like you that the description is
> > confusing and
> > does not correspond to what is done in the code and now I also see
> > it now.
> > 
> > Please fell free to review and point out something wrong, only in
> > this way can I
> > evolve. :)
> 
> Sure. Let's start by discussing this:
> 
> https://patchwork.kernel.org/patch/5708521/
> 
> If it is a HW issue your patches can't solve it. If it is a SW issue
> patch above (and current mainline code - commit 19c5392eb1c1) is
> wrong.
> 
> Before updating the code I want to understand what the problem is
> with
> MSI-X in current mainline.
> 
> To be as clear as I can: this series is doing the *right* thing, I
> want
> to understand what the current driver is doing with MSIs and why, so
> that we can help you update the code correctly.

It's partly a software issue and partly a wrong understanding of MSI-X
on my side at the time. The DW hardware doesn't support different MSI
target addresses for individual MSIs, but that's just a optional
feature of MSI-X and not required to implement them correctly. Enabling
of MSI-X on the DW hardware via a proper software implementation is
fine.

Regards,
Lucas

  reply	other threads:[~2018-02-13 12:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-26 16:35 [PATCH v6 0/9] PCI: dwc: MSI-X feature Gustavo Pimentel
2018-01-26 16:35 ` [PATCH v6 1/9] PCI: dwc: Add IRQ chained API support Gustavo Pimentel
2018-02-09 11:10   ` Marc Zyngier
2018-02-12 17:58     ` Gustavo Pimentel
2018-02-12 18:15       ` Marc Zyngier
2018-01-26 16:35 ` [PATCH v6 2/9] PCI: dwc: exynos: Switch to use the IRQ chained API Gustavo Pimentel
2018-01-26 16:35 ` [PATCH v6 3/9] PCI: dwc: imx6: " Gustavo Pimentel
2018-01-26 16:35 ` [PATCH v6 4/9] PCI: dwc: artpec6: " Gustavo Pimentel
2018-01-26 16:35 ` [PATCH v6 5/9] PCI: dwc: designware: " Gustavo Pimentel
2018-01-26 16:35 ` [PATCH v6 6/9] PCI: dwc: qcom: " Gustavo Pimentel
2018-01-26 16:35 ` [PATCH v6 7/9] PCI: dwc: keystone: " Gustavo Pimentel
2018-01-26 16:35 ` [PATCH v6 8/9] PCI: dwc: Remove IRQ domain hierarchy API support Gustavo Pimentel
2018-01-26 16:35 ` [PATCH v6 9/9] PCI: dwc: Expand maximum number of IRQs from 32 to 256 Gustavo Pimentel
2018-02-12 12:23 ` [PATCH v6 0/9] PCI: dwc: MSI-X feature Lorenzo Pieralisi
2018-02-12 18:14   ` Gustavo Pimentel
2018-02-13 12:29     ` Lorenzo Pieralisi
2018-02-13 12:36       ` Lucas Stach [this message]
2018-02-13 14:04         ` Lorenzo Pieralisi

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=1518525395.2744.14.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=Joao.Pinto@synopsys.com \
    --cc=bhelgaas@google.com \
    --cc=gabriele.paoloni@huawei.com \
    --cc=gustavo.pimentel@synopsys.com \
    --cc=hongxing.zhu@nxp.com \
    --cc=jesper.nilsson@axis.com \
    --cc=jingoohan1@gmail.com \
    --cc=kishon@ti.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --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=nsekhar@ti.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 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).