init.rc: use the busybox in ramdisk because.
board: a quick script to show detailed board/soc info
init.rc: sigh, this is for cm9 compatibility
sdcard binary from greg white
leanKernel v2.7.2

- ramdisk modified for better CM9 compatibility.
- "board" script
- better init.d support
OMAP3+: Smartreflex: fix interrupt status clear write

ChangeId Ic0e3d9960ed9511769c3c25b2c71ff1e53bcc796
(OMAP3+: Smartreflex: Fix interrupt disable sequence)
intended to write the interrupt mask to status register
prior to disabling it, instead, we ended up writing 0
to the register, essentially leaving the interrupt status
not cleared. Fix this by splitting the interrupt disable
sequence out(v1 and v2 require different operation) and
ensure we write the correct value to interrupt status register.

Change-Id: Ib28352ff9ea4ec4b787aeee14a907e73080a6d12
Signed-off-by: Nishanth Menon <nm@ti.com>
Linux 3.0.26
OMAP: MUSB: Fix for issue when booting with USB charger connected

Issue:
When the charger is disconnected after bootup, the device fails
to go into OFF mode.
Bug Details:
1. At the end of Gadget Driver probe pm_runtime_put()is not called in
case of charger/USB cable connected during bootup.
2. After bootup when we disconnect the charger, the disconnect handler
for USB_EVENT_NONE checks first if the disconnect was for charger.
If yes it returns without autosuspend else it call pm_runtime_autosuspend.
So because of this PM calls get imbalanced and system does not go to OFF.
Fix:
Logic at the end of the gadget probe function is fixed to prevent
the above problem.

Change-Id: Ief7daade9aed7460bd4d1d576c22024a419ddbda
Signed-off-by: Mantesh Sarashetti <mantesh@ti.com>
CC: Ruchika Kharwar <ruchika@ti.com>

Conflicts:

	drivers/usb/musb/musb_gadget.c
omap:musb:PHY powering time change to longer

This patch helps to avoid problems in coldboot stage with some
selfpowered hubs, like old belkin. Problem looks like this:

[ 1019.749084] usb 2-1: reset high speed USB device number 107 using musb-hdrc
[ 1034.881805] usb 2-1: device descriptor read/64, error -110
[ 1040.115386] usb 2-1: device descriptor read/64, error -19
[ 1043.303710] hub 2-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
[ 1046.389648] hub 2-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
[ 1049.475555] hub 2-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
[ 1049.483459] usb 2-1: USB disconnect, device number 107
[ 1052.569366] hub 2-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?
[ 1055.655242] hub 2-0:1.0: Cannot enable port 1.  Maybe the USB cable is bad?

At boot time DEVCTL register occasionaly change it's state from
IRQ host to IRQ device but musb->xceiv->state is still host what cause messages.
Problem caused transient processes caused powering after enabling clocks.

Powering on the phy need more time after enabling the internal phy clocks.
It was done because 300ms give us possibility to avoid problems caused transient
processes after powering that was found in the experimental practice
with a larger number of selfpowered hubs.

Also it should make work with chain of two selfpowered hubs more stable.

Change-Id: Ib0add65ab2be6fc2f0123538fb0b6447fa140f8b
Signed-off-by: Moiz Sonasath <m-sonasath@ti.com>
Signed-off-by: Andrii Danylov <x0158318@ti.com>
OMAP4: cpuidle: don't touch mpu and core state until CPU1 is off

MPU/Core logic and PD states shouldn't be changed until CPU1 is
completely off

Change-Id: Ia90126776e7bd7108c7b885c622df36323982cb0
Signed-off-by: Lianwei Wang <lian-wei.wang@motorola.com>
Signed-off-by: suilunlam <a0868997@ti.com>
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
ARM: OMAP4: cpuidle: Configure MPU C4 state to OSWR

Due to MPU_EMIF_NO_DYNDEP_IDLE_iXXX, MPU->EMIF dynamic dependency
is disabled when going to LP mode. This allows us to enable deeper
power state for MPU as MPU can transition to lower power state
independent of core power domain. We have observed 1.5mA saving in
OS Idle Screen on use case.

Change-Id: If4ec4426626dabf810b1f21ed33cdabafa386d5f
Signed-off-by: Madhusudan Chittim <c-madhu@ti.com>
OMAP MUSB: Finish cherry-pick of 4e8fb4f
mms_ts: turn off touchscreen at early_suspend, by Turl
rpmsg: resmgr: disable aux_clk_src in case of error

If set_rate of aux_clk failed aux_clk_src was being left
enabled affecting the core OFF, fix the same.

Also avoid changing the return value of clk_set_rate.

Change-Id: I897d0669b43bf75ae49e9119ebfadf531bd585d5
Reported-by: Huzefa Kankroliwala <huzefank@ti.com>
Reported-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Miguel Vadillo <vadillo@ti.com>
cpuidle: ok ease up a little on aggressive multiplier calc

some people were having issues with mediascanner's partial wakelock
checkt: show cpu stats per cpu core
ramdisk: immediate suspend to ram

(still needs to be tested)
OMAP3+: PM: DVFS: add qos requirement to prevent interruptions

DVFS transitions are not meant to be interrupted as the interruptions
can cause severe mismatch in configuration sequences involved in DVFS.

We currently have omap_dvfs_lock check made in omap4_enter_sleep
function, however, considering cpuidle path:
a) omap4_enter_sleep is called by cpuidle's omap4_enter_idle_primary
   after the following steps:
   i) set the log state and set power domain state
   ii) WAIT FOR power domain state to transition!!!
  then we call omap4_enter_sleep
b) Now in omap4_enter_idle_secondary,
  GIC disabled, and we directly hit omap4_enter_lowpwer and goes down

We DONOT want this to take place when DVFS frequency configuration,
voltage programming and smartreflex AVS operations take place.

So request for QoS for the period of transition and release once operation
is done as it is less intrusive and takes care of CPU0 or CPU1 activity
to low power states as well.

Change-Id: I7731a3262bf88dd78e279a8c8306850e077865a5
Reported-by: Vinay Chaurasia <vinaych@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
OMAP3630+: SmartReflex : 1p5: add qos request

Since we do calibration sequences out of the DVFS path, we still
need to honor the requirement not to interrupt the hardware activities
by attempting lower power states untill calibration is complete.
Hence request a QoS while we have hardware calibration sequence
active and monitoring is in progress.

We currently have check for work->active and abort as part of trigger
sequence from omap4_enter_sleep function, however,
considering cpuidle path:
a) omap4_enter_sleep is called by cpuidle's omap4_enter_idle_primary
after the following steps:
  i) set the log state and set power domain state
  ii) WAIT for power domain state to transition!!!
  we then call omap4_enter_sleep
b) Now in omap4_enter_idle_secondary,
  GIC disabled, and we directly hit omap4_enter_lowpwer and goes down

We DONOT want these to take place while we are capturing a calibrated
voltage for the OPP.

Change-Id: I217d80b1ffcf7cbe80eea4ceb29363bd2d25178e
Reported-by: Shashi Shekar B.S. <shashi.shekar@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
OMAP3+: PM: VP: dereference voltdm after checking valid voltdm

voltdm should be dereferenced only after voltdm has been checked
for NULL parameters.

Change-Id: I61792933b6a33121dc2e7855e6c0b75f24a0d03b
Reported-by; Hoon Heo <ryan.heo@samsung.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>