linux-kernel - Re: [PATCH 0/2] Fix LED GPIO trigger behavior

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]

Date:   Fri, 17 May 2019 18:56:17 +0200
From:   Jacek Anaszewski <jacek.anaszewski@...il.com>
To:     Kun Yi <kunyi@...gle.com>, linux-leds@...r.kernel.org
Cc:     pavel@....cz, dmurphy@...com, u.kleine-koenig@...gutronix.de,
        linux-kernel@...r.kernel.org,
        Linus Walleij <linus.walleij@...aro.org>,
        "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>
Subject: Re: [PATCH 0/2] Fix LED GPIO trigger behavior

Cc Linus Walleij and leds-gpio@...r.kernel.org.

On 5/16/19 11:42 PM, Kun Yi wrote:
> *** BLURB HERE ***
> Hello there,
> 
> I recently tested ledtrig-gpio on an embedded controller and one of the
> issues I had involve not requesting the user input pin as GPIO.
> 
> In many embedded systems, a pin could be muxed as several functions, and
> requesting the pin as GPIO is necessary to let pinmux select the pin as
> a GPIO instead of, say an I2C pin. I'd like to learn whether it is appropriate
> to assume user of ledtrig-gpio really intends to use GPIOs and not some
> weird pins that are used as other functions.
> 
> Kun Yi (2):
>    ledtrig-gpio: Request user input pin as GPIO
>    ledtrig-gpio: 0 is a valid GPIO number
> 
>   drivers/leds/trigger/ledtrig-gpio.c | 35 ++++++++++++++++++++---------
>   1 file changed, 24 insertions(+), 11 deletions(-)
> 

-- 
Best regards,
Jacek Anaszewski