Commit bfc9dcab authored by Dominik D. Geyer's avatar Dominik D. Geyer Committed by Linus Torvalds

correct gpio.txt typos

Corrected sysfs gpio chip node name and fixed punctuation.
Signed-off-by: default avatarDominik D. Geyer <dominik.geyer@gmx.de>
Signed-off-by: default avatarRandy Dunlap <randy.dunlap@oracle.com>
Cc: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
parent 2770f189
...@@ -380,7 +380,7 @@ rare; use gpiochip_remove() when it is unavoidable. ...@@ -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 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, 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 Any debugfs dump method should normally ignore signals which haven't been
requested as GPIOs. They can use gpiochip_is_requested(), which returns requested as GPIOs. They can use gpiochip_is_requested(), which returns
...@@ -531,7 +531,7 @@ and have the following read/write attributes: ...@@ -531,7 +531,7 @@ and have the following read/write attributes:
This file exists only if the pin can be configured as an This file exists only if the pin can be configured as an
interrupt generating input pin. 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 controller implementing GPIOs starting at #42) and have the following
read-only attributes: read-only attributes:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment