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 the
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 ha
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 paren
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 yet.
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
