public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 1/7] iommu: provide early initialisation hook for IOMMU drivers
Date: Mon, 01 Sep 2014 16:31:28 +0200	[thread overview]
Message-ID: <4386980.goxm0OjCmJ@wuerfel> (raw)
In-Reply-To: <20140901075216.GA24430@ulmo>

On Monday 01 September 2014 09:52:19 Thierry Reding wrote:
> I don't think this is the right direction. We've been preaching that
> using initcall ordering is a bad thing and people should be using
> deferred probe instead. Now we have a bunch of these OF tables that do
> the exact opposite. Note that these are nothing more than a variant of
> initcalls that get called at platform-specific points in time.
> 
> There are also ongoing discussions about how to change the device probe
> order to use dependencies (such as phandles from device tree) to prevent
> excessive deferred probing. With that in place this would be solved in a
> much more generic way.

We are not creating an ABI here, so it can always be changed later.
For now, I think iommus are clearly in the same category as irqchips,
timers, clock controllers and smp operations: we really want them
to be available before we set up any other devices.

I don't mind finding a more generic solution in the long run, but for
now, this gets the problem out of the way, and I can't think of any
realistic corner cases that would prevent it from working. Do you
think that an IOMMU driver may have a dependency on another device
driver that is probed later? Do you have an example of such hardware?

	Arnd

  reply	other threads:[~2014-09-01 14:31 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 [this message]
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
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=4386980.goxm0OjCmJ@wuerfel \
    --to=arnd@arndb.de \
    --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