User space interface for GPIO interrupts

[Maverick Kuo]

Sorry, I got it wrong, gpio interrupt is really available, BUT I forgot, I
have a patched from https://github.com/ckraemer/freebsd/tree/gsoc2018

Just after the comparison was revised, I found out that I apologize again.

Regards,
Chris

Maverick Kuo <maverick.kuo at gmail.com> 於 2019年6月3日 週一 下午4:00寫道：

> 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 at gmail.com> 於 2019年6月3日 週一 下午2:56寫道：
>
>> 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 =>>
>> 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
>>
>