Hi Arnd, > -----Original Message----- > From: Arnd Bergmann [mailto:arnd@xxxxxxxx] > Sent: Monday, September 15, 2014 8:08 AM > To: Sethi Varun-B16395 > Cc: devicetree@xxxxxxxxxxxxxxx; iommu@xxxxxxxxxxxxxxxxxxxxxxxxxx; > thierry.reding@xxxxxxxxx; Mark.Rutland@xxxxxxx; will.deacon@xxxxxxx; > hdoyu@xxxxxxxxxx; swarren@xxxxxxxxxx; robh+dt@xxxxxxxxxx; linux-arm- > kernel@xxxxxxxxxxxxxxxxxxx; Yoder Stuart-B08248 > Subject: Re: [RFC][PATCH] devicetree: Add master-id-bits property to the > iommu device > > On Sunday 14 September 2014, Varun Sethi wrote: > > "master-id-bits" property added to the IOMMU device node. This > > property can be used by the IOMMU driver to match relevan bits in the > > master id expressed by a DMA master. > > > > This can be used to mask out certain bits that get added to the device > > master id due to IOMMU topology. For example, in case of MMU-500 the > > TBUID gets appended to the master id. This prevents sharing of a > > stream ID, amongst devices which are connected to different TBUs. > > > > Signed-off-by: Varun Sethi <Varun.Sethi@xxxxxxxxxxxxx> > > This seems rather specific to MMU-500. I don't think that most IOMMUs would > use the term 'master ID', 'stream ID' or even the general concept, and you > don't expand the acronym 'TBU'. I've seen many IOMMUs and I don't even > know what that means. TBU refers to the translation buffer unit, which is responsible for caching page translations. In case of translation miss in the cache, translation request is forwarded to the TCU (Translation control unit). The master id forwarded to TCU would also contain the TBU ID. Using the master-id-bits property we can mask out the additional TBU bits at the TCU. This is a cause of concern when we want to share master id for devices which are connected to different TBUs. We have a hot pluggable bus architecture, where a device group can have multiple devices connected to different TBUs. So, we need a mechanism to mask out additional TBIU bits. > > Why do you think this is something that is needed to be known at the global > level, rather than a property for some individual drivers? > In case of Freescale Layerscape SOCs, number of bits used for defining a stream id are specific to a given platform. Are you suggesting that this property should be added to the master device node, rather than the iommu node? -Varun -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
