linux-kernel - Re: [PATCH] Documentation: gpio: clarify sysfs line values are logical

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: Wed, 14 Feb 2024 10:29:24 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Kent Gibson <warthog618@...il.com>
Cc: linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org, 
	linux-doc@...r.kernel.org, linus.walleij@...aro.org, andy@...nel.org, 
	corbet@....net
Subject: Re: [PATCH] Documentation: gpio: clarify sysfs line values are logical

On Mon, Feb 12, 2024 at 10:34 AM Kent Gibson <warthog618@...il.com> wrote:
>
> Clarify that line values are logical, not physical, by replacing high/low
> terminology with active/inactive.
>
> Signed-off-by: Kent Gibson <warthog618@...il.com>
> ---
>  Documentation/userspace-api/gpio/sysfs.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/userspace-api/gpio/sysfs.rst b/Documentation/userspace-api/gpio/sysfs.rst
> index e12037a0f2b4..116921048b18 100644
> --- a/Documentation/userspace-api/gpio/sysfs.rst
> +++ b/Documentation/userspace-api/gpio/sysfs.rst
> @@ -87,9 +87,9 @@ and have the following read/write attributes:
>                 allow userspace to reconfigure this GPIO's direction.
>
>         "value" ...
> -               reads as either 0 (low) or 1 (high). If the GPIO
> +               reads as either 0 (inactive) or 1 (active). If the GPIO
>                 is configured as an output, this value may be written;
> -               any nonzero value is treated as high.
> +               any nonzero value is treated as active.
>
>                 If the pin can be configured as interrupt-generating interrupt
>                 and if it has been configured to generate interrupts (see the
> --
> 2.39.2
>

Applied, thanks!

Bart