Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: robin.murphy@arm.com (Robin Murphy)
To: linux-arm-kernel@lists.infradead.org
Subject: Need some information about IOMMU support for ARM64 in 4.6
Date: Thu, 15 Dec 2016 14:59:06 +0000	[thread overview]
Message-ID: <a02aee03-00ff-4855-73fe-a5ac809c461c@arm.com> (raw)
In-Reply-To: <E6F4274F7BEC774AAA4E7A98618BCFAE132076@XAP-PVEXMBX01.xlnx.xilinx.com>

Hi Barghav,

I assume you're talking about the ARM SMMU(v2)?

On 15/12/16 06:50, Bhargav Shah wrote:
> Hi,
> I am using kernel version 4.6.
> of_iommu_configure() gets IOMMU ops from of_iommu_list and call arch_setup_dma_ops.
> Presently, __iommu_setup_dma_ops() it expects iommu ops to be present. 
> Here, of_iommu_configure() get NULL iommu ops and it calls arch_setup_dma_ops with it.
> 
> So, in my current flow iommu ops is not getting set for device.

Yes. The SMMUv2 driver in 4.6 does not call of_iommu_set_ops(). That's
because it doesn't support of_xlate() either, so in general can't be
used for DMA ops. The default domain support which went into 4.6 was
just some early groundwork which, in hindsight, caused more problems
than it solved at that time.

> Am I missing something  which is causing this ?
> What is proper way to set iommu ops to device ? 

The proper way would be to update to 4.9, where full generic
configuration and DMA ops support finally landed ;)

Robin.

> 
> Thanks
> Bhargav 
> 
> 

      reply	other threads:[~2016-12-15 14:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-15  6:50 Need some information about IOMMU support for ARM64 in 4.6 Bhargav Shah
2016-12-15 14:59 ` Robin Murphy [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=a02aee03-00ff-4855-73fe-a5ac809c461c@arm.com \
    --to=robin.murphy@arm.com \
    --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