Date: Wed, 5 Sep 2012 08:17:48 -0400 From: John Baldwin <jhb@freebsd.org> To: Warner Losh <imp@bsdimp.com> Cc: freebsd-hackers@freebsd.org, freebsd-arm@freebsd.org, Aleksander Dutkowski <aleek@freebsd.org> Subject: Re: availability of interrupts during bootup process Message-ID: <201209050817.48698.jhb@freebsd.org> In-Reply-To: <13628135-18C7-4D98-B2DC-60C8AB65A643@bsdimp.com> References: <CABkKHSbCwiZsRU=J_6EwvhkO63W2vLpgkgEhkDJ%2BdxtsSZez2A@mail.gmail.com> <201209041205.19794.jhb@freebsd.org> <13628135-18C7-4D98-B2DC-60C8AB65A643@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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). > >> 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 configured during device attaching, because usb > >> ehci driver depends on it. > >> Is it possbile? I've tried it but it hangs on waiting for i2c > >> interrupt, but someone told me, that interrupts are available during > >> bootup for some time. > > > > No, interrupts do not work during bootup. If you can poll your hardware > > you could use polling until interrupts are enabled (using 'if (cold)' to > > check for the boot time before interrupts are enabled). > > Are interrupts off, or ithreads not scheduled? I thought I had some stuff > working that needed interrupts, but didn't need scheduling.. Am I nuts? No, that's correct. Filters will work, just not scheduling. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201209050817.48698.jhb>