Date: Mon, 3 Jun 2019 16:00:17 +0800 From: Maverick Kuo <maverick.kuo@gmail.com> To: freebsd-arm@freebsd.org Subject: Re: User space interface for GPIO interrupts Message-ID: <CAEKjv0D6V77RRnMhfJp13gPtwiT33SdVnN==WN6Mb4Q6htrOpQ@mail.gmail.com> In-Reply-To: <CAEKjv0BN%2BA16AeVfb0e0COS-8FH-bsXqd5MsS65U%2BFT=EW9gmw@mail.gmail.com> References: <CAEKjv0BN%2BA16AeVfb0e0COS-8FH-bsXqd5MsS65U%2BFT=EW9gmw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Good News !! after cvs to 12.0-STABLE #0 r348527M GPIO Interrupt with kqueue Works !!! Thanks to the developers :) Regards, Chris Maverick Kuo <maverick.kuo@gmail.com> =E6=96=BC 2019=E5=B9=B46=E6=9C=883=E6= =97=A5 =E9=80=B1=E4=B8=80 =E4=B8=8B=E5=8D=882:56=E5=AF=AB=E9=81=93=EF=BC=9A > Hi, > > i am running 12.0-STABLE r348448 arm64 on raspberry pi3 b+. > > Look at the kernel and it seems that all the functions related to gpio > interrupt are available. > > System startup process > Bcm_gpio_intr_attach =3D>> > Bus_setup_intr > ?? bcm_gpio_intr_bank[0,1] > ?? bcm_gpio_intr_internal > > It seems that BCM_GPIO_GPEDS (Event Status) will be read in the > bcm_gpio_intr_internal function but it is not executed there. > > am I missed that part?? > > Let users use kqueue/kevent to monitor gpio interrupt to reduce cpu load. > > Regards, > Chris >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAEKjv0D6V77RRnMhfJp13gPtwiT33SdVnN==WN6Mb4Q6htrOpQ>