From c9f3f2d8b3247b7e16b3cd66698e690ab4697301 Mon Sep 17 00:00:00 2001 From: Masanari Iida Date: Thu, 18 Jul 2013 01:29:12 +0900 Subject: doc: Fix typo in doucmentations Correct typo (double words) in documentations. Signed-off-by: Masanari Iida Acked-by: Randy Dunlap Signed-off-by: Jiri Kosina --- Documentation/arm/OMAP/omap_pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'Documentation/arm') diff --git a/Documentation/arm/OMAP/omap_pm b/Documentation/arm/OMAP/omap_pm index 9012bb039094..4ae915a9f899 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, -- cgit v1.2.3-59-g8ed1b