Browse Source

pinctrl: s/have/has/ in GPIO driver interaction description

Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Andrew Jeffery 9 years ago
parent
commit
eef06737e5
1 changed files with 1 additions and 1 deletions
  1. 1 1
      Documentation/pinctrl.txt

+ 1 - 1
Documentation/pinctrl.txt

@@ -286,7 +286,7 @@ see the section named "pin control requests from drivers" and
 "drivers needing both pin control and GPIOs" below for details. But in some
 "drivers needing both pin control and GPIOs" below for details. But in some
 situations a cross-subsystem mapping between pins and GPIOs is needed.
 situations a cross-subsystem mapping between pins and GPIOs is needed.
 
 
-Since the pin controller subsystem have its pinspace local to the pin
+Since the pin controller subsystem has its pinspace local to the pin
 controller we need a mapping so that the pin control subsystem can figure out
 controller we need a mapping so that the pin control subsystem can figure out
 which pin controller handles control of a certain GPIO pin. Since a single
 which pin controller handles control of a certain GPIO pin. Since a single
 pin controller may be muxing several GPIO ranges (typically SoCs that have
 pin controller may be muxing several GPIO ranges (typically SoCs that have