diff options
| author | Anatol Pomozov <anatol.pomozov@gmail.com> | 2013-05-08 19:56:16 -0400 |
|---|---|---|
| committer | Jiri Kosina <jkosina@suse.cz> | 2013-05-28 06:02:12 -0400 |
| commit | f884ab15afdc5514e88105c92a4e2e1e6539869a (patch) | |
| tree | 24d2bca7a44b4302ca30bdd460a222d677fe1e9b /Documentation/pinctrl.txt | |
| parent | 7e21f14d179ee8973a9b18552854c9934fcbe370 (diff) | |
doc: fix misspellings with 'codespell' tool
Signed-off-by: Anatol Pomozov <anatol.pomozov@gmail.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'Documentation/pinctrl.txt')
| -rw-r--r-- | Documentation/pinctrl.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/pinctrl.txt b/Documentation/pinctrl.txt index 447fd4cd54ec..d3c6d3dd7d4d 100644 --- a/Documentation/pinctrl.txt +++ b/Documentation/pinctrl.txt | |||
| @@ -298,7 +298,7 @@ Since the pin controller subsystem have its pinspace local to the pin | |||
| 298 | controller we need a mapping so that the pin control subsystem can figure out | 298 | controller we need a mapping so that the pin control subsystem can figure out |
| 299 | which pin controller handles control of a certain GPIO pin. Since a single | 299 | which pin controller handles control of a certain GPIO pin. Since a single |
| 300 | pin controller may be muxing several GPIO ranges (typically SoCs that have | 300 | pin controller may be muxing several GPIO ranges (typically SoCs that have |
| 301 | one set of pins but internally several GPIO silicon blocks, each modeled as | 301 | one set of pins but internally several GPIO silicon blocks, each modelled as |
| 302 | a struct gpio_chip) any number of GPIO ranges can be added to a pin controller | 302 | a struct gpio_chip) any number of GPIO ranges can be added to a pin controller |
| 303 | instance like this: | 303 | instance like this: |
| 304 | 304 | ||