linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robin.murphy@arm.com (Robin Murphy)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v2 PATCH 0/6] MT8173 IOMMU SUPPORT
Date: Mon, 18 May 2015 11:23:05 +0100	[thread overview]
Message-ID: <5559BD89.1060100@arm.com> (raw)
In-Reply-To: <CAGS+omASN0GWiXYFg9kn7grWoKywqUiSwLZdW9BKc+S-Dnp+Cg@mail.gmail.com>

On 16/05/15 08:08, Daniel Kurtz wrote:
> On Fri, May 15, 2015 at 5:43 PM, Yong Wu <yong.wu@mediatek.com> wrote:
>>    This patch adds support for m4u(Multimedia Memory Management Unit),
>> Currently it only support the m4u with 2 levels of page table on mt8173.
>>
>>    It is based on Robin Murphy's arm64: IOMMU-backed DMA mapping[1].
>
>
> Hi Yong, Robin,

Hi Dan,

> The quoted "arm64 iommu-backed DMA mapping" patch set is from 2015-February.
> That was over 3 months ago.
> What is the status of this work?

Still in progress - I've been hampered a bit by having to rework a whole 
bunch of SMMU driver changes and other in-development stuff in parallel 
so I can do at least try to test as much as I can, not to mention 
various unrelated internal work. It also doesn't help that I also tried 
re-engineering things for v3 in a way that made some of it nicer, but 
turned out not to work so well elsewhere.

> Is that still the most recent version of these patches?
> If so, is there a plan when an update will be posted?
> Or, is there an updated public git repo with a more recent version of
> these patches?

This is now my primary focus again, so I'll get an updated posting out 
by the end of next week at the latest.

> My apologies if these questions have been asked and answered before
> and/or elsewhere.

Not on-list, at any rate, so there's no harm calling it out - helps me 
get my priorities straight ;)

Thanks,
Robin.

  reply	other threads:[~2015-05-18 10:23 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15  9:43 [RFC v2 PATCH 0/6] MT8173 IOMMU SUPPORT Yong Wu
2015-05-15  9:43 ` [PATCH v2 1/6] dt-bindings: iommu: Add binding for mediatek IOMMU Yong Wu
2015-05-25  6:31   ` Tomasz Figa
2015-05-27  7:03     ` Yong Wu
2015-05-15  9:43 ` [PATCH v2 2/6] dt-bindings: mediatek: Add smi dts binding Yong Wu
2015-05-15 10:02   ` Yong Wu
2015-05-25  6:48   ` Tomasz Figa
2015-05-27  7:36     ` Yong Wu
2015-05-15  9:43 ` [PATCH v2 3/6] iommu: add ARM short descriptor page table allocator Yong Wu
2015-05-15 15:30   ` Robin Murphy
2015-05-22  3:14     ` Yong Wu
2015-06-05 13:12   ` Will Deacon
2015-06-26  7:30     ` Yong Wu
2015-05-15  9:43 ` [PATCH v2 4/6] soc: mediatek: Add SMI driver Yong Wu
2015-05-19 11:14   ` Matthias Brugger
2015-05-21  6:16     ` Yong Wu
2015-05-21  7:30       ` Matthias Brugger
2015-05-21  7:38         ` Yong Wu
2015-05-21 14:33         ` Daniel Kurtz
2015-05-21 14:49           ` Yong Wu
2015-05-21 15:20             ` Matthias Brugger
2015-05-15  9:43 ` [PATCH v2 5/6] iommu/mediatek: Add mt8173 IOMMU driver Yong Wu
2015-05-25  8:29   ` Tomasz Figa
2015-05-27  7:26     ` Yong Wu
2015-06-05 13:30   ` Will Deacon
2015-05-15  9:43 ` [PATCH v2 6/6] dts: mt8173: Add iommu/smi nodes for mt8173 Yong Wu
2015-05-16  7:08 ` [RFC v2 PATCH 0/6] MT8173 IOMMU SUPPORT Daniel Kurtz
2015-05-18 10:23   ` Robin Murphy [this message]
2015-05-18 12:09 ` Matthias Brugger

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=5559BD89.1060100@arm.com \
    --to=robin.murphy@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).