imx.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Frank Li <Frank.Li@nxp.com>
Cc: tglx@linutronix.de, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, shawnguo@kernel.org,
	s.hauer@pengutronix.de, kw@linux.com, bhelgaas@google.com,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
	peng.fan@nxp.com, aisheng.dong@nxp.com, jdmason@kudzu.us,
	kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
	kishon@ti.com, lorenzo.pieralisi@arm.com, ntb@lists.linux.dev,
	lznuaa@gmail.com, imx@lists.linux.dev,
	manivannan.sadhasivam@linaro.org
Subject: Re: [PATCH v11 0/6] PCI EP driver support MSI doorbell from host
Date: Wed, 28 Sep 2022 09:33:47 -0400	[thread overview]
Message-ID: <86mtaj7hdw.wl-maz@kernel.org> (raw)
In-Reply-To: <20220922161246.20586-1-Frank.Li@nxp.com>

On Thu, 22 Sep 2022 12:12:40 -0400,
Frank Li <Frank.Li@nxp.com> wrote:
> 
> 
> 
>                   ┌───────┐          ┌──────────┐
>                   │       │          │          │
> ┌─────────────┐   │       │          │ PCI Host │
> │ MSI         │◄┐ │       │          │          │
> │ Controller  │ │ │       │          │          │
> └─────────────┘ └─┼───────┼──────────┼─Bar0     │
>                   │ PCI   │          │ Bar1     │
>                   │ Func  │          │ Bar2     │
>                   │       │          │ Bar3     │
>                   │       │          │ Bar4     │
>                   │       ├─────────►│          │
>                   └───────┘          └──────────┘
> 
> Many PCI controllers provided Endpoint functions.
> Generally PCI endpoint is hardware, which is not running a rich OS,
> like linux.
> 
> But Linux also supports endpoint functions.  PCI Host write BAR<n> space
> like write to memory. The EP side can't know memory changed by the Host
> driver. 
> 
> PCI Spec has not defined a standard method to do that.  Only define
> MSI(x) to let EP notified RC status change. 

[...]

FWIW, I have queued the first 4 patches of this series into -next. If
there is a need for these patches to be pulled by another subsystem, I
have pushed out a stable branch at [1].

Thanks,

	M.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/log/?h=irq/fsl-mu-msi

-- 
Without deviation from the norm, progress is not possible.

  parent reply	other threads:[~2022-09-28 13:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 16:12 [PATCH v11 0/6] PCI EP driver support MSI doorbell from host Frank Li
2022-09-22 16:12 ` [PATCH v12 1/6] platform-msi: export symbol platform_msi_create_irq_domain() Frank Li
2022-09-22 16:12 ` [PATCH v12 2/6] irqchip: allow pass down .pm field at IRQCHIP_PLATFORM_DRIVER_END Frank Li
2022-09-22 16:12 ` [PATCH v12 3/6] irqchip: Add IMX MU MSI controller driver Frank Li
2022-09-22 16:12 ` [PATCH v12 4/6] dt-bindings: irqchip: imx mu work as msi controller Frank Li
2022-09-22 16:12 ` [PATCH v12 5/6] PCI: endpoint: pci-epf-vntb: Clean up Frank Li
2022-10-06 14:25   ` Frank Li
2022-10-07  8:43     ` Lorenzo Pieralisi
2022-09-22 16:12 ` [PATCH v12 6/6] PCI: endpoint: Add vNTB MSI support Frank Li
2022-10-07  9:15   ` Lorenzo Pieralisi
2022-10-07 14:54     ` [EXT] " Frank Li
2022-09-28 13:33 ` Marc Zyngier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-09-19 15:40 [PATCH v11 0/6] PCI EP driver support MSI doorbell from host Frank Li

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=86mtaj7hdw.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=aisheng.dong@nxp.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=jdmason@kudzu.us \
    --cc=kernel@pengutronix.de \
    --cc=kishon@ti.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=kw@linux.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=lznuaa@gmail.com \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=ntb@lists.linux.dev \
    --cc=peng.fan@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=tglx@linutronix.de \
    /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).