lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 28 Nov 2015 10:09:07 +0800 From: chenfeng <puck.chen@...ilicon.com> To: Joerg Roedel <joro@...tes.org> CC: <iommu@...ts.linux-foundation.org>, <linux-kernel@...r.kernel.org>, <robh+dt@...nel.org>, <pawel.moll@....com>, <mark.rutland@....com>, <ijc+devicetree@...lion.org.uk>, <devicetree@...r.kernel.org>, <puck.chen@...yun.com>, <w.f@...wei.com>, <xuwei5@...ilicon.com>, <guodong.xu@...aro.org>, <arnd@...aro.org>, <haojian.zhuang@...aro.org> Subject: Re: [PATCH V5 RESEND 0/3] Add iommu support for hi6220 HiKey board 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 > > > . > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists