linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v3 3/7] iommu: add new iommu_ops callback for adding an OF device
Date: Wed, 17 Sep 2014 02:39:07 +0100	[thread overview]
Message-ID: <20140917013907.GA15756@arm.com> (raw)
In-Reply-To: <5416D432.8020107@samsung.com>

On Mon, Sep 15, 2014 at 12:57:38PM +0100, Marek Szyprowski wrote:
> Hello,

Hi Marek,

Thanks for looking again at this -- I'll take at look at your exynos series
when I'm back in the UK next week.

> On 2014-09-12 18:34, Will Deacon wrote:
> > This patch adds a new function to the iommu_ops structure to allow an
> > OF device to be added to a specific IOMMU instance using the recently
> > merged generic devicetree binding for IOMMUs. The callback (of_xlate)
> > takes a struct device representing the master and an of_phandle_args
> > representing the IOMMU and the correspondong IDs for the new master.
> >
> > Signed-off-by: Will Deacon <will.deacon@arm.com>
> > ---
> >   include/linux/iommu.h | 5 +++++
> >   1 file changed, 5 insertions(+)
> >
> > diff --git a/include/linux/iommu.h b/include/linux/iommu.h
> > index 4256f3ce1673..821eb0bd9f6c 100644
> > --- a/include/linux/iommu.h
> > +++ b/include/linux/iommu.h
> > @@ -21,6 +21,7 @@
> >   
> >   #include <linux/errno.h>
> >   #include <linux/err.h>
> > +#include <linux/of.h>
> >   #include <linux/types.h>
> >   #include <trace/events/iommu.h>
> >   
> > @@ -140,6 +141,10 @@ struct iommu_ops {
> >   	/* Get the numer of window per domain */
> >   	u32 (*domain_get_windows)(struct iommu_domain *domain);
> >   
> > +#ifdef CONFIG_OF_IOMMU
> > +	int (*of_xlate)(struct device *dev, struct of_phandle_args *args);
> > +#endif
> 
> 
> If I understand correctly, this callback is intended to do per-master 
> initialization
> of the iommu structures required by the given iommu driver (I stored them in
> dev->archdata.iommu). However I really don't get what is the meaning of 
> the return
> value. Is it a boolean value? It is used only by of_iommu_configure to 
> check if
> the parse loop should be terminated...

It should probably return 0 on success, < 0 otherwise. I'll fix
of_iommu_configure to check for < 0 and only exit the loop then. The idea is
that we don't swizzle the DMA ops for a device to IOMMU ops if of_xlate
failed for any of its IDs.

Will

  reply	other threads:[~2014-09-17  1:39 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-12 16:34 [RFC PATCH v3 0/7] Introduce automatic DMA configuration for IOMMU masters Will Deacon
2014-09-12 16:34 ` [RFC PATCH v3 1/7] iommu: provide early initialisation hook for IOMMU drivers Will Deacon
2014-09-18 14:31   ` Robin Murphy
2014-09-22 17:35     ` Will Deacon
2014-09-12 16:34 ` [RFC PATCH v3 2/7] dma-mapping: replace set_arch_dma_coherent_ops with arch_setup_dma_ops Will Deacon
2014-09-12 16:34 ` [RFC PATCH v3 3/7] iommu: add new iommu_ops callback for adding an OF device Will Deacon
2014-09-15 11:57   ` Marek Szyprowski
2014-09-17  1:39     ` Will Deacon [this message]
2014-09-12 16:34 ` [RFC PATCH v3 4/7] iommu: provide helper function to configure an IOMMU for an of master Will Deacon
2014-09-18 11:13   ` Laurent Pinchart
2014-09-22 17:13     ` Will Deacon
2014-10-14 13:12       ` Laurent Pinchart
2014-09-12 16:34 ` [RFC PATCH v3 5/7] dma-mapping: detect and configure IOMMU in of_dma_configure Will Deacon
2014-09-18 11:17   ` Laurent Pinchart
2014-09-22  9:29     ` Thierry Reding
2014-09-22 17:50       ` Will Deacon
2014-10-14 12:53         ` Laurent Pinchart
2014-10-27 10:51           ` Will Deacon
2014-10-27 11:12             ` Marek Szyprowski
2014-10-27 11:30             ` Laurent Pinchart
2014-10-27 16:02               ` Will Deacon
2014-10-27 16:33                 ` jroedel at suse.de
2014-09-22 17:46     ` Will Deacon
2014-09-12 16:34 ` [RFC PATCH v3 6/7] arm: call iommu_init before of_platform_populate Will Deacon
2014-09-22  9:36   ` Thierry Reding
2014-09-22 11:08     ` Arnd Bergmann
2014-09-22 11:40       ` Thierry Reding
2014-09-22 16:03         ` Arnd Bergmann
2014-09-23  7:02           ` Thierry Reding
2014-09-23  7:44             ` Arnd Bergmann
2014-09-23  8:59               ` Thierry Reding
2014-10-14 13:07               ` Laurent Pinchart
2014-10-14 13:20                 ` Arnd Bergmann
2014-10-14 13:37                   ` Thierry Reding
2014-10-14 15:01                     ` Laurent Pinchart
2014-10-14 15:05                       ` Thierry Reding
2014-10-14 15:10                         ` Laurent Pinchart
2014-09-12 16:34 ` [RFC PATCH v3 7/7] arm: dma-mapping: plumb our iommu mapping ops into arch_setup_dma_ops Will Deacon
2014-09-22  9:19   ` Thierry Reding
2014-09-22  9:22     ` Laurent Pinchart
2014-09-22 17:43     ` Will Deacon
2014-09-23  7:14       ` Thierry Reding
2014-09-24 16:33         ` Will Deacon
2014-09-25  6:40           ` Thierry Reding
2014-09-30 16:00             ` Will Deacon
2014-10-01  8:46               ` Thierry Reding
2014-10-03 15:08                 ` Will Deacon
2014-10-06  9:52                   ` Thierry Reding
2014-10-06 10:50                     ` Laurent Pinchart
2014-10-06 13:05                       ` Thierry Reding
2014-09-16 11:40 ` [RFC PATCH v3 0/7] Introduce automatic DMA configuration for IOMMU masters Robin Murphy
2014-09-17  1:19   ` Will Deacon

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=20140917013907.GA15756@arm.com \
    --to=will.deacon@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;
as well as URLs for NNTP newsgroup(s).