Re: [PATCH v2 08/10] of/platform: Resolve interrupt references at probe time

2013-10-25 Thread Thierry Reding
On Thu, Oct 24, 2013 at 05:37:49PM +0100, Grant Likely wrote: > On Wed, 16 Oct 2013 00:24:36 +0100, Grant Likely > wrote: > > On Wed, 18 Sep 2013 15:24:50 +0200, Thierry Reding > > wrote: > > > Interrupt references are currently resolved very early (when a device is > > > created). This has

Re: [PATCH v2 08/10] of/platform: Resolve interrupt references at probe time

2013-10-25 Thread Thierry Reding
On Thu, Oct 24, 2013 at 05:37:49PM +0100, Grant Likely wrote: On Wed, 16 Oct 2013 00:24:36 +0100, Grant Likely grant.lik...@linaro.org wrote: On Wed, 18 Sep 2013 15:24:50 +0200, Thierry Reding thierry.red...@gmail.com wrote: Interrupt references are currently resolved very early (when a

Re: [PATCH v2 08/10] of/platform: Resolve interrupt references at probe time

2013-10-24 Thread Grant Likely
On Wed, 16 Oct 2013 00:24:36 +0100, Grant Likely wrote: > On Wed, 18 Sep 2013 15:24:50 +0200, Thierry Reding > wrote: > > Interrupt references are currently resolved very early (when a device is > > created). This has the disadvantage that it will fail in cases where the > > interrupt parent

Re: [PATCH v2 08/10] of/platform: Resolve interrupt references at probe time

2013-10-24 Thread Grant Likely
On Wed, 16 Oct 2013 00:24:36 +0100, Grant Likely grant.lik...@linaro.org wrote: On Wed, 18 Sep 2013 15:24:50 +0200, Thierry Reding thierry.red...@gmail.com wrote: Interrupt references are currently resolved very early (when a device is created). This has the disadvantage that it will fail

Re: [PATCH v2 08/10] of/platform: Resolve interrupt references at probe time

2013-10-16 Thread Thierry Reding
On Wed, Oct 16, 2013 at 12:24:36AM +0100, Grant Likely wrote: > On Wed, 18 Sep 2013 15:24:50 +0200, Thierry Reding > wrote: > > Interrupt references are currently resolved very early (when a device is > > created). This has the disadvantage that it will fail in cases where the > > interrupt

Re: [PATCH v2 08/10] of/platform: Resolve interrupt references at probe time

2013-10-16 Thread Thierry Reding
On Wed, Oct 16, 2013 at 12:24:36AM +0100, Grant Likely wrote: On Wed, 18 Sep 2013 15:24:50 +0200, Thierry Reding thierry.red...@gmail.com wrote: Interrupt references are currently resolved very early (when a device is created). This has the disadvantage that it will fail in cases where the

Re: [PATCH v2 08/10] of/platform: Resolve interrupt references at probe time

2013-10-15 Thread Grant Likely
On Wed, 18 Sep 2013 15:24:50 +0200, Thierry Reding wrote: > Interrupt references are currently resolved very early (when a device is > created). This has the disadvantage that it will fail in cases where the > interrupt parent hasn't been probed and no IRQ domain for it has been > registered

Re: [PATCH v2 08/10] of/platform: Resolve interrupt references at probe time

2013-10-15 Thread Grant Likely
On Wed, 18 Sep 2013 15:24:50 +0200, Thierry Reding thierry.red...@gmail.com wrote: Interrupt references are currently resolved very early (when a device is created). This has the disadvantage that it will fail in cases where the interrupt parent hasn't been probed and no IRQ domain for it has

[PATCH v2 08/10] of/platform: Resolve interrupt references at probe time

2013-09-18 Thread Thierry Reding
Interrupt references are currently resolved very early (when a device is created). This has the disadvantage that it will fail in cases where the interrupt parent hasn't been probed and no IRQ domain for it has been registered yet. To work around that various drivers use explicit initcall ordering

[PATCH v2 08/10] of/platform: Resolve interrupt references at probe time

2013-09-18 Thread Thierry Reding
Interrupt references are currently resolved very early (when a device is created). This has the disadvantage that it will fail in cases where the interrupt parent hasn't been probed and no IRQ domain for it has been registered yet. To work around that various drivers use explicit initcall ordering