On Sun, Jul 10, 2016 at 12:01:29AM +0200, Marcus Glocker wrote: > On Sat, Jul 09, 2016 at 10:24:59PM +0200, Mark Kettenis wrote: > > > > Date: Sat, 9 Jul 2016 22:07:16 +0200 > > > From: Marcus Glocker <mar...@nazgul.ch> > > > > > > On every boot on my G5 the 'smu-pulsar' node hangs for around 66 seconds > > > in autoconfs config_search() it seems before the boot process continues: > > > > > > "smu-pulsar" at iic2 addr 0x6a not configured > > > > > > I don't know why. > > > > > > Anyone else seeing this with a 'smu-pulsar' node in his FDT? > > > Anything speaking against it to skip it from autoconf for now, similar > > > as we already do for 'deq' and 'tas3004'? > > > > That makes no sense. The delay is in no way related to this > > "smu-pulsar" device. As the "not configured" message indicates, we > > don't have a driver for this device. All your diff does is eliminate > > that message. The delay will still be there. > > With this diff the delay is gone. > > But as said, I don't understand yet where it exactly happens.
It seems the issue is because iic attaches to smu before smu_attach() has finished. Then iic starts to scan for devices while smu is still doing stuff in smu_attach(). Probably the hang happens somewhere in smu_do_cmd(). I don't know if it would be an option to use config_defer() for iic?
