linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Generic PCI MSI + IOMMU topology bindings
Date: Thu, 23 Jul 2015 17:52:42 +0100	[thread overview]
Message-ID: <1437670365-20704-1-git-send-email-mark.rutland@arm.com> (raw)

Hi all,

Currently we have no generic/standard mechanisms for describing the
relationship between PCI root complexes and other components which may be
required to make them usable, specifically IOMMUs and MSI controllers.

There is an existing binding for IOMMUs, and there is a de-facto standard for
referring to MSI controllers, but the generic portion of these can only
describe a relationship with a root complex as opposed to a device under a root
complex. This falls apart where IOMMUs and MSI controllers may distinguish
individual devices based on non-probeable information.

This series adds a generic "glue" bindings for describing the relationship
between root complexes, IOMMUs, and MSI controllers. The existing de-facto
binding for MSI controllers is formalised, along with a (backwards compatible)
extension necessary for describing contemporary MSI controllers which make use
of (non-probeable) sideband data.

Thanks,
Mark.

Mark Rutland (3):
  Docs: dt: add generic MSI bindings
  Docs: dt: Add PCI MSI map bindings
  Docs: dt: add PCI IOMMU map bindings

 .../bindings/interrupt-controller/msi.txt          | 135 +++++++++++++
 .../devicetree/bindings/pci/pci-iommu.txt          | 171 ++++++++++++++++
 Documentation/devicetree/bindings/pci/pci-msi.txt  | 220 +++++++++++++++++++++
 3 files changed, 526 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/interrupt-controller/msi.txt
 create mode 100644 Documentation/devicetree/bindings/pci/pci-iommu.txt
 create mode 100644 Documentation/devicetree/bindings/pci/pci-msi.txt

-- 
1.9.1

             reply	other threads:[~2015-07-23 16:52 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 16:52 Mark Rutland [this message]
2015-07-23 16:52 ` [PATCH 1/3] Docs: dt: add generic MSI bindings Mark Rutland
2015-07-23 18:26   ` David Daney
2015-07-24  7:04     ` Marc Zyngier
2015-07-27  8:02   ` Marc Zyngier
2015-07-27  9:46     ` Mark Rutland
2015-08-03 10:44       ` Marc Zyngier
2015-08-05 16:51   ` Mark Rutland
2015-08-06  7:56     ` Marc Zyngier
2015-08-24 10:17     ` Mark Rutland
2015-08-24 13:37       ` Rob Herring
2015-08-24 13:47         ` Mark Rutland
2015-07-23 16:52 ` [PATCH 2/3] Docs: dt: Add PCI MSI map bindings Mark Rutland
2015-07-24 23:27   ` Chalamarla, Tirumalesh
2015-07-27  9:16     ` Mark Rutland
2015-07-27  8:16   ` Marc Zyngier
2015-09-04 22:33     ` David Daney
2015-09-07 18:05       ` Mark Rutland
2015-09-08 15:53         ` Stuart Yoder
2015-09-07 17:56     ` Mark Rutland
2015-08-05 16:39   ` Varun Sethi
2015-08-06 17:38     ` Mark Rutland
2015-08-08 15:06       ` Varun Sethi
     [not found]   ` <CALRxmdA32xiSX7DDKAJPLR8=bh_9j-6MN124u4KjYGRT8bAKNg@mail.gmail.com>
2015-08-05 19:53     ` Stuart Yoder
2015-08-06 18:14       ` Mark Rutland
2015-08-06 19:46         ` Stuart Yoder
2015-07-23 16:52 ` [PATCH 3/3] Docs: dt: add PCI IOMMU " Mark Rutland
2015-07-24 12:23   ` Robin Murphy
2015-07-24 13:26     ` Mark Rutland

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=1437670365-20704-1-git-send-email-mark.rutland@arm.com \
    --to=mark.rutland@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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).