Date: Thu, 5 Jul 2018 09:07:15 +0200 From: Christian =?ISO-8859-1?Q?Kr=E4mer?= <uddka@student.kit.edu> To: soc-status@freebsd.org Cc: Chuck Tuffli <chuck@freebsd.org>, Luiz Otavio O Souza <loos.br@gmail.com> Subject: User space interface for GPIO interrupts / Status Report Weeks 6+7 Message-ID: <20180705090715.cd9063a3c897ed9872885ffd@student.kit.edu>
next in thread | raw e-mail | index | archive | help
Hi all, during the last two weeks I implemented the second part of the long-term test, which is an utility that replays the same PRNG as the interrupt source and predicts when the next interrupt should occur. I also added some functions to libgpio to handle the driver and modified the configuration utility in order to use these functions instead of calling ioctl() directly. Currently I am still working on the pin distinction which requires changes to many parts of the driver, but this should be done after this week. The configuration will be sticked to the file descriptor. I also took a closer look at asynchronous I/O and did some tests, but currently only unsafe AIO is possible, because the read() syscall does always block. Due to this the implementation of the read() syscall will be changed to allow non-blocking calls also. The source code of the driver can be found in my fork of the FreeBSD src tree on GitHub [1]. The utilities for configuration and testing are located in a separate repository [2]. Regards, Chris [1] <https://github.com/ckraemer/freebsd/tree/gsoc2018>; [2] <https://github.com/ckraemer/gsoc2018-utils>;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180705090715.cd9063a3c897ed9872885ffd>