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] [day] [month] [year] [list]

Message-ID: <CACRpkda7_YP7FC0e4JnaXJNB_aGMFbNdjN8kdKfHZ0LVnkyopg@mail.gmail.com>
Date:   Fri, 23 Aug 2019 11:11:33 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Ramon Fried <ramon.fried@...ux.intel.com>
Cc:     Bartosz Golaszewski <bgolaszewski@...libre.com>,
        Stefan Wahren <stefan.wahren@...e.com>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] gpiolib: Take MUX usage into account

On Wed, Aug 14, 2019 at 1:01 PM Ramon Fried <ramon.fried@...ux.intel.com> wrote:

> 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>
> ---
> v3:
> * Remove the debug message and replace with comment in code.

This V3 version applied to the pinctrl tree for testing with
Stefan's ACK.

Thanks for hashing this out.

Yours,
Linus Walleij