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 4/7] iommu: provide helper function to configure an IOMMU for an of master
Date: Tue, 2 Sep 2014 11:03:42 +0100	[thread overview]
Message-ID: <20140902100342.GG25379@arm.com> (raw)
In-Reply-To: <4335091.FB685Z52eG@wuerfel>

On Mon, Sep 01, 2014 at 09:18:26PM +0100, Arnd Bergmann wrote:
> On Monday 01 September 2014 17:40:00 Will Deacon wrote:
> > On Mon, Sep 01, 2014 at 03:46:18PM +0100, Arnd Bergmann wrote:
> > > On Monday 01 September 2014 10:29:40 Thierry Reding wrote:
> > > > 
> > > > I think this could use a bit more formalization. As I said in another
> > > > reply earlier, there's very little standardization in the IOMMU API.
> > > > That certainly gives us a lot of flexibility but it also has the
> > > > downside that it's difficult to handle these abstractions in the core,
> > > > which is really what the core is all about, isn't it?
> > > > 
> > > > One method that worked really well for this in the past for other
> > > > subsystems is to allow drivers to specify an .of_xlate() function that
> > > > takes the controller device and a struct of_phandle_args. It is that
> > > > function's responsibility to take the information in an of_phandle_args
> > > > structure and use that to create some subsystem specific handle that
> > > > represents this information in a way that it can readily be used.
> > > 
> > > Yes, good idea.
> > 
> > Hmm, how does this work for PCI devices? The current RFC takes care to
> > ensure that the core changes work just as well for OF devices as PCI
> > devices, and the of-specific functions and data structures are not part of
> > it.
> 
> I don't mind handling PCI devices separately. They are different in a number
> of ways already, in particular the way that they don't normally have an
> of_node attached to them but actually have a PCI bus/dev/function number.

Sure, but at the point when we call back into the iommu_ops structure we
really don't want bus specific functions. That's why I avoided any OF
data structures being passed to add_device_master_ids.

Anyway, I'll try to hack something together shortly. I think the proposal
is:

  - Make add_device_master_ids take a generic structure (struct iommu)
  - Add an of_xlate callback into iommu_ops which returns a populated
    struct iommu based on the of_node

Sound about right?

Will

  reply	other threads:[~2014-09-02 10:03 UTC|newest]

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

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=20140902100342.GG25379@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).