b8f15b7e1d
Increase the timeout for disabling an IP block to five milliseconds. This is to handle the usb_host_fs idle latency, which takes almost four milliseconds after a host controller reset. This is the second of two patches needed to resolve the following boot warning: omap_hwmod: usb_host_fs: _wait_target_disable failed Thanks to Sergei Shtylyov <sshtylyov@mvista.com> for finding an unrelated hunk in a previous version of this patch. Signed-off-by: Paul Walmsley <paul@pwsan.com> Cc: Sergei Shtylyov <sshtylyov@mvista.com> Cc: Tero Kristo <t-kristo@ti.com>
36 lines
1.2 KiB
C
36 lines
1.2 KiB
C
/*
|
|
* OMAP2+ Clock Management prototypes
|
|
*
|
|
* Copyright (C) 2007-2009 Texas Instruments, Inc.
|
|
* Copyright (C) 2007-2009 Nokia Corporation
|
|
*
|
|
* Written by Paul Walmsley
|
|
*
|
|
* This program is free software; you can redistribute it and/or modify
|
|
* it under the terms of the GNU General Public License version 2 as
|
|
* published by the Free Software Foundation.
|
|
*/
|
|
#ifndef __ARCH_ASM_MACH_OMAP2_CM_H
|
|
#define __ARCH_ASM_MACH_OMAP2_CM_H
|
|
|
|
/*
|
|
* MAX_MODULE_READY_TIME: max duration in microseconds to wait for the
|
|
* PRCM to request that a module exit the inactive state in the case of
|
|
* OMAP2 & 3.
|
|
* In the case of OMAP4 this is the max duration in microseconds for the
|
|
* module to reach the functionnal state from an inactive state.
|
|
*/
|
|
#define MAX_MODULE_READY_TIME 2000
|
|
|
|
/*
|
|
* MAX_MODULE_DISABLE_TIME: max duration in microseconds to wait for
|
|
* the PRCM to request that a module enter the inactive state in the
|
|
* case of OMAP2 & 3. In the case of OMAP4 this is the max duration
|
|
* in microseconds for the module to reach the inactive state from
|
|
* a functional state.
|
|
* XXX FSUSB on OMAP4430 takes ~4ms to idle after reset during
|
|
* kernel init.
|
|
*/
|
|
#define MAX_MODULE_DISABLE_TIME 5000
|
|
|
|
#endif
|