From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Andrew Murray <amurray@thegoodpenguin.co.uk>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] misc: Improvements to pci_endpoint_test driver
Date: Fri, 20 Mar 2020 09:52:04 +0000 [thread overview]
Message-ID: <20200320095204.GA21466@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <20200317100158.4692-1-kishon@ti.com>
On Tue, Mar 17, 2020 at 03:31:53PM +0530, Kishon Vijay Abraham I wrote:
> This series adds improvements and fixes to pci_endpoint_test driver
> mostly applicable when used with multi-function endpoint (or multiple
> endpoint instances using pci_epf_test).
>
> *) Using module parameter to determine irqtype would indicate all the
> pci_endpoint_test device have the same irqtype. Fix it here.
> *) Add ioctl to clear irq so that "cat /proc/interrupts" only lists
> the entries for the devices that is actually being used.
> *) Creating more than 10 pci-endpoint-test devices results in a kernel
> error.
> *) Use full pci-endpoint-test name in request irq so that it's easy to
> profile the interrupt details in "cat /proc/interrupts"
>
> Changes from v1:
> *) Removed a patch that references J721E device ID (That patch will
> be added as part of J721E support series)
> *) Removed a patch that always enable legacy interrupt. That should
> be handled by pci_alloc_irq_vectors()
>
> Kishon Vijay Abraham I (5):
> misc: pci_endpoint_test: Avoid using module parameter to determine
> irqtype
> misc: pci_endpoint_test: Add ioctl to clear IRQ
> tools: PCI: Add 'e' to clear IRQ
> misc: pci_endpoint_test: Fix to support > 10 pci-endpoint-test devices
> misc: pci_endpoint_test: Use full pci-endpoint-test name in request
> irq
>
> drivers/misc/pci_endpoint_test.c | 49 +++++++++++++++++++++++++-------
> include/uapi/linux/pcitest.h | 1 +
> tools/pci/pcitest.c | 16 ++++++++++-
> 3 files changed, 55 insertions(+), 11 deletions(-)
Applied to pci/endpoint for v5.7.
Thanks,
Lorenzo
prev parent reply other threads:[~2020-03-20 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 10:01 [PATCH v2 0/5] misc: Improvements to pci_endpoint_test driver Kishon Vijay Abraham I
2020-03-17 10:01 ` [PATCH v2 1/5] misc: pci_endpoint_test: Avoid using module parameter to determine irqtype Kishon Vijay Abraham I
2020-03-17 10:01 ` [PATCH v2 2/5] misc: pci_endpoint_test: Add ioctl to clear IRQ Kishon Vijay Abraham I
2020-03-17 10:01 ` [PATCH v2 3/5] tools: PCI: Add 'e' " Kishon Vijay Abraham I
2020-03-17 10:01 ` [PATCH v2 4/5] misc: pci_endpoint_test: Fix to support > 10 pci-endpoint-test devices Kishon Vijay Abraham I
2020-03-17 10:01 ` [PATCH v2 5/5] misc: pci_endpoint_test: Use full pci-endpoint-test name in request irq Kishon Vijay Abraham I
2020-03-20 9:52 ` Lorenzo Pieralisi [this message]
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=20200320095204.GA21466@e121166-lin.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=amurray@thegoodpenguin.co.uk \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavo.pimentel@synopsys.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).