Re: availability of interrupts during bootup process

2012-09-05 Thread John Baldwin
On Tuesday, September 04, 2012 9:30:08 pm Warner Losh wrote: > > On Sep 4, 2012, at 10:05 AM, John Baldwin wrote: > > > On Sunday, September 02, 2012 5:31:21 pm Aleksander Dutkowski wrote: > >> hello! > >> > >> I have PMIC (TWL4030) module connected to the SoC (ARM/OMAP3) via i2c > > (iicbus).

Re: availability of interrupts during bootup process

2012-09-04 Thread Warner Losh
On Sep 4, 2012, at 10:05 AM, John Baldwin wrote: > On Sunday, September 02, 2012 5:31:21 pm Aleksander Dutkowski wrote: >> hello! >> >> I have PMIC (TWL4030) module connected to the SoC (ARM/OMAP3) via i2c > (iicbus). >> Current solution is that i2c_attach calls bus_generic_attach(dev); >> whic

Re: availability of interrupts during bootup process

2012-09-04 Thread John Baldwin
On Sunday, September 02, 2012 5:31:21 pm Aleksander Dutkowski wrote: > hello! > > I have PMIC (TWL4030) module connected to the SoC (ARM/OMAP3) via i2c (iicbus). > Current solution is that i2c_attach calls bus_generic_attach(dev); > which calls my pmic probe/attach functions, but main configurati

availability of interrupts during bootup process

2012-09-02 Thread Aleksander Dutkowski
hello! I have PMIC (TWL4030) module connected to the SoC (ARM/OMAP3) via i2c (iicbus). Current solution is that i2c_attach calls bus_generic_attach(dev); which calls my pmic probe/attach functions, but main configuration of PMIC in done after drivers setup by config_intrhook. But I need it to be c