On Mon, May 13, 2013 at 10:07:24AM +0100, Andreas Herrmann wrote:
On Tue, May 07, 2013 at 04:26:02PM -0400, Olav Haugan wrote:
I think you misunderstood me. I am talking about having for example 1
master with two (2) context banks so that StreamID 1 goes to CB0 and
StreamID 2 goes to CB1.
Hi Will,
On 4/24/2013 2:55 AM, Will Deacon wrote:
On Tue, Apr 23, 2013 at 11:54:53PM +0100, Olav Haugan wrote:
On 4/18/2013 12:01 PM, Will Deacon wrote:
Getting phandles has no dependencies on anything -- the only dependency is
that the device is added to the bus on which the SMMU sits, just
On Tue, Apr 23, 2013 at 11:54:53PM +0100, Olav Haugan wrote:
Hi Will,
Hello again,
On 4/18/2013 12:01 PM, Will Deacon wrote:
No. The device-tree describes the *hardware*, as per usual. The StreamIDs
are fixed properties of the SoC and we can't change them from Linux, so we
describe all
Hi Will,
On 4/18/2013 12:01 PM, Will Deacon wrote:
On Tue, Apr 16, 2013 at 07:18:42PM +0100, Olav Haugan wrote:
On 4/15/2013 6:13 AM, Will Deacon wrote:
If so, doesn't that strongly tie your video driver to the SMMU?
Isn't this more or less what you are doing in DT where you associate
On 4/15/2013 6:13 AM, Will Deacon wrote:
On Sat, Apr 13, 2013 at 10:02:09PM +0100, Olav Haugan wrote:
On 4/10/2013 10:37 AM, Will Deacon wrote:
Ok, but then how does that interact with the IOMMU API in Linux? e.g.
if a client asks for an iova - pa mapping on a device, then you
need to lookup
Hi again Will,
On 4/10/2013 10:37 AM, Will Deacon wrote:
On Mon, Apr 08, 2013 at 06:03:54PM +0100, Olav Haugan wrote:
Generally, the StreamIDs are fixed in hardware (as a function of
various AXI bits -- see the SMMU integration guide) and cannot be
set by software. Furthermore, when the
On Mon, Apr 08, 2013 at 06:03:54PM +0100, Olav Haugan wrote:
Hi Will,
Hello,
Generally, the StreamIDs are fixed in hardware (as a function of various AXI
bits -- see the SMMU integration guide) and cannot be set by software.
Furthermore, when the StreamIDs have an implicit effect on IOMMU
On Fri, Apr 05, 2013 at 07:25:26PM +0100, Rob Herring wrote:
On 04/05/2013 11:57 AM, Will Deacon wrote:
Hi Rob,
On Fri, Apr 05, 2013 at 05:43:06PM +0100, Rob Herring wrote:
[...]
+- compatible: Should be one of arm,smmu-v1 or arm,smmu-v2
+ depending on the
Hi Olav,
On Fri, Apr 05, 2013 at 09:44:49PM +0100, Olav Haugan wrote:
On 4/4/2013 9:50 AM, Will Deacon wrote:
diff --git a/Documentation/devicetree/bindings/iommu/arm,smmu.txt
b/Documentation/devicetree/bindings/iommu/arm,smmu.txt
new file mode 100644
index 000..938325f
---
Hi Will,
On 4/8/2013 2:25 AM, Will Deacon wrote:
Hi Olav,
On Fri, Apr 05, 2013 at 09:44:49PM +0100, Olav Haugan wrote:
On 4/4/2013 9:50 AM, Will Deacon wrote:
diff --git a/Documentation/devicetree/bindings/iommu/arm,smmu.txt
b/Documentation/devicetree/bindings/iommu/arm,smmu.txt
new file
Hi Rob,
On Fri, Apr 05, 2013 at 05:43:06PM +0100, Rob Herring wrote:
On 04/04/2013 11:50 AM, Will Deacon wrote:
This patch adds a description of the device tree binding for the ARM
System MMU architecture.
Cc: Rob Herring robherri...@gmail.com
Cc: Andreas Herrmann
On 04/04/2013 11:50 AM, Will Deacon wrote:
This patch adds a description of the device tree binding for the ARM
System MMU architecture.
Cc: Rob Herring robherri...@gmail.com
Cc: Andreas Herrmann andreas.herrm...@calxeda.com
Signed-off-by: Will Deacon will.dea...@arm.com
---
Hello,
On 4/4/2013 9:50 AM, Will Deacon wrote:
This patch adds a description of the device tree binding for the ARM
System MMU architecture.
Cc: Rob Herring robherri...@gmail.com
Cc: Andreas Herrmann andreas.herrm...@calxeda.com
Signed-off-by: Will Deacon will.dea...@arm.com
---
Hello,
The
13 matches
Mail list logo
