linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 4/5] iommu/mediatek: Add mt8173 IOMMU driver
Date: Wed, 16 Dec 2015 16:15:15 +0100	[thread overview]
Message-ID: <20151216151514.GI18805@8bytes.org> (raw)
In-Reply-To: <5670098E.40601@arm.com>

On Tue, Dec 15, 2015 at 12:37:34PM +0000, Robin Murphy wrote:
> The potential issue I *do* see, looking more closely, is that
> iommu_group_get_for_dev() is setting group->domain but not calling
> the attach_dev callback, which looks wrong...

Attaching the device happens from iommu_group_add_device(), which is
called from iommu_group_get_for_dev() right after the domains are
allocated/initialized.


	Joerg

  parent reply	other threads:[~2015-12-16 15:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-08  9:49 [PATCH v6 0/5] MT8173 IOMMU SUPPORT Yong Wu
2015-12-08  9:49 ` [PATCH v6 1/5] dt-bindings: iommu: Add binding for mediatek IOMMU Yong Wu
2015-12-09  3:33   ` Rob Herring
2015-12-09  6:55     ` Yong Wu
2015-12-08  9:49 ` [PATCH v6 2/5] dt-bindings: mediatek: Add smi dts binding Yong Wu
2015-12-09  3:35   ` Rob Herring
2015-12-08  9:49 ` [PATCH v6 3/5] memory: mediatek: Add SMI driver Yong Wu
2015-12-11  7:22   ` Yong Wu
2015-12-14 18:18   ` Matthias Brugger
2015-12-15  2:38     ` Yong Wu
2015-12-15  5:45       ` Daniel Kurtz
2015-12-16  6:00         ` Yong Wu
2015-12-08  9:49 ` [PATCH v6 4/5] iommu/mediatek: Add mt8173 IOMMU driver Yong Wu
2015-12-08 10:32   ` kbuild test robot
2015-12-14 14:16   ` Joerg Roedel
2015-12-15  3:28     ` Yong Wu
2015-12-15 12:37       ` Robin Murphy
2015-12-16  5:59         ` Yong Wu
2015-12-16 12:48           ` Robin Murphy
2015-12-17  3:12             ` Yong Wu
2015-12-16 15:15         ` Joerg Roedel [this message]
2015-12-14 18:19   ` Matthias Brugger
2015-12-15  2:40     ` Yong Wu
2015-12-08  9:49 ` [PATCH v6 5/5] dts: mt8173: Add iommu/smi nodes for mt8173 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=20151216151514.GI18805@8bytes.org \
    --to=joro@8bytes.org \
    --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).