From: Yong Wu <yong.wu@mediatek.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Thierry Reding <treding@nvidia.com>,
Mark Rutland <mark.rutland@arm.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
"Robin Murphy" <robin.murphy@arm.com>,
Will Deacon <will.deacon@arm.com>,
"Daniel Kurtz" <djkurtz@google.com>,
Tomasz Figa <tfiga@google.com>,
Lucas Stach <l.stach@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
"Catalin Marinas" <catalin.marinas@arm.com>,
<linux-mediatek@lists.infradead.org>,
Sasha Hauer <kernel@pengutronix.de>,
<srv_heupstream@mediatek.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<iommu@lists.linux-foundation.org>, <pebolle@tiscali.nl>,
<arnd@arndb.de>, <mitchelh@codeaurora.org>,
Sricharan R <sricharan@codeaurora.org>, <youhua.li@mediatek.com>,
<k.zhang@mediatek.com>, <kendrick.hsu@mediatek.com>
Subject: Re: [PATCH v5 5/6] iommu/mediatek: Add mt8173 IOMMU driver
Date: Mon, 26 Oct 2015 13:23:41 +0800 [thread overview]
Message-ID: <1445837021.24436.8.camel@mhfsdcap03> (raw)
In-Reply-To: <20151014125309.GO27420@8bytes.org>
On Wed, 2015-10-14 at 14:53 +0200, Joerg Roedel wrote:
> On Fri, Oct 09, 2015 at 10:23:07AM +0800, Yong Wu wrote:
> > + /*
> > + * There is a domain for each a iommu device in normal case.
> > + * But MTK only has one iommu domain called the m4u domain which all
> > + * the multimedia HW share. Here we reserve one as the m4u domain and
> > + * free the others.
> > + *
> > + * And the attach_device that from __iommu_setup_dma_ops
> > + * will be called earlier than probe.
> > + */
>
> Okay, with this being the case, you need to put all devices behind one
> IOMMU into the same iommu-group, because the IOMMU can't really isolate
> the devices from each other.
>
> > +static int mtk_iommu_add_device(struct device *dev)
> > +{
> > + struct iommu_group *group;
> > + struct mtk_iommu_client_priv *priv;
> > + struct mtk_iommu_domain *m4udom;
> > + struct iommu_domain *domain;
> > + int ret;
> > +
> > + if (!dev->archdata.iommu) /* Not a iommu client device */
> > + return -ENODEV;
> > +
> > + group = iommu_group_get(dev);
> > + if (!group) {
> > + group = iommu_group_alloc();
> > + if (IS_ERR(group)) {
> > + dev_err(dev, "Failed to allocate IOMMU group\n");
> > + return PTR_ERR(group);
> > + }
> > + }
> > +
> > + ret = iommu_group_add_device(group, dev);
> > + if (ret) {
> > + dev_err(dev, "Failed to add IOMMU group\n");
> > + goto err_group_put;
> > + }
> > +
> > + domain = iommu_get_domain_for_dev(dev);
> > + if (!domain) {
> > + /*
> > + * Get the m4u iommu domain from the m4u device.
> > + * Attach all the client devices into the m4u domain.
> > + */
> > + priv = dev->archdata.iommu;
> > + m4udom = dev_get_drvdata(priv->m4udev);
> > + ret = iommu_attach_group(&m4udom->domain, group);
> > + if (ret)
> > + dev_err(dev, "Failed to attach IOMMU group\n");
> > + }
> > +
> > +err_group_put:
> > + iommu_group_put(group);
> > + return ret;
> > +}
>
> Here it looks like you are allocating one group for each device. As I
> said, all devices need to be in one group.
>
> Joerg
>
Thanks for this suggestion. I have put all the iommu client devices into
the same iommu group, the code looks like below.
And I will send this in the next version after the Short descriptor is
reviewed.
static int mtk_iommu_add_device(struct device *dev)
{
struct iommu_group *group;
struct mtk_iommu_client_priv *priv;
struct mtk_iommu_domain *m4udom;
struct iommu_domain *domain;
int ret;
priv = dev->archdata.iommu;
if (!priv) /* Not a iommu client device */
return -ENODEV;
m4udom = dev_get_drvdata(priv->m4udev);
group = iommu_group_get(dev);
if (!group) {
/*
* All the iommu client devices are in the m4u domain,
* they all are in the same m4u iommu-group too here.
*/
if (!m4udom->m4u_group) {
group = iommu_group_alloc();
if (IS_ERR(group)) {
dev_err(dev, "Failed to allocate IOMMU group\n");
return PTR_ERR(group);
}
m4udom->m4u_group = group;
} else {
group = m4udom->m4u_group;
}
}
ret = iommu_group_add_device(group, dev);
if (ret) {
dev_err(dev, "Failed to add IOMMU group\n");
goto err_group_put;
}
domain = iommu_get_domain_for_dev(dev);
if (!domain)
ret = iommu_attach_group(&m4udom->domain, group);
err_group_put:
iommu_group_put(group);
return ret;
}
next prev parent reply other threads:[~2015-10-26 5:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 2:23 [PATCH v5 0/6] MT8173 IOMMU SUPPORT Yong Wu
2015-10-09 2:23 ` [PATCH v5 1/6] dt-bindings: iommu: Add binding for mediatek IOMMU Yong Wu
2015-10-09 2:23 ` [PATCH v5 2/6] dt-bindings: mediatek: Add smi dts binding Yong Wu
2015-10-09 2:23 ` [PATCH v5 3/6] iommu: add ARM short descriptor page table allocator Yong Wu
2015-10-14 12:54 ` Joerg Roedel
2015-10-15 17:20 ` Will Deacon
2015-11-06 8:42 ` Yong Wu
2015-11-06 11:42 ` Will Deacon
2015-10-09 2:23 ` [PATCH v5 4/6] memory: mediatek: Add SMI driver Yong Wu
2015-10-27 13:24 ` Robin Murphy
2015-10-31 8:32 ` Yong Wu
2015-10-09 2:23 ` [PATCH v5 5/6] iommu/mediatek: Add mt8173 IOMMU driver Yong Wu
2015-10-14 12:53 ` Joerg Roedel
2015-10-26 5:23 ` Yong Wu [this message]
2015-10-27 13:25 ` Robin Murphy
2015-10-31 8:28 ` Yong Wu
2015-10-09 2:23 ` [PATCH v5 6/6] dts: mt8173: Add iommu/smi nodes for mt8173 Yong Wu
2015-10-14 12:56 ` [PATCH v5 0/6] MT8173 IOMMU SUPPORT Joerg Roedel
2015-10-22 4:40 ` Yong Wu
2015-10-23 9:26 ` Joerg Roedel
2015-11-24 5:58 ` Yong Wu
2015-11-24 10:38 ` Thierry Reding
2015-11-25 1:30 ` 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=1445837021.24436.8.camel@mhfsdcap03 \
--to=yong.wu@mediatek.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=djkurtz@google.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=k.zhang@mediatek.com \
--cc=kendrick.hsu@mediatek.com \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=mitchelh@codeaurora.org \
--cc=pebolle@tiscali.nl \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sricharan@codeaurora.org \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@google.com \
--cc=treding@nvidia.com \
--cc=will.deacon@arm.com \
--cc=youhua.li@mediatek.com \
/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).