On Fri, Jan 17, 2014 at 12:26:50PM -0600, Josh Cartwright wrote:
On Fri, Jan 17, 2014 at 11:58:51AM -0600, Josh Cartwright wrote:
Both the PM_RUNTIME and PM_SLEEP callbacks call into the common
msm_otg_{suspend,resume} routines, however these routines are only being
built when
On Tue, Feb 18, 2014 at 10:24:16AM -0600, Felipe Balbi wrote:
On Fri, Jan 17, 2014 at 12:26:50PM -0600, Josh Cartwright wrote:
On Fri, Jan 17, 2014 at 11:58:51AM -0600, Josh Cartwright wrote:
Both the PM_RUNTIME and PM_SLEEP callbacks call into the common
msm_otg_{suspend,resume}
On Tue, Feb 18, 2014 at 10:33:21AM -0600, Josh Cartwright wrote:
On Tue, Feb 18, 2014 at 10:24:16AM -0600, Felipe Balbi wrote:
On Fri, Jan 17, 2014 at 12:26:50PM -0600, Josh Cartwright wrote:
On Fri, Jan 17, 2014 at 11:58:51AM -0600, Josh Cartwright wrote:
Both the PM_RUNTIME and
Both the PM_RUNTIME and PM_SLEEP callbacks call into the common
msm_otg_{suspend,resume} routines, however these routines are only being
built when CONFIG_PM_SLEEP. In addition, msm_otg_{suspend,resume} also
depends on msm_hsusb_config_vddcx(), which is only built when
CONFIG_PM_SLEEP.
Fix the
On Fri, Jan 17, 2014 at 11:58:51AM -0600, Josh Cartwright wrote:
Both the PM_RUNTIME and PM_SLEEP callbacks call into the common
msm_otg_{suspend,resume} routines, however these routines are only being
built when CONFIG_PM_SLEEP. In addition, msm_otg_{suspend,resume} also
depends on
