linux-kernel - Re: [PATCH v3] gpiolib: Take MUX usage into account

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, 19 Aug 2019 21:27:03 +0200
From:   Stefan Wahren <stefan.wahren@...e.com>
To:     Ramon Fried <ramon.fried@...ux.intel.com>,
        linus.walleij@...aro.org, bgolaszewski@...libre.com
Cc:     linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] gpiolib: Take MUX usage into account

Am 14.08.19 um 13:00 schrieb Ramon Fried:
> From: Stefan Wahren <stefan.wahren@...e.com>
>
> The user space like gpioinfo only see the GPIO usage but not the
> MUX usage (e.g. I2C or SPI usage) of a pin. As a user we want to know which
> pin is free/safe to use. So take the MUX usage of strict pinmux controllers
> into account to get a more realistic view for ioctl GPIO_GET_LINEINFO_IOCTL.
>
> Signed-off-by: Stefan Wahren <stefan.wahren@...e.com>
> Tested-by: Ramon Fried <rfried.dev@...il.com>
> Signed-off-by: Ramon Fried <rfried.dev@...il.com>
Acked-by: Stefan Wahren <stefan.wahren@...e.com>