From: Rob Herring <robh@kernel.org>
To: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
Grant.Likely@arm.com, linux-pci@vger.kernel.org,
Jeremy.Linton@arm.com, robh+dt@kernel.org, bhelgaas@google.com,
Robin.Murphy@arm.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] dt-bindings: Add external-facing PCIe port property
Date: Sat, 06 Apr 2019 01:06:36 -0500 [thread overview]
Message-ID: <5ca841ee.1c69fb81.1ba7b.707f@mx.google.com> (raw)
In-Reply-To: <20190402131548.41949-2-jean-philippe.brucker@arm.com>
On Tue, 2 Apr 2019 14:15:47 +0100, Jean-Philippe Brucker wrote:
> Provide a way for the firmware to tell the OS which devices are external
> to the machine and therefore untrusted. The property can describe for
> example Thunderbolt and other user-accessible ports, which should always
> have the strongest IOMMU protection.
>
> Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
> ---
> Documentation/devicetree/bindings/pci/pci.txt | 50 +++++++++++++++++++
> 1 file changed, 50 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-04-06 6:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 13:15 [PATCH v2 0/2] PCI: Describe external-facing ports in device tree Jean-Philippe Brucker
2019-04-02 13:15 ` [PATCH v2 1/2] dt-bindings: Add external-facing PCIe port property Jean-Philippe Brucker
2019-04-05 21:39 ` Robin Murphy
2019-04-06 6:06 ` Rob Herring [this message]
2019-04-02 13:15 ` [PATCH v2 2/2] PCI: OF: Support external-facing property Jean-Philippe Brucker
2019-04-05 21:18 ` Bjorn Helgaas
2019-04-05 21:28 ` Robin Murphy
2019-04-06 19:42 ` [PATCH v2 0/2] PCI: Describe external-facing ports in device tree Grant Likely
2019-04-09 23:11 ` Bjorn Helgaas
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=5ca841ee.1c69fb81.1ba7b.707f@mx.google.com \
--to=robh@kernel.org \
--cc=Grant.Likely@arm.com \
--cc=Jeremy.Linton@arm.com \
--cc=Robin.Murphy@arm.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=jean-philippe.brucker@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).