From: Shawn Lin <shawn.lin@rock-chips.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, Shawn Lin <shawn.lin@rock-chips.com>
Subject: [PATCH v2 0/9] Add new helper to allocate IRQ domain for host drivers
Date: Sat, 28 Apr 2018 09:48:22 +0800 [thread overview]
Message-ID: <1524880102-100856-1-git-send-email-shawn.lin@rock-chips.com> (raw)
Hi Bjorn and Lorenzo,
PCI drivers use highly similar code block to allocate IRQ domain which
leads to code duplication than expected. This patchset adds a new helper,
pci_alloc_intx_irqd(), to avoid that as much as possible. Just leave
pcie-rockchip out now as it's under re-construct and will add incremental
patch for it if this series looks ok and the pcie-rockchip ongoing patches
got merge.
Changes in v2:
- fix typo and move the code to C file.
Shawn Lin (9):
PCI: Add pci_alloc_intx_irqd() for allocating IRQ domain
PCI: dra7xx: Use pci_alloc_intx_irqd() helper to simplify the code
PCI: keystone-dw: Use pci_alloc_intx_irqd() helper to get irq domain
for INTx
PCI: aardvark: Use pci_alloc_intx_irqd() helper to get irq domain for
INTx
PCI: faraday: Use pci_alloc_intx_irqd() helper to get irq domain for
INTx
PCI: altera: Use pci_alloc_intx_irqd() helper to get irq domain for
INTx
PCI: mediatek: Use pci_alloc_intx_irqd() helper to get irq domain for
INTx
PCI: xilinx-nwl: Use pci_alloc_intx_irqd() helper to get irq domain
for INTx
PCI: xilinx: Use pci_alloc_intx_irqd() helper to get irq domain for
INTx
drivers/pci/dwc/pci-dra7xx.c | 41 ++---------------------
drivers/pci/dwc/pci-keystone-dw.c | 12 +++----
drivers/pci/host/pci-aardvark.c | 24 +++-----------
drivers/pci/host/pci-ftpci100.c | 15 +++------
drivers/pci/host/pcie-altera.c | 38 +++------------------
drivers/pci/host/pcie-mediatek.c | 29 ++--------------
drivers/pci/host/pcie-xilinx-nwl.c | 21 +++---------
drivers/pci/host/pcie-xilinx.c | 43 ++----------------------
drivers/pci/irq.c | 68 ++++++++++++++++++++++++++++++++++++++
include/linux/pci.h | 10 ++++++
10 files changed, 108 insertions(+), 193 deletions(-)
--
1.9.1
next reply other threads:[~2018-04-28 1:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 1:48 Shawn Lin [this message]
2018-04-28 1:48 ` [PATCH v2 1/9] PCI: Add pci_alloc_intx_irqd() for allocating IRQ domain Shawn Lin
2018-04-28 17:59 ` Christoph Hellwig
2018-04-29 21:56 ` kbuild test robot
2018-04-30 0:23 ` kbuild test robot
2018-04-28 1:49 ` [PATCH v2 2/9] PCI: dra7xx: Use pci_alloc_intx_irqd() helper to simplify the code Shawn Lin
2018-04-28 1:49 ` [PATCH v2 3/9] PCI: keystone-dw: Use pci_alloc_intx_irqd() helper to get irq domain for INTx Shawn Lin
2018-04-28 1:49 ` [PATCH v2 4/9] PCI: aardvark: " Shawn Lin
2018-04-28 1:49 ` [PATCH v2 5/9] PCI: faraday: " Shawn Lin
2018-04-28 1:50 ` [PATCH v2 6/9] PCI: altera: " Shawn Lin
2018-04-28 1:50 ` [PATCH v2 7/9] PCI: mediatek: " Shawn Lin
2018-04-28 1:50 ` [PATCH v2 8/9] PCI: xilinx-nwl: " Shawn Lin
2018-04-28 1:50 ` [PATCH v2 9/9] PCI: xilinx: " Shawn Lin
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=1524880102-100856-1-git-send-email-shawn.lin@rock-chips.com \
--to=shawn.lin@rock-chips.com \
--cc=bhelgaas@google.com \
--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 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).