From: Frank Li <Frank.li@nxp.com>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: tglx@linutronix.de, aisheng.dong@nxp.com, bhelgaas@google.com,
devicetree@vger.kernel.org, festevam@gmail.com,
imx@lists.linux.dev, jdmason@kudzu.us, kernel@pengutronix.de,
kishon@ti.com, krzysztof.kozlowski+dt@linaro.org, kw@linux.com,
linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
lorenzo.pieralisi@arm.com, lpieralisi@kernel.org, maz@kernel.org,
ntb@lists.linux.dev, peng.fan@nxp.com, robh+dt@kernel.org,
s.hauer@pengutronix.de, shawnguo@kernel.org
Subject: Re: [PATCH 1/3] PCI: endpoint: Add RC-to-EP doorbell support using platform MSI controller
Date: Wed, 6 Sep 2023 11:36:25 -0400 [thread overview]
Message-ID: <ZPiceT2SidayOwDk@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20230906152704.GD5930@thinkpad>
On Wed, Sep 06, 2023 at 08:57:04PM +0530, Manivannan Sadhasivam wrote:
> On Wed, Sep 06, 2023 at 11:00:12AM -0400, Frank Li wrote:
> > On Wed, Sep 06, 2023 at 08:22:27PM +0530, Manivannan Sadhasivam wrote:
> > > > >
> > > > > Can't you assign it in the EPF driver itself? I do not want any OF reference in
> > > > > the EPF core since it has no OF support.
> > > >
> > > > If that, Each EPF driver need do duplicate work.
> > > >
> > >
> > > Yes, and that's how it should be. EPF core has no job in supplying the of_node.
> > > It is the responsibility of the EPF drivers as they depend on OF for platform
> > > support.
> >
> > EPF driver still not depend on OF. such pci-epf-test, which was probed by
> > configfs.
> >
>
> Hmm, yeah. Then it should be part of the EPC driver.
>
> Sorry for the confusion.
EPC can't get epf->msg data. It is too long time. I can't remember the
detail.
Let try to move to epc again.
>
> - Mani
>
> > Frank
> >
> > >
> > > - Mani
> > >
> > > > IMS will support per-device MSI domain, then we can implement customized
> > > > MSI irq allocated. But so far, it is simplest solution, we can update it
> > > > after IMS implementation at kernel. Only one place need be changed.
> > > >
> > > மணிவண்ணன் சதாசிவம்
>
> --
> மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2023-09-06 15:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 20:34 [PATCH 0/3] Add RC-to-EP doorbell with platform MSI controller Frank Li
2023-04-26 20:34 ` [PATCH 1/3] PCI: endpoint: Add RC-to-EP doorbell support using " Frank Li
2023-09-02 4:52 ` Manivannan Sadhasivam
2023-09-02 4:53 ` Manivannan Sadhasivam
2023-09-06 4:24 ` Frank Li
2023-09-06 12:26 ` Manivannan Sadhasivam
2023-09-06 14:33 ` Frank Li
2023-09-06 14:52 ` Manivannan Sadhasivam
2023-09-06 15:00 ` Frank Li
2023-09-06 15:27 ` Manivannan Sadhasivam
2023-09-06 15:36 ` Frank Li [this message]
2023-04-26 20:34 ` [PATCH 2/3] misc: pci_endpoint_test: Add doorbell test case Frank Li
2023-09-02 5:11 ` Manivannan Sadhasivam
2023-04-26 20:34 ` [PATCH 3/3] tools: PCI: Add 'B' option for test doorbell Frank Li
2023-05-12 14:45 ` [PATCH 0/3] Add RC-to-EP doorbell with platform MSI controller Frank Li
2023-06-12 16:17 ` Frank Li
2023-07-17 14:06 ` Frank Li
2023-08-24 19:01 ` Frank Li
2023-08-25 8:34 ` Manivannan Sadhasivam
2023-08-30 7:36 ` Li Chen
2023-08-30 18:27 ` 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=ZPiceT2SidayOwDk@lizhi-Precision-Tower-5810 \
--to=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=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=maz@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).