Date: Tue, 22 May 2018 12:06:34 +0200 From: Christian =?ISO-8859-1?Q?Kr=E4mer?= <uddka@student.kit.edu> To: soc-status@freebsd.org Subject: User space interface for GPIO interrupts / Status Report Week 1 Message-ID: <20180522120634.05263479f27c0783fe79482d@student.kit.edu>
next in thread | raw e-mail | index | archive | help
Dear all, during last week I implemented an initial version of the device driver that registers an interrupt on a specific GPIO pin and creates a character device as interface into the user space. The driver blocks any read() syscall until an interrupt on the monitored pin is triggered. The source code can be found on GitHub [1]. A very simple example of usage in the shell can look like this: $ cat /dev/gpiointr0 && echo Interrupt triggered The configuration is currently (still) static. While the actual pin is defined in the DTS file, the edge of the interrupt trigger is hard coded in the source of the driver). During this week I will start to implement the dynamic configuration of the driver during runtime and write some user space utilities for testing. Thanks, Chris [1] <https://github.com/ckraemer/freebsd/tree/gsoc2018>;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180522120634.05263479f27c0783fe79482d>