usb: host: tegra: defer ehci cpu freq. boost work

Delayed work is getting executed even before DVFS initialization
(which happens in late_initcall after all devices initialization
has completed). So device fails in changing the CPU rate, as
regulator is still not present, with following warning -

"Increasing CPU rate while regulator is not ready is not allowed"

Currently DVFS initialization, initializes both CPU and Core, and
only Core is dependent on completion of device initialization.
So ideally CPU init. can be done much earlier which will resolve
this issue. This is still under discussion.

This patch defers the cpu rate change by ehci even further so that
DVFS initialization gets completed before pm_qos_update_request.

Bug 1352877

Change-Id: Ia21af01c4bc915e1120fc72917428d9fdc26b38d
Signed-off-by: Shreshtha Sahu <ssahu@nvidia.com>
Reviewed-on: http://git-master/r/304198
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Rakesh Babu Bodla <rbodla@nvidia.com>
Reviewed-by: Venkat Moganty <vmoganty@nvidia.com>

diff --git a/drivers/usb/host/ehci-tegra.c b/drivers/usb/host/ehci-tegra.c
index 09824a8c3b3c726ef7a04225b732ba0fe9734535..09cd1b2ce93a895634e75a0dbcffae2e2ffb312a 100644 (file)
--- a/drivers/usb/host/ehci-tegra.c
+++ b/drivers/usb/host/ehci-tegra.c
@@ -647,7 +647,7 @@ static int tegra_ehci_probe(struct platform_device *pdev)
                                        tegra_ehci_boost_cpu_frequency_work);
        pm_qos_add_request(&tegra->boost_cpu_freq_req, PM_QOS_CPU_FREQ_MIN,
                                        PM_QOS_DEFAULT_VALUE);
-       schedule_delayed_work(&tegra->boost_cpu_freq_work, 4000);
+       schedule_delayed_work(&tegra->boost_cpu_freq_work, 12000);
        tegra->cpu_boost_in_work = true;
 #endif