Re: [PATCH/RFC 1/2] arm64: mm: Silently allow devices lacking IOMMU group

Hi Robin, On Mon, Jan 23, 2017 at 9:34 PM, Robin Murphy wrote: > Hi Magnus, > > On 23/01/17 12:12, Magnus Damm wrote: >> From: Magnus Damm >> >> Consider failure of iommu_get_domain_for_dev() as non-critical and >> get rid of the warning printout. This allows IOMMU properties to be >> included i

RE: [PATCH/RFC 1/2] arm64: mm: Silently allow devices lacking IOMMU group

Hi Robin, >> Consider failure of iommu_get_domain_for_dev() as non-critical and >> get rid of the warning printout. This allows IOMMU properties to be >> included in the DTB even though the kernel is configured with >> CONFIG_IOMMU_API=n or in case a particular IOMMU driver refuses to >> enable IO

Re: [PATCH/RFC 1/2] arm64: mm: Silently allow devices lacking IOMMU group

Hi Magnus, On 23/01/17 12:12, Magnus Damm wrote: > From: Magnus Damm > > Consider failure of iommu_get_domain_for_dev() as non-critical and > get rid of the warning printout. This allows IOMMU properties to be > included in the DTB even though the kernel is configured with > CONFIG_IOMMU_API=n o

[PATCH/RFC 1/2] arm64: mm: Silently allow devices lacking IOMMU group

From: Magnus Damm Consider failure of iommu_get_domain_for_dev() as non-critical and get rid of the warning printout. This allows IOMMU properties to be included in the DTB even though the kernel is configured with CONFIG_IOMMU_API=n or in case a particular IOMMU driver refuses to enable IOMMU su