M2: quiet down klog debugging
M2: msm: simplify ifdefs (no functional change)

I made these before we had a unified "MACH_M2" (thanks invisiblek).
Looks better now.

Change-Id: Ibfd7e22267acb13eea7fc1778994affccbec196d
M2: regulators: fixup: make RPM_VREG_ID_PM8921_S2 regulator sleep_selectable

M2: ATT: Increase frequency for RPM_VREG_ID_PM8921_S2 regulator to 2.4.

(same as in stock. ATT specific change is forced in rpm-regulator.c)

M2: ATT: Change voltage parameters for L22 (same as stock).

Change-Id: Ib351f8f75437e85fb50ba166dcaf887fac042df5
M2: otg: fix runaway wakelock

When booting with wall-charger plugged-in state machine transitions to
STATE_B_PERIPHERAL (B_SESS_VLD bit is set in msm_otg_init_sm).

Aftr uplugging, bit is not cleared, and state machine never transitions
to IDLE, consequently msm_otg wakelock is never unlocked.
M2: msm: move ram_console back to fff00000
M2: pm: Remove ccadc calibration schedule

As of
99ee5 msm: power: update power drivers to msm-3.4 tip
ccadc re-calibration is forced for all pm8921 users, both on resume, and
on during regular time-intervals via a delayed workqueue.

This is bad - locking a mutex in the resume path
that is also locked in a delayed work queue is
asking for trouble.  In particular, if the system suspends while the
mutex is held, trying to re-lock the mutex in the resume path causes
deadlock (SOD).

Could be fixed with mutex_try_lock in the resume path, but:

This is not for us, since in the stock mangled samsung pm8xxx drivers, there is no
ccadc (re)calibration. Also not calibrating seems to have a positive
effect on battery life in limited testing.
M2: De-base proximity sensor events

Rapid prox near/far events can hang the device.

De-base the readings in a delayed workqueue by .3 seconds.