From mboxrd@z Thu Jan 1 00:00:00 1970 From: ray.jui@broadcom.com (Ray Jui) Date: Tue, 6 Jun 2017 23:20:03 -0700 Subject: Device address specific mapping of arm,mmu-500 In-Reply-To: References: <1b79efe2-6835-7a7a-f5ad-361391a7b967@broadcom.com> <20170530151437.GC23067@arm.com> <81637642-22d9-4868-156f-052f64bd042f@broadcom.com> <226bcebc-3902-90d3-24e5-51f2e1f3affb@arm.com> <16e5fc9d-b014-af7c-dcda-527522ac5cc9@arm.com> <7bd03bf8-71d5-a974-bea2-a38b4349c547@broadcom.com> <20170531124418.GE9723@arm.com> <498100e8-e94e-4a65-a9e1-ae59bd59fe2d@broadcom.com> Message-ID: <41f12daa-b46c-83f1-9c9f-51de1cadf14f@broadcom.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Robin, On 6/6/2017 3:02 AM, Robin Murphy wrote: > I've currently got some experimental patches pushed out here: > > git://linux-arm.org/linux-rm iommu/pgtable > > So far, there's still one silly bug (which doesn't affect DMA ops usage) > and an awkward race for non-coherent table walks which will need > resolving before I have anything to post properly, which I hope will be > within the next couple of weeks. In the meantime, though, it already > seems to work well enough in practice, so any feedback is welcome! > > Robin. Excellent! I'm going to find time to test it out (likely next week). I'll report back the test result after that. Thanks, Ray