aboutsummaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/arm/omap
diff options
context:
space:
mode:
authorMasanari Iida <standby24x7@gmail.com>2012-03-04 23:16:11 +0900
committerJiri Kosina <jkosina@suse.cz>2012-03-07 16:08:24 +0100
commit40e47125e6c5110383b0176d7b9d530f2936b1ae (patch)
tree9653ac1f586cbfe36286c2d987c9330078eb37ad /Documentation/devicetree/bindings/arm/omap
parent4e70daaf05a181b6968e29e72e9f1c16a183e92c (diff)
Documentation: Fix multiple typo in Documentation
Signed-off-by: Masanari Iida <standby24x7@gmail.com> Acked-by: Randy Dunlap <rdunlap@xenotime.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'Documentation/devicetree/bindings/arm/omap')
-rw-r--r--Documentation/devicetree/bindings/arm/omap/omap.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/devicetree/bindings/arm/omap/omap.txt b/Documentation/devicetree/bindings/arm/omap/omap.txt
index dbdab40ed3a..edc618a8aab 100644
--- a/Documentation/devicetree/bindings/arm/omap/omap.txt
+++ b/Documentation/devicetree/bindings/arm/omap/omap.txt
@@ -5,7 +5,7 @@ IPs present in the SoC.
On top of that an omap_device is created to extend the platform_device
capabilities and to allow binding with one or several hwmods.
The hwmods will contain all the information to build the device:
-adresse range, irq lines, dma lines, interconnect, PRCM register,
+address range, irq lines, dma lines, interconnect, PRCM register,
clock domain, input clocks.
For the moment just point to the existing hwmod, the next step will be
to move data from hwmod to device-tree representation.