From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] devicetree: Add generic IOMMU device tree bindings
Date: Wed, 30 Jul 2014 15:30:37 +0100 [thread overview]
Message-ID: <20140730143037.GD8989@arm.com> (raw)
In-Reply-To: <20140730132348.GM29590@ulmo>
On Wed, Jul 30, 2014 at 02:23:50PM +0100, Thierry Reding wrote:
> On Wed, Jul 30, 2014 at 12:04:25PM +0100, Will Deacon wrote:
> > On Fri, Jul 04, 2014 at 04:29:17PM +0100, Thierry Reding wrote:
> > > From: Thierry Reding <treding@nvidia.com>
> > >
> > > This commit introduces a generic device tree binding for IOMMU devices.
> > > Only a very minimal subset is described here, but it is enough to cover
> > > the requirements of both the Exynos System MMU and Tegra SMMU as
> > > discussed here:
> > >
> > > https://lkml.org/lkml/2014/4/27/346
> > >
> > > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > > ---
> > > Changes in v4:
> > > - clarify that disabling an IOMMU DT node may not disable translation
> > > - be more explicit that examples are only examples
> > > - add multi-ID master example
> > >
> > > Changes in v3:
> > > - use #iommu-cells instead of #address-cells/#size-cells
> > > - drop optional iommu-names property
> > >
> > > Changes in v2:
> > > - add notes about "dma-ranges" property (drop note from commit message)
> > > - document priorities of "iommus" property vs. "dma-ranges" property
> > > - drop #iommu-cells in favour of #address-cells and #size-cells
> > > - remove multiple-master device example
> > >
> > > Documentation/devicetree/bindings/iommu/iommu.txt | 172 ++++++++++++++++++++++
> > > 1 file changed, 172 insertions(+)
> > > create mode 100644 Documentation/devicetree/bindings/iommu/iommu.txt
> >
> > I'm concerned that this patch hasn't been picked up for 3.17 (I can't see it
> > in -next). If we want to move the ARM SMMU driver over to this new binding,
> > we can't keep dragging our feet for much longer as I *really* don't plan to
> > support two bindings in parallel (one is complicated enough already).
> >
> > Any chance we can see this merged, please?
>
> I think there weren't any comments left for me to address and I've
> mostly been waiting for Joerg to pick it up.
>
> Joerg, can you take this through the iommu tree for 3.17? Will acked
> this, but perhaps you were waiting for an ACK from the device tree
> bindings maintainers?
Rob, Mark: can one or both of you take a look at this please?
Cheers,
Will
next prev parent reply other threads:[~2014-07-30 14:30 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 15:29 [PATCH v4] devicetree: Add generic IOMMU device tree bindings Thierry Reding
2014-07-09 13:40 ` Will Deacon
2014-07-09 14:21 ` Thierry Reding
2014-07-09 18:10 ` Will Deacon
2014-07-10 9:49 ` Thierry Reding
2014-07-10 10:23 ` Will Deacon
2014-07-10 10:57 ` Thierry Reding
2014-07-10 12:38 ` Will Deacon
2014-07-11 20:55 ` Rob Clark
2014-07-12 9:39 ` Will Deacon
2014-07-12 11:26 ` Rob Clark
2014-07-12 12:22 ` Arnd Bergmann
2014-07-12 12:57 ` Rob Clark
2014-07-13 9:43 ` Will Deacon
2014-07-13 11:43 ` Rob Clark
2014-07-16 1:25 ` Olav Haugan
2014-07-16 10:10 ` Will Deacon
2014-07-16 20:24 ` Rob Clark
2014-07-14 6:44 ` Thierry Reding
2014-07-14 10:08 ` Will Deacon
2014-07-14 6:24 ` Thierry Reding
2014-07-14 10:13 ` Rob Clark
2014-07-14 6:15 ` Thierry Reding
2014-07-30 11:04 ` Will Deacon
2014-07-30 13:23 ` Thierry Reding
2014-07-30 13:33 ` Joerg Roedel
2014-07-30 17:37 ` Olof Johansson
2014-07-30 14:30 ` Will Deacon [this message]
2014-07-30 18:08 ` Rob Herring
2014-07-30 20:11 ` Arnd Bergmann
2014-07-30 15:26 ` Mark Rutland
2014-07-30 17:35 ` Olof Johansson
2014-07-30 18:18 ` Mark Rutland
2014-07-31 10:09 ` Thierry Reding
2014-07-31 10:50 ` Mark Rutland
2014-07-31 11:14 ` Thierry Reding
2014-07-31 9:51 ` Thierry Reding
2014-07-31 8:39 ` Thierry Reding
2014-07-31 9:22 ` Mark Rutland
2014-07-31 10:18 ` Thierry Reding
2014-07-31 10:23 ` Joerg Roedel
2014-07-31 10:46 ` Thierry Reding
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=20140730143037.GD8989@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).