From: Dirk Behme <dirk.behme@gmail.com>
To: linux-gpio@vger.kernel.org
Cc: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <acourbot@nvidia.com>,
Dirk Behme <dirk.behme@gmail.com>
Subject: [PATCH] Documentation: gpiolib: sysfs: high can be any nonzero value
Date: Wed, 22 Apr 2015 18:39:46 +0200 [thread overview]
Message-ID: <1429720786-6277-1-git-send-email-dirk.behme@gmail.com> (raw)
With the commit 79a9becda8940d ("gpiolib: export descriptor-based
GPIO interface") the gpiolib can return any nonzero value for high.
Not only 1. Correct this in the documentation.
Signed-off-by: Dirk Behme <dirk.behme@gmail.com>
---
Note: Commit 79a9becda8940d has been merged in v3.13. If this
patch is considered to be fine, please think about applying
it to -stable >= v3.14, too.
Documentation/gpio/sysfs.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/gpio/sysfs.txt b/Documentation/gpio/sysfs.txt
index c2c3a97..bc7f31d 100644
--- a/Documentation/gpio/sysfs.txt
+++ b/Documentation/gpio/sysfs.txt
@@ -69,7 +69,7 @@ and have the following read/write attributes:
it was exported by kernel code that didn't explicitly
allow userspace to reconfigure this GPIO's direction.
- "value" ... reads as either 0 (low) or 1 (high). If the GPIO
+ "value" ... reads as either 0 (low) or nonzero (high). If the GPIO
is configured as an output, this value may be written;
any nonzero value is treated as high.
--
2.3.6
next reply other threads:[~2015-04-22 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 16:39 Dirk Behme [this message]
2015-04-22 17:10 ` [PATCH] Documentation: gpiolib: sysfs: high can be any nonzero value Johan Hovold
2015-04-22 21:12 ` Vladimir Zapolskiy
2015-05-02 16:36 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1429720786-6277-1-git-send-email-dirk.behme@gmail.com \
--to=dirk.behme@gmail.com \
--cc=acourbot@nvidia.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox