moto: fix Edison power domains target state

It sounds weird, but Edison doesn't want to put the powerdomains into target state for any reason - since we renamed the MAPPHONE_EDISON ection to MODEM_PORT. Using the prior definition too as well to fix it.

Change-Id: I4474c338b30c4f3d431aa1edb11bde0a8de07259
linux: workqeue: include back missing option

accidently removed
Revert "linux: workqeue: include back missing option"

This reverts commit 45bde708a5a555283b57abf3c88bdb9ed82b76e2.
workqueue: drop CPU_DYING notifier operation

Workqueue used CPU_DYING notification to mark GCWQ_DISASSOCIATED.
This was necessary because workqueue's CPU_DOWN_PREPARE happened
before other DOWN_PREPARE notifiers and workqueue needed to stay
associated across the rest of DOWN_PREPARE.

After the previous patch, workqueue's DOWN_PREPARE happens after
others and can set GCWQ_DISASSOCIATED directly.  Drop CPU_DYING and
let the trustee set GCWQ_DISASSOCIATED after disabling concurrency
management.
workqueue: ROGUE workers are UNBOUND workers

Currently, WORKER_UNBOUND is used to mark workers for the unbound
global_cwq and WORKER_ROGUE is used to mark workers for disassociated
per-cpu global_cwqs.  Both are used to make the marked worker skip
concurrency management and the only place they make any difference is
in worker_enter_idle() where WORKER_ROGUE is used to skip scheduling
idle timer, which can easily be replaced with trustee state testing.

This patch replaces WORKER_ROGUE with WORKER_UNBOUND and drops
WORKER_ROGUE.  This is to prepare for removing trustee and handling
disassociated global_cwqs as unbound.
[1/2] kernel: workqueue: backport from 3.9 and include patches from Neobuddy

See:

https://github.com/neobuddy89/hammerhead_kernel_caf/commits/kitkat-caf/kernel/workqueue.c
[2/2] kernel: workqueue: Adapt related changes to headers and fix code syntax in main driver
omap: voltage: mpu: raise values ~ -25mV of stock

Before we lowered the voltages a lot. But this seems to cause the system 'starving' and trying to compensate by autocalc higher values constantly which also caused a constant battery drain. Custom voltage interface was kinda locked too. With higher values we should be fine.
omap: voltage--amend : mpu: raise valus-25mV of stock

Before we lowered the voltages a lot. But this seems to cause the system 'starving' and trying to compensate by autocalc higher values constantly which also caused a constant battery drain. Custom voltage interface was kinda locked too. With higher values we should be fine.
Fix voltages and config
Revert "omap: cpufreq: start to cleanup"

This reverts commit 215ecaebc1d26d99ed172ae749d6f767b70e522c.
Revert "[3/4] drivers: cpufreq/input: add related functions to support governor based screen- and freq-stats"

This reverts commit 11879523b1ce3c11920caeab117395af6e959237.
Revert "[2/4] block: add related function 'load_prev_screen_on' to work with update governors"

This reverts commit 8ecb2a19e1b01969d0743cf618eee7b3872f7fab.
Revert "[1/4] power: introduce android_battery"

This reverts commit 43942b2f5d13227dd780c68dfa797f97b360613d.
Revert "CPU hotplug, debug: detect imbalance between get_online_cpus() and put_online_cpus()"

This reverts commit f40ca141f1c2defe880acda612ed6fb2699f7229.
omap: cpu: Improved  voltages, freq calculation, overall handling
Added todays changelog and updated full history
add all changes to related config files