Even though the wifi-only model has nothing attached to ehci3, the
driver still needs to be probed. This is because the USB register
settings are lost in LP0. So currently after the device resumes from
LP0 the first time, the current drain is 12mA higher! When the
ehci3 driver is present, its resume code runs and restores the
registers to a known good state, which solves the power management
issue.
Change-Id: I6329704f7a1161eb139b62002a50085eb05d2fdc
Signed-off-by: Greg Meiste <w30289@motorola.com>
if (!(factorycable && mot_boot_recovery))
platform_device_register(&tegra_udc_device);
- if (stingray_hw_has_cdma()) {
+ if (stingray_hw_has_cdma())
platform_device_register(&tegra_ehci2_device);
- platform_device_register(&tegra_ehci3_device);
- }
+
+ platform_device_register(&tegra_ehci3_device);
#ifdef CONFIG_USB_ANDROID_RNDIS
src = usb_serial_num;