path: root/Documentation
diff options
authorDominik D. Geyer <dominik.geyer@gmx.de>2009-12-06 18:30:44 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2009-12-09 18:59:52 -0800
commitbfc9dcabd513334c1d888ab66f7b7d84a3159571 (patch)
tree66638fc446addaef69f9d9e0578e41bb3418a5b9 /Documentation
parent2770f189b7a5582869c137e5617fb88cc0ad0fd3 (diff)
correct gpio.txt typos
Corrected sysfs gpio chip node name and fixed punctuation. Signed-off-by: Dominik D. Geyer <dominik.geyer@gmx.de> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com> Cc: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation')
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/gpio.txt b/Documentation/gpio.txt
index fa4dc077ae0e..e4e7daed2ba8 100644
--- a/Documentation/gpio.txt
+++ b/Documentation/gpio.txt
@@ -380,7 +380,7 @@ rare; use gpiochip_remove() when it is unavoidable.
Most often a gpio_chip is part of an instance-specific structure with state
not exposed by the GPIO interfaces, such as addressing, power management,
-and more. Chips such as codecs will have complex non-GPIO state,
+and more. Chips such as codecs will have complex non-GPIO state.
Any debugfs dump method should normally ignore signals which haven't been
requested as GPIOs. They can use gpiochip_is_requested(), which returns
@@ -531,7 +531,7 @@ and have the following read/write attributes:
This file exists only if the pin can be configured as an
interrupt generating input pin.
-GPIO controllers have paths like /sys/class/gpio/chipchip42/ (for the
+GPIO controllers have paths like /sys/class/gpio/gpiochip42/ (for the
controller implementing GPIOs starting at #42) and have the following
read-only attributes: