Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Jun 2019 21:44:22 +0200
From:      Peter Blok <pblok@bsd4all.org>
To:        Maverick Kuo <maverick.kuo@gmail.com>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: User space interface for GPIO interrupts
Message-ID:  <454A5736-7B40-447A-8ED7-8C7A5CDE650F@bsd4all.org>
In-Reply-To: <CAEKjv0D3YO8_j2NvTA9o9Wfxp=xA4eu0b=JFfLc_JoBGYB7fDw@mail.gmail.com>
References:  <CAEKjv0BN%2BA16AeVfb0e0COS-8FH-bsXqd5MsS65U%2BFT=EW9gmw@mail.gmail.com> <CAEKjv0D6V77RRnMhfJp13gPtwiT33SdVnN==WN6Mb4Q6htrOpQ@mail.gmail.com> <CAEKjv0D3YO8_j2NvTA9o9Wfxp=xA4eu0b=JFfLc_JoBGYB7fDw@mail.gmail.com>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
Hi Chris,

Do you have an example or any documentation how to use kqueue with interrupts?

Peter

> On 3 Jun 2019, at 11:46, Maverick Kuo <maverick.kuo@gmail.com> wrote:
> 
> 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@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@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
>>> 
>> 
> _______________________________________________
> freebsd-arm@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"


[-- Attachment #2 --]
0	*H
010
	`He0	*H
 00l"ϫmW0
	*H
010	UGB10UGreater Manchester10USalford10U
COMODO CA Limited1=0;U4COMODO RSA Client Authentication and Secure Email CA0
180414000000Z
210413235959Z0D10	UNL10U
Peter Blok1 0	*H
	pblok@bsd4all.org0"0
	*H
0
O޾̴͚UFkڅUĈIG΂m2C:C<&㎎ְkx҃M\xiKdD<eb#ۨ>EgN YFNU5
4dȬZ

T.~qt#2^A
^|<2G"plj84I(ARٝ*WHPdvKۑsY,pyM/ٔUاO)`nj90sn%ԛ00U#0la|=+qH^ċ0U\Yx%Z&?^0U0U00U%0++0FU ?0=0;+10+0)+https://secure.comodo.net/CPS0ZUS0Q0OMKIhttp://crl.comodoca.com/COMODORSAClientAuthenticationandSecureEmailCA.crl0+0}0U+0Ihttp://crt.comodoca.com/COMODORSAClientAuthenticationandSecureEmailCA.crt0$+0http://ocsp.comodoca.com0
	*H
e5pm| Z3"2pgX*<θQD0.1TFu3Bqϙ}')uao."YTcRa8yv4>Yv;?K(Z7?kNZY6o0,0=։ϣK_yv6c]R3ѵrʀNξK)k
?bD'vnoDkRO3{$H
4uD!100010	UGB10UGreater Manchester10USalford10U
COMODO CA Limited1=0;U4COMODO RSA Client Authentication and Secure Email CAl"ϫmW0
	`He0	*H
	1	*H
0	*H
	1
190625194423Z0/	*H
	1" lQK
RNFW/+0	+710010	UGB10UGreater Manchester10USalford10U
COMODO CA Limited1=0;U4COMODO RSA Client Authentication and Secure Email CAl"ϫmW0*H
	1010	UGB10UGreater Manchester10USalford10U
COMODO CA Limited1=0;U4COMODO RSA Client Authentication and Secure Email CAl"ϫmW0
	*H
~4\JI=a,NMR`PT_j3xP9f5#xWtd;X"='`YLQ"0O!F82[!
B	9Ts~w,}pbuQn=EH:Npyp#d!&qQ)!.۠8*>vs	;Yl_k ZwU@wՅݻ"g.|&qJ_	"
help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?454A5736-7B40-447A-8ED7-8C7A5CDE650F>