Date: Thu, 7 Jun 2018 11:48:22 +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 Week 3 Message-ID: <20180607114822.bd3dfebc6827848abc994e69@student.kit.edu>
index | next in thread | raw e-mail
Hi, this time my status report is unfortunately somewhat delayed, but here are proceedings of the last week: I managed to realise trigger type configuration during runtime and started to implement a handler for the poll() syscall. It is now also possible to configure multiple pins at once, each one with a different trigger type. The plan for this week is to fix the remaining issues with the poll() syscall, along with some other minor issues and prepare a concept for a convenient interface of the driver that allows distinction which of the configured pins was actually triggered. I will also spend some time on working out a suitable scenario for automated long-term tests. 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 the following repository [2]. Regards, Chris [1] <https://github.com/ckraemer/gsoc2018-utils>; [2] <https://github.com/ckraemer/freebsd/tree/gsoc2018>;home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180607114822.bd3dfebc6827848abc994e69>