From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: Report from 2013 ARM kernel summit
Date: Thu, 21 Nov 2013 11:00:24 +0000 [thread overview]
Message-ID: <20131121110024.GA8395@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <CAL_Jsq+AxEWhkOhxwAZ=+rpzDZ+yC1b3ZV541UhOu9kiwUhUdQ@mail.gmail.com>
On Wed, Nov 20, 2013 at 08:02:10PM +0000, Rob Herring wrote:
> On Wed, Nov 20, 2013 at 12:39 AM, Hiroshi Doyu <hdoyu@nvidia.com> wrote:
> > smmu_a: iommu at xxxxxxxx {
> > #iommu-cells = <2>;
> > ....
> > };
> >
> > smmu_b: iommu at xxxxxxxx {
> > #iommu-cells = <3>;
> > ....
> > };
> >
> > device_a {
> > iommus = <&smmu_a param1 param2>,
> > <&smmu_b param1 param2 param3>;
> > };
> >
> > This can describe the relation between a device and an iommu
> > independently. The number of params needed for each IOMMU can be
> > sepcified by #iommu-cells in its iommu entry.
> >
> > device_a <-> smmu_a, needs 2 params for a device
> > device_a <-> smmu_b, needs 3 params for a device
> >
> > For example, "smmu_a" can be an bus level global IOMMU where all child
> > devices can be an master of "smmu_a", and "smmu_b" is a local IOMMU
> > only for "device_a".
> >
> > "memory controller"---"smmu_a"---bus--+--"smmu_b"--"device_a"
> > |
> > |
> > +--"device_b"
>
> I think the above binding would be the correct way to describe things
> if you have 1 device connected to 2 IOMMUs (directly rather than
> chained). IIUC, that is something you have on tegra?
>
> For the topology above where you are chaining iommu's, I think
> something like this is more accurately describing the hierarchy:
>
> smmu_b: iommu at xxxxxxxx {
> #iommu-cells = <3>;
> iommus = <&smmu_a param1 param2>;
> ....
> };
> device_a {
> iommus = <&smmu_b param1 param2 param3>;
> };
>
> I remember discussing this with Will and seem to recall some issue
> with describing things this way. But looking at it now, I don't see
> what that was.
I think it was the usual issue with StreamID remastering. For example, if
you had a device going into two chained IOMMUs, you need a way to relate the
StreamIDs of the device to the remastered IDs coming out of the first SMMU.
Will
next prev parent reply other threads:[~2013-11-21 11:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 13:20 Report from 2013 ARM kernel summit Grant Likely
2013-11-11 9:47 ` Hiroshi Doyu
2013-11-15 7:06 ` Grant Likely
2013-11-19 9:40 ` Hiroshi Doyu
2013-11-19 17:35 ` Will Deacon
2013-11-19 20:45 ` Rob Herring
2013-11-20 6:39 ` Hiroshi Doyu
2013-11-20 20:02 ` Rob Herring
2013-11-20 20:22 ` Stephen Warren
2013-11-21 8:49 ` Hiroshi Doyu
2013-11-21 11:00 ` Will Deacon [this message]
2013-11-21 18:40 ` Stephen Warren
2013-11-25 18:03 ` Will Deacon
2013-11-20 10:31 ` Will Deacon
2013-11-20 13:53 ` Thierry Reding
2013-11-20 19:47 ` Rob Herring
2013-11-20 20:22 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2013-11-07 23:29 Grant Likely
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=20131121110024.GA8395@mudshark.cambridge.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).