From: <suravee.suthikulpanit@amd.com>
To: <bhelgaas@google.com>
Cc: <liviu.dudau@arm.com>, <lorenzo.pieralisi@arm.com>,
<will.deacon@arm.com>, <linux-pci@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
Subject: [PATCH V2 0/2] PCI: generic: Assiging msi-controller to PCI hostbridge
Date: Tue, 11 Nov 2014 13:17:32 -0600 [thread overview]
Message-ID: <1415733454-24322-1-git-send-email-suravee.suthikulpanit@amd.com> (raw)
From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
This patch set introduces a new callback function to allow PCI host drivers
to specify MSI controller to be used for the child buses / devices.
This is reabased from:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git pci/host-generic
Changes from V1:
- Adding "msi-parent" device tree binding in documentation.
- Rebase the patch to get rid of artifacts from other precursor patch
accidently applied to the developement tree. This should now apply cleanly
to the pci/host-generic branch.
Suravee Suthikulpanit (2):
PCI: Add new pci_ops for setting MSI parent for PCI bus
PCI: generic: Add set_msi_parent callback
Documentation/devicetree/bindings/pci/host-generic-pci.txt | 3 +++
drivers/pci/host/pci-host-generic.c | 13 +++++++++++++
drivers/pci/probe.c | 3 +++
include/linux/pci.h | 1 +
4 files changed, 20 insertions(+)
--
1.9.3
next reply other threads:[~2014-11-11 19:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 19:17 suravee.suthikulpanit [this message]
2014-11-11 19:17 ` [PATCH V2 1/2] PCI: Add new pci_ops for setting MSI parent for PCI bus suravee.suthikulpanit
2014-11-11 19:17 ` [PATCH V2 2/2] PCI: generic: Add msi_parent DT binding suravee.suthikulpanit
2014-11-12 6:56 ` Srikanth Thokala
2014-11-12 7:09 ` Srikanth Thokala
2014-11-12 11:37 ` Suravee Suthikulpanit
2014-11-12 11:36 ` Suravee Suthikulpanit
2014-11-13 18:09 ` [PATCH V2 0/2] PCI: generic: Assiging msi-controller to PCI hostbridge Bjorn Helgaas
2014-11-14 1:19 ` Yijing Wang
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=1415733454-24322-1-git-send-email-suravee.suthikulpanit@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=bhelgaas@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=will.deacon@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
all inboxes | Powered by JetHome®