linux-kernel - Re: [PATCH v2 0/7] gpio: mockup: extensions for testing purposes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 6 Feb 2017 13:12:40 +0100
From:   Bartosz Golaszewski <bgolaszewski@...libre.com>
To:     Linus Walleij <linus.walleij@...aro.org>,
        Alexandre Courbot <gnurou@...il.com>,
        Bamvor Jian Zhang <bamvor.zhangjian@...aro.org>
Cc:     linux-gpio <linux-gpio@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Bartosz Golaszewski <bgolaszewski@...libre.com>
Subject: Re: [PATCH v2 0/7] gpio: mockup: extensions for testing purposes

2017-02-06 13:10 GMT+01:00 Bartosz Golaszewski <bgolaszewski@...libre.com>:
> I would like to create an automated test-suite for libgpiod, but
> the gpio-mockup driver is quite limited when it comes to current
> user space functionality - I can't test neither line event
> notifications nor finding GPIO lines by name.
>
> This series proposes to extend the gpio framework by allowing to
> inject line events from the kernel code and by providing a debugfs
> interface for that to the gpio-mockup driver. We also allow the
> user to request that the mockup driver name the lines.
>
> The first two patches only contain coding style changes which, I
> believe, will make the driver easier to maintain.
>
> The third patch adds the option to have the lines named.
>
> The fourth patch adds a devres flavor of irq_alloc_descs() to be used
> in patch 5, which actually adds the dummy irqchip.
>
> The last two patches implement the debugfs directory structure that
> can be used by the user space to inject line events.
>
> v1 -> v2:
> - made the event injection self-contained within the driver by using
>   the irq_work as suggested by Lars-Peter Clauses

s/ Lars-Peter Clauses/ Lars-Peter Clausen/

sorry!

Thanks,
Bartosz