From: chenfeng <puck.chen@hisilicon.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: <iommu@lists.linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <robh+dt@kernel.org>,
<pawel.moll@arm.com>, <mark.rutland@arm.com>,
<ijc+devicetree@hellion.org.uk>, <devicetree@vger.kernel.org>,
<puck.chen@aliyun.com>, <w.f@huawei.com>, <xuwei5@hisilicon.com>,
<guodong.xu@linaro.org>, <arnd@linaro.org>,
<haojian.zhuang@linaro.org>
Subject: Re: [PATCH V5 RESEND 0/3] Add iommu support for hi6220 HiKey board
Date: Sat, 28 Nov 2015 10:09:07 +0800 [thread overview]
Message-ID: <56590CC3.5050401@hisilicon.com> (raw)
In-Reply-To: <20151127114920.GH24300@8bytes.org>
On 2015/11/27 19:49, Joerg Roedel wrote:
> On Fri, Nov 20, 2015 at 10:25:06AM +0800, Chen Feng wrote:
>> eg:
>> struct iommu_domain *domain = iommu_domain_alloc(bus);
>> iommu_attach_device(domain, dev);
>> struct iova_domain *iovad = (struct iova_domain *)m_dev->archdata.iommu;
>> struct iova * t_iova = alloc_iova(iovad, size, limit_pfn, align);
>> iommu_map(domain, t_iova->pfn_lo << 12, phy_addr, size, port);
>
> Any reason the media subsystem should use the iommu-api directly, and
> not the dma-api? You can make your iommu available by adapting the
> common dma-iommu implementation from Robin Murphy to your iommu to make
> it usable through the dma-api.
>
ok, I will change this to dma-api. Since v1 version, the dma-api was not ok for arm64.
I will do this with dma-api function.
>
> Joerg
>
>
> .
>
prev parent reply other threads:[~2015-11-28 2:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 2:25 [PATCH V5 RESEND 0/3] Add iommu support for hi6220 HiKey board Chen Feng
2015-11-20 2:25 ` [PATCH V5 RESEND 1/3] docs: iommu: Documentation for iommu in hi6220 SoC Chen Feng
2015-11-20 14:21 ` Rob Herring
2015-11-20 2:25 ` [PATCH V5 RESEND 2/3] iommu/hisilicon: Add hi6220-SoC smmu driver Chen Feng
2015-11-27 12:02 ` Joerg Roedel
2015-11-28 2:19 ` chenfeng
2015-11-28 12:19 ` Joerg Roedel
2015-11-20 2:25 ` [PATCH V5 RESEND 3/3] arm64: dts: Add dts node for hi6220 " Chen Feng
2015-11-27 11:49 ` [PATCH V5 RESEND 0/3] Add iommu support for hi6220 HiKey board Joerg Roedel
2015-11-28 2:09 ` chenfeng [this message]
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=56590CC3.5050401@hisilicon.com \
--to=puck.chen@hisilicon.com \
--cc=arnd@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=guodong.xu@linaro.org \
--cc=haojian.zhuang@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=puck.chen@aliyun.com \
--cc=robh+dt@kernel.org \
--cc=w.f@huawei.com \
--cc=xuwei5@hisilicon.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