Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 4 Sep 2012 12:05:19 -0400
From:      John Baldwin <jhb@freebsd.org>
To:        freebsd-hackers@freebsd.org
Cc:        freebsd-arm@freebsd.org, Aleksander Dutkowski <aleek@freebsd.org>
Subject:   Re: availability of interrupts during bootup process
Message-ID:  <201209041205.19794.jhb@freebsd.org>
In-Reply-To: <CABkKHSbCwiZsRU=J_6EwvhkO63W2vLpgkgEhkDJ%2BdxtsSZez2A@mail.gmail.com>
References:  <CABkKHSbCwiZsRU=J_6EwvhkO63W2vLpgkgEhkDJ%2BdxtsSZez2A@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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).

-- 
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201209041205.19794.jhb>