Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: Niklas Cassel <cassel@kernel.org>
Cc: "Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Kishon Vijay Abraham I" <kishon@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	imx@lists.linux.dev, dlemoal@kernel.org, maz@kernel.org,
	tglx@linutronix.de, jdmason@kudzu.us
Subject: Re: [PATCH v4 0/5] PCI: EP: Add RC-to-EP doorbell with platform MSI controller
Date: Wed, 6 Nov 2024 12:13:09 -0500	[thread overview]
Message-ID: <ZyujpT+4bd7TwbcM@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <Zys4qs-uHvISaaPB@ryzen>

On Wed, Nov 06, 2024 at 10:36:42AM +0100, Niklas Cassel wrote:
> On Wed, Nov 06, 2024 at 10:15:27AM +0100, Niklas Cassel wrote:
> >
> > I do get a domain, but I do not get any IRQ on the EP side when the RC side is
> > writing the doorbell (as part of pcitest -B),
> >
> > [    7.978984] pci_epc_alloc_doorbell: num_db: 1
> > [    7.979545] pci_epf_test_bind: doorbell_addr: 0x40
> > [    7.979978] pci_epf_test_bind: doorbell_data: 0x0
> > [    7.980397] pci_epf_test_bind: doorbell_bar: 0x1
> > [   21.114613] pci_epf_enable_doorbell db_bar: 1
> > [   21.115001] pci_epf_enable_doorbell: doorbell_addr: 0xfe650040
> > [   21.115512] pci_epf_enable_doorbell: phys_addr: 0xfe650000
> > [   21.115994] pci_epf_enable_doorbell: success
> >
> > # cat /proc/interrupts | grep epc
> > 117:          0          0          0          0          0          0          0          0  ITS-pMSI-a40000000.pcie-ep   0 Edge      pci-epc-doorbell0
> >
> > Even if I try to write the doorbell manually from EP side using devmem:
> >
> > # devmem 0xfe670040 32 1
>
> Sorry, this should of course have been:
> # devmem 0xfe650040 32 1

Thank you test it. You can't write it at EP side. ITS identify the bus
master. master ID (streamid) of CPU is the diffference with PCI master's
ID (streamid). You set msi-parent = <&its0 0x0000>, not sure if 0x0000 is
validate stream.

You have to run at RC side, "devmem (Bar1+0x40) 32 0".  So PCIe EP
controller can use EP streamid.

some system need special register to config stream id, you can refer host
side's settings.

Frank

>
> But the result is the name, no IRQ triggered on the EP side.
>
> (My command above was from testing "msi-parent = <&its0 0x0000>",
> rather than &its1, but that also didn't work when writing the
> corresponding "doorbell_addr" using e.g. devmem.)

<&its0 0x0000>,  second argument is your PCIe controller's stream ID. You
can ref RC side.

>
> Considering that the RC node is using &its1, that is probably
> also what should be used in the EP node when running the controller
> in EP mode instead of RC mode.

Generally,  RC node should use smmu-map, instead &its1. Or your PCI
controller direct use 16bit RID as streamid.

>
>
> Kind regards,
> Niklas

  reply	other threads:[~2024-11-06 17:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31 16:26 [PATCH v4 0/5] PCI: EP: Add RC-to-EP doorbell with platform MSI controller Frank Li
2024-10-31 16:27 ` [PATCH v4 1/5] PCI: endpoint: Add pci_epc_get_fn() API for customizable filtering Frank Li
2024-10-31 16:27 ` [PATCH v4 2/5] PCI: endpoint: Add RC-to-EP doorbell support using platform MSI controller Frank Li
2024-11-08  0:53   ` Krishna Chaitanya Chundru
2024-10-31 16:27 ` [PATCH v4 3/5] PCI: endpoint: pci-epf-test: Add doorbell test support Frank Li
2024-11-07 21:52   ` Niklas Cassel
2024-11-07 22:44     ` Frank Li
2024-11-07 22:48       ` Niklas Cassel
2024-10-31 16:27 ` [PATCH v4 4/5] misc: pci_endpoint_test: Add doorbell test case Frank Li
2024-11-07 21:42   ` Niklas Cassel
2024-11-07 22:45     ` Frank Li
2024-10-31 16:27 ` [PATCH v4 5/5] tools: PCI: Add 'B' option for test doorbell Frank Li
2024-11-06  9:15 ` [PATCH v4 0/5] PCI: EP: Add RC-to-EP doorbell with platform MSI controller Niklas Cassel
2024-11-06  9:36   ` Niklas Cassel
2024-11-06 17:13     ` Frank Li [this message]
2024-11-06 23:57       ` Niklas Cassel
2024-11-07  0:41         ` Frank Li
2024-11-08  0:07           ` Niklas Cassel
2024-11-07  0:46         ` 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=ZyujpT+4bd7TwbcM@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=imx@lists.linux.dev \
    --cc=jdmason@kudzu.us \
    --cc=kishon@kernel.org \
    --cc=kw@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=maz@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