On Fri, Apr 18, 2014 at 3:52 PM, Tony Lindgren <tony@xxxxxxxxxxx> wrote: > * Rob Herring <robherring2@xxxxxxxxx> [140411 10:33]: >> On Fri, Mar 21, 2014 at 9:46 AM, Jean-Jacques Hiblot >> <jjhiblot@xxxxxxxxxxxxxxx> wrote: >> > The goal of this patch is to allow drivers to be probed even if at the time of >> > the DT parsing some of their IRQ ressources are not available yet. >> > >> > In the current situation, the IRQ resources of a platform device are filled from >> > the DT at the time the device is created (of_device_alloc()). The drawback of >> > this is that a device sitting close to the top of the DT (ahb for example) but >> > depending on ressources that are initialized later (IRQ domain dynamically >> > created for example) will fail to probe because the ressources don't exist >> > at this time. >> >> s/ressources/resources/ > > While I've tested these two patches and they fix the issue for me. I have > some serious doubts again about this whole ------ up string parsing > pile of ---- called device tree. > > Do we really need to sprinkle more of_* hacks to the irq subsystem? > > There's nothing wrong with with the irq subsystem. Platform bus is just > calling the irq subsystem at the wrong time with uninitialized data. This patch doesn't even touch the irq subsystem. > It seems that we're again papering over the fact that there's nothing > coordinating the setting up of various resources with device tree. > That seems to be the repeating never ending pattern as we've already > seen with GPIOs, pinctrl, and IRQchips. We end up adding all kinds of > cross subsystem calls that were never needed earlier. This problem may be made worse with DT, but this problem has existed for as long as I have worked on the kernel. It is worse with DT since platforms have less control over the init ordering and loose some ability to do tricks like changing the initcall levels. We didn't even try to do pinctrl in any generic way before DT. Rob -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
