Re: GPIO/IRQ expander cannot map interrupt

[Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>]

On Tue, Nov 29, 2011 at 07:59:26AM +0100, Thierry Reding wrote:

> of hook that allows the driver to specify at probe time that some resources
> are still missing and is used for cases where there is no explicit dependency
> information and thus the driver core doesn't know in which order devices need
> to be probed.

The intention is to use it at all times and just not bother with
explicit ordering information as this is going to be more robust
especially given the need to sort out things like driver registration
ordering.

> However, for this particular case we actually have this explicit dependency
> information because the devices specify an interrupt and/or GPIO parent.
> Moreover it's not really the probing that is the issue here, but rather the
> device instantiation. The OF core instantiates the I2C slaves much too early
> (i.e. together with the interrupt parent) and therefore requires access to
> the IRQ domain mapping at the time of the instantiation already.

That's a separate issue though.