From: Niklas Cassel <cassel@kernel.org>
To: bhelgaas@google.com, kw@linux.com, manivannan.sadhasivam@linaro.org
Cc: linux-pci@vger.kernel.org, Damien Le Moal <dlemoal@kernel.org>,
Kunihiko Hayashi <hayashi.kunihiko@socionext.com>,
Niklas Cassel <cassel@kernel.org>
Subject: [PATCH 0/7] pci_endpoint_test: Add support for PCITEST_IRQ_TYPE_AUTO
Date: Mon, 10 Mar 2025 12:10:17 +0100 [thread overview]
Message-ID: <20250310111016.859445-9-cassel@kernel.org> (raw)
Hello all,
For the PCITEST_WRITE, PCITEST_READ, and PCITEST_COPY test cases,
tools/testing/selftests/pci_endpoint/pci_endpoint_test.c unconditionally
uses MSIs, even for EPC drivers that do not support MSI.
(E.g. an EPC could support only INTx, or only MSI-X.)
Thus, improve tools/testing/selftests/pci_endpoint/pci_endpoint_test.c to
use any supported IRQ type (by introducing a new IRQ type
PCITEST_IRQ_TYPE_AUTO).
Note that it is only the PCITEST_WRITE, PCITEST_READ, and PCITEST_COPY test
cases that will use this new IRQ type. (PCITEST_MSI, PCITEST_MSIX, and
PCITEST_LEGACY_IRQ actually test a specific IRQ type, so these test cases
must still use a specific IRQ type.)
Kind regards,
Niklas
Niklas Cassel (7):
PCI: endpoint: pcitest: Add IRQ_TYPE_* defines to UAPI header
misc: pci_endpoint_test: Use IRQ_TYPE_* defines from UAPI header
selftests: pci_endpoint: Use IRQ_TYPE_* defines from UAPI header
PCI: endpoint: Add intx_capable to epc_features
PCI: dw-rockchip: EP mode cannot raise INTx interrupts
PCI: endpoint: pci-epf-test: Expose supported IRQ types in CAPS
register
misc: pci_endpoint_test: Add support for PCITEST_IRQ_TYPE_AUTO
drivers/misc/pci_endpoint_test.c | 69 +++++++++++--------
drivers/pci/controller/dwc/pcie-dw-rockchip.c | 2 +
drivers/pci/endpoint/functions/pci-epf-test.c | 12 ++++
include/linux/pci-epc.h | 1 +
include/uapi/linux/pcitest.h | 6 ++
.../pci_endpoint/pci_endpoint_test.c | 24 +++----
6 files changed, 75 insertions(+), 39 deletions(-)
--
2.48.1
next reply other threads:[~2025-03-10 11:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 11:10 Niklas Cassel [this message]
2025-03-10 11:10 ` [PATCH 1/7] PCI: endpoint: pcitest: Add IRQ_TYPE_* defines to UAPI header Niklas Cassel
2025-03-10 11:10 ` [PATCH 2/7] misc: pci_endpoint_test: Use IRQ_TYPE_* defines from " Niklas Cassel
2025-03-10 11:10 ` [PATCH 3/7] selftests: pci_endpoint: " Niklas Cassel
2025-03-10 11:10 ` [PATCH 4/7] PCI: endpoint: Add intx_capable to epc_features Niklas Cassel
2025-03-21 21:50 ` Bjorn Helgaas
2025-03-21 21:55 ` Niklas Cassel
2025-03-21 22:42 ` Bjorn Helgaas
2025-03-26 6:25 ` Krzysztof Wilczyński
2025-03-10 11:10 ` [PATCH 5/7] PCI: dw-rockchip: EP mode cannot raise INTx interrupts Niklas Cassel
2025-03-10 11:10 ` [PATCH 6/7] PCI: endpoint: pci-epf-test: Expose supported IRQ types in CAPS register Niklas Cassel
2025-03-10 11:10 ` [PATCH 7/7] misc: pci_endpoint_test: Add support for PCITEST_IRQ_TYPE_AUTO Niklas Cassel
2025-03-14 12:45 ` Manivannan Sadhasivam
2025-03-14 17:25 ` Niklas Cassel
2025-03-18 8:56 ` Manivannan Sadhasivam
2025-03-18 9:45 ` Niklas Cassel
2025-03-18 10:38 ` Niklas Cassel
2025-03-10 13:47 ` [PATCH 0/7] " Krzysztof Wilczyński
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=20250310111016.859445-9-cassel@kernel.org \
--to=cassel@kernel.org \
--cc=bhelgaas@google.com \
--cc=dlemoal@kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
/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