RE: status of USB on omap35xx ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Paul

>-----Original Message-----
>From: Paul Walmsley [mailto:paul@xxxxxxxxx]
>Sent: Thursday, December 11, 2008 12:15 PM
>To: Pandita, Vikram
>Cc: Steve Sakoman; Tony Lindgren; linux-omap; David Brownell; me@xxxxxxxxxxxxxxx; Jeff Steele
>Subject: Re: status of USB on omap35xx ?
>
>Hi Vikram,
>
>looking at ehci-omap.c lines 190-204.  Is there some reason why the
>USBHOST clockdomain needs to be in software-supervised mode?  Also, is
>there some reason why the interface clock must be prevented from
>auto-idling?  This will cause problems with power management.

All these checks were in place for initial debugging. 
There is no need to keep these check now.

>
>
>- Paul
>
>	/* PRCM settings for USBHOST:
>	 * Interface clk un-related to domain transition
>	 */
>	cm_write_mod_reg(0 << OMAP3430ES2_AUTO_USBHOST_SHIFT,
>				OMAP3430ES2_USBHOST_MOD, CM_AUTOIDLE);
>
>	/* Disable sleep dependency with MPU and IVA */
>	cm_write_mod_reg((0 << OMAP3430ES2_EN_MPU_SHIFT) |
>				(0 << OMAP3430ES2_EN_IVA2_SHIFT),
>				OMAP3430ES2_USBHOST_MOD, OMAP3430_CM_SLEEPDEP);
>
>	/* Disable Automatic transition of clock */
>	cm_write_mod_reg(0 << OMAP3430ES2_CLKTRCTRL_USBHOST_SHIFT,
>				OMAP3430ES2_USBHOST_MOD, CM_CLKSTCTRL);
>
>
>
>

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux