All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kishon Vijay Abraham I <kishon@ti.com>
To: Kishon Vijay Abraham I <kishon@ti.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Arnd Bergmann <arnd@arndb.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Bjorn Helgaas <bhelgaas@google.com>, <linux-pci@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: [PATCH 0/7] Improvements to pci_endpoint_test driver
Date: Mon, 30 Dec 2019 18:03:08 +0530	[thread overview]
Message-ID: <20191230123315.31037-1-kishon@ti.com> (raw)

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"
*) Always enable legacy interrupt.

Kishon Vijay Abraham I (7):
  misc: pci_endpoint_test: Avoid using module parameter to determine
    irqtype
  misc: pci_endpoint_test: Do not request or allocate IRQs in probe
  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
  misc: pci_endpoint_test: Enable legacy interrupt

 drivers/misc/pci_endpoint_test.c | 43 +++++++++++++++++++++++++-------
 include/uapi/linux/pcitest.h     |  1 +
 tools/pci/pcitest.c              | 16 +++++++++++-
 3 files changed, 50 insertions(+), 10 deletions(-)

-- 
2.17.1


             reply	other threads:[~2019-12-30 12:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-30 12:33 Kishon Vijay Abraham I [this message]
2019-12-30 12:33 ` [PATCH 1/7] misc: pci_endpoint_test: Avoid using module parameter to determine irqtype Kishon Vijay Abraham I
2019-12-30 12:33 ` [PATCH 2/7] misc: pci_endpoint_test: Do not request or allocate IRQs in probe Kishon Vijay Abraham I
2019-12-30 15:07   ` kbuild test robot
2019-12-30 15:07     ` kbuild test robot
2019-12-30 17:10   ` kbuild test robot
2019-12-30 17:10     ` kbuild test robot
2019-12-31  8:35     ` Kishon Vijay Abraham I
2019-12-31  8:35       ` Kishon Vijay Abraham I
2019-12-31 10:40       ` [kbuild-all] " Philip Li
2019-12-31 10:40         ` Philip Li
2019-12-30 12:33 ` [PATCH 3/7] misc: pci_endpoint_test: Add ioctl to clear IRQ Kishon Vijay Abraham I
2019-12-30 12:33 ` [PATCH 4/7] tools: PCI: Add 'e' " Kishon Vijay Abraham I
2019-12-30 12:33 ` [PATCH 5/7] misc: pci_endpoint_test: Fix to support > 10 pci-endpoint-test devices Kishon Vijay Abraham I
2019-12-30 12:33 ` [PATCH 6/7] misc: pci_endpoint_test: Use full pci-endpoint-test name in request irq Kishon Vijay Abraham I
2019-12-30 12:33 ` [PATCH 7/7] misc: pci_endpoint_test: Enable legacy interrupt Kishon Vijay Abraham I

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=20191230123315.31037-1-kishon@ti.com \
    --to=kishon@ti.com \
    --cc=arnd@arndb.de \
    --cc=bhelgaas@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.