diff options
| author | Masanari Iida <standby24x7@gmail.com> | 2013-07-18 01:29:12 +0900 |
|---|---|---|
| committer | Jiri Kosina <jkosina@suse.cz> | 2013-07-25 12:34:15 +0200 |
| commit | c9f3f2d8b3247b7e16b3cd66698e690ab4697301 (patch) | |
| tree | 99249f76975e1371f915c4c04eeca4c97674d86b /Documentation/arm | |
| parent | 30abda170be7cbd9bce9a7026ce83ce1f74c0e7a (diff) | |
doc: Fix typo in doucmentations
Correct typo (double words) in documentations.
Signed-off-by: Masanari Iida <standby24x7@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'Documentation/arm')
| -rw-r--r-- | Documentation/arm/OMAP/omap_pm | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/arm/OMAP/omap_pm b/Documentation/arm/OMAP/omap_pm index 9012bb03909..4ae915a9f89 100644 --- a/Documentation/arm/OMAP/omap_pm +++ b/Documentation/arm/OMAP/omap_pm @@ -78,7 +78,7 @@ to NULL. Drivers should use the following idiom: The most common usage of these functions will probably be to specify the maximum time from when an interrupt occurs, to when the device becomes accessible. To accomplish this, driver writers should use the -set_max_mpu_wakeup_lat() function to to constrain the MPU wakeup +set_max_mpu_wakeup_lat() function to constrain the MPU wakeup latency, and the set_max_dev_wakeup_lat() function to constrain the device wakeup latency (from clk_enable() to accessibility). For example, |