linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 5/6] iommu/mediatek: Add mt8173 IOMMU driver
Date: Fri, 24 Jul 2015 17:55:10 +0100	[thread overview]
Message-ID: <20150724165509.GD21177@arm.com> (raw)
In-Reply-To: <1437716593.23932.73.camel@mhfsdcap03>

On Fri, Jul 24, 2015 at 06:43:13AM +0100, Yong Wu wrote:
> On Tue, 2015-07-21 at 15:59 +0100, Will Deacon wrote:
> > On Thu, Jul 16, 2015 at 10:04:34AM +0100, Yong Wu wrote:
> > > +static void mtk_iommu_tlb_flush_all(void *cookie)
> > > +{
> > > +       struct mtk_iommu_domain *domain = cookie;
> > > +       void __iomem *base;
> > > +
> > > +       base = domain->data->base;
> > > +       writel(F_INVLD_EN1 | F_INVLD_EN0, base + REG_MMU_INV_SEL);
> > > +       writel(F_ALL_INVLD, base + REG_MMU_INVALIDATE);
> > 
> > This needs to be synchronous, so you probably want to call
> > mtk_iommu_tlb_sync at the end.
> 
> From our spec, we have to wait until HW done after tlb flush range.
> But it don't need wait after tlb flush all.
> so It isn't necessary to add mtk_iommu_tlb_sync in tlb_flush_all here.

Okey doke, but I'm surprised you don't need a subsequent DSB or read-back.
What if the writel is buffered on the way to the IOMMU?

Will

  reply	other threads:[~2015-07-24 16:55 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16  9:04 [PATCH v3 0/6] MT8173 IOMMU SUPPORT Yong Wu
2015-07-16  9:04 ` [PATCH v3 1/6] dt-bindings: iommu: Add binding for mediatek IOMMU Yong Wu
2015-07-16  9:04 ` [PATCH v3 2/6] dt-bindings: mediatek: Add smi dts binding Yong Wu
2015-07-16  9:04 ` [PATCH v3 3/6] iommu: add ARM short descriptor page table allocator Yong Wu
2015-07-21 17:11   ` Will Deacon
2015-07-24  5:24     ` Yong Wu
2015-07-24 16:53       ` Will Deacon
2015-07-27  4:21         ` Yong Wu
2015-07-27 14:05           ` Robin Murphy
2015-07-27 14:11             ` Will Deacon
2015-07-28  5:08               ` Yong Wu
2015-07-28 11:00                 ` Will Deacon
2015-07-28 13:37                   ` Yong Wu
2015-07-28 13:47                     ` Will Deacon
     [not found]           ` <1438329337.25925.147.camel@mhfsdcap03>
2015-07-31 11:32             ` Will Deacon
2015-09-14 12:25     ` Yong Wu
2015-09-16 12:55       ` Will Deacon
2015-09-17  2:38         ` Yong Wu
2015-07-16  9:04 ` [PATCH v3 4/6] memory: mediatek: Add SMI driver Yong Wu
2015-07-16  9:04 ` [PATCH v3 5/6] iommu/mediatek: Add mt8173 IOMMU driver Yong Wu
2015-07-21 14:59   ` Will Deacon
2015-07-24  5:43     ` Yong Wu
2015-07-24 16:55       ` Will Deacon [this message]
2015-07-27  4:24         ` Yong Wu
2015-07-27 15:48           ` Will Deacon
2015-07-27 13:23   ` Robin Murphy
2015-07-27 15:31     ` Russell King - ARM Linux
2015-07-27 15:49       ` Robin Murphy
2015-07-29  5:41         ` Yong Wu
2015-07-29 10:31           ` Will Deacon
2015-07-29  6:32     ` Yong Wu
2015-07-16  9:04 ` [PATCH v3 6/6] dts: mt8173: Add iommu/smi nodes for mt8173 Yong Wu
2015-07-23 14:40   ` Daniel Kurtz
2015-07-29  7:29     ` Yong Wu

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=20150724165509.GD21177@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).