From owner-soc-status@freebsd.org Thu Jun 7 09:48:44 2018 Return-Path: Delivered-To: soc-status@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4BD5FFDE190 for ; Thu, 7 Jun 2018 09:48:44 +0000 (UTC) (envelope-from uddka@student.kit.edu) Received: from scc-mailout-kit-02.scc.kit.edu (scc-mailout-kit-02.scc.kit.edu [IPv6:2a00:1398:9:f712::810d:e752]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CB93987FFB; Thu, 7 Jun 2018 09:48:43 +0000 (UTC) (envelope-from uddka@student.kit.edu) Received: from tr-v1239-fse.scc.kit.edu ([129.13.74.14] helo=server-01.fs-etec.kit.edu) by scc-mailout-kit-02.scc.kit.edu with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (envelope-from ) id 1fQrX6-0006v7-J9; Thu, 07 Jun 2018 11:48:42 +0200 Received: from Chris-TP.fritz.box (p200300D2EF11B7005CB746157775E90D.dip0.t-ipconnect.de [IPv6:2003:d2:ef11:b700:5cb7:4615:7775:e90d]) by server-01.fs-etec.kit.edu (Postfix) with ESMTPSA id 17EE0759; Thu, 7 Jun 2018 11:48:40 +0200 (CEST) Date: Thu, 7 Jun 2018 11:48:22 +0200 From: Christian =?ISO-8859-1?Q?Kr=E4mer?= To: soc-status@freebsd.org Cc: Chuck Tuffli , Luiz Otavio O Souza Subject: User space interface for GPIO interrupts / Status Report Week 3 Message-Id: <20180607114822.bd3dfebc6827848abc994e69@student.kit.edu> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: soc-status@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Summer of Code Status Reports and Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2018 09:48:44 -0000 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] [2]