From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 11/13] dtb: amd: Add PCIe SMMU device tree node
Date: Thu, 28 Jan 2016 14:27:52 +0000 [thread overview]
Message-ID: <20160128142751.GA775@arm.com> (raw)
In-Reply-To: <6645680.g0j8d12m6d@wuerfel>
On Thu, Jan 28, 2016 at 03:17:33PM +0100, Arnd Bergmann wrote:
> On Thursday 28 January 2016 12:20:58 Robin Murphy wrote:
> > >
> > > Will, Robin, thoughts?
> >
> > Any IDs specified here would only apply to DMA by the "platform device"
> > side of the host controller itself (as would an equivalent "iommus"
> > property on pcie0 once I finish the SMMUv2 generic binding support I'm
> > working on). In terms of PCI devices, the "mmu-masters" property is
> > overloaded such that only its existence matters, to identify that there
> > _is_ a relationship between the SMMU and the PCI bus(es) behind that
> > host controller.
>
> I wasn't aware that this was actually still specified. I had hoped
> we were getting rid of mmu-masters before anyone actually started
> using it, but now I see it in ns2.dtsi and fsl-ls2080a.dtsi.
>
> Does anyone know what happened to the plan to use the iommu DT binding
> for the ARM SMMU instead? Do we now have to support both ways indefinitely?
We always did -- Seattle used the mmu-masters binding before the generic
binding even existed. Robin has been working on patches to get of_xlate
up and running, but it got held up by Laurent's series which didn't end
up going anywhere.
Will
next prev parent reply other threads:[~2016-01-28 14:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 21:11 [PATCH 00/13] dtb: amd: Miscelleneous Updates for AMD Seattle DTS Suravee Suthikulpanit
2016-01-27 21:11 ` [PATCH 01/13] MAINTAINERS: Adding Maintainers for AMD Seattle Device Tree Suravee Suthikulpanit
2016-01-28 4:49 ` Martin Michlmayr
2016-01-27 21:11 ` [PATCH 02/13] dtb: amd: Fix GICv2 hypervisor and virtual interface sizes Suravee Suthikulpanit
2016-01-27 21:11 ` [PATCH 03/13] dtb: amd: Fix DMA ranges in device tree Suravee Suthikulpanit
2016-01-27 21:11 ` [PATCH 04/13] dtb: amd: Fix typo in SPI device nodes Suravee Suthikulpanit
2016-01-27 21:11 ` [PATCH 05/13] dtb: amd: Misc changes for I2C " Suravee Suthikulpanit
2016-01-27 21:11 ` [PATCH 06/13] dtb: amd: Misc changes for SATA device tree nodes Suravee Suthikulpanit
2016-01-27 21:11 ` [PATCH 07/13] dtb: amd: Misc changes for GPIO devices Suravee Suthikulpanit
2016-01-27 21:11 ` [PATCH 08/13] dtb: amd: Add PERF CCN-504 device tree node Suravee Suthikulpanit
2016-01-27 21:11 ` [PATCH 09/13] dtb: amd: Add KCS " Suravee Suthikulpanit
2016-01-27 21:11 ` [PATCH 10/13] dtb: amd: Add AMD XGBE device tree file Suravee Suthikulpanit
2016-01-27 21:11 ` [PATCH 11/13] dtb: amd: Add PCIe SMMU device tree node Suravee Suthikulpanit
2016-01-28 11:14 ` Mark Rutland
2016-01-28 11:17 ` Will Deacon
2016-01-28 11:18 ` Mark Rutland
2016-01-28 11:19 ` Will Deacon
2016-01-28 12:20 ` Robin Murphy
2016-01-28 14:17 ` Arnd Bergmann
2016-01-28 14:27 ` Will Deacon [this message]
2016-03-30 15:37 ` Eric Auger
2016-03-30 15:45 ` Will Deacon
2016-03-30 15:57 ` Eric Auger
2016-03-30 17:24 ` Will Deacon
2016-03-31 7:39 ` Eric Auger
2016-03-31 17:34 ` Will Deacon
2016-01-27 21:12 ` [PATCH 12/13] dtb: amd: Add support for new AMD Overdrive boards Suravee Suthikulpanit
2016-01-27 21:12 ` [PATCH 13/13] dtb: amd: Add support for AMD/Linaro 96Boards Enterprise Edition Server board Suravee Suthikulpanit
2016-01-28 21:39 ` [PATCH 00/13] dtb: amd: Miscelleneous Updates for AMD Seattle DTS Olof Johansson
2016-01-28 22:20 ` Suravee Suthikulanit
2016-01-29 2:43 ` Olof Johansson
2016-01-30 0:02 ` Suravee Suthikulanit
2016-01-30 1:02 ` Frank Rowand
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=20160128142751.GA775@arm.com \
--to=will.deacon@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).