omap4-common: Revert back to Motorola's workaround for i719

Revert "Revert "[moto] arch/arm/mach-omap2/omap4-sar: changes for sar restore""
This reverts commit fed5f03d61d40147bbd0a8a6f4efa2f13ae74d2d.

Revert "ARM: OMAP4: USB: Update workaround for USB errata i719"
This reverts commit 58cb9633db740df1268c28426de62d025ebb0ed9.

Revert "OMAP4430: USB Host: Implement workaround for Errata i719"
This reverts commit 4f22585d474427eec131fbf9740ddcaf6c8de0d8.

Revert "OMAP4: SAR: WA overwrite L3INIT CD mode to SW_SLEEP(1) in SAR"
This reverts commit 49af0431b126f0e71f7539212c17a8c35fd810cf.

Change-Id: I83d1a2b212b8138f34c782ef926ec2250dfc585b
Revert "omap: pm: use workaround for CK PAD differential only on edison/targa"

This reverts commit 6c4691975e686eb5fb3f66aa0df8477067fdff02.
Revert "Revert "omap: pm: remove old workaround for CK differential IO PADn, PADp""

This reverts commit 63a20075fb31f62d580b5558ba1680ffcbed9fdf.
Merge remote-tracking branch 'CyanogenMod/cm-11.0' into cm-11.0
omap: dpll_cascading: add missing code and adapt to module
cpufreq: Fix sysfs deadlock with concurrent hotplug/frequency switch

Running one program that continuously hotplugs and replugs a cpu
concurrently with another program that continuously writes to the
scaling_setspeed node eventually deadlocks with:

=============================================
[ INFO: possible recursive locking detected ]
3.4.0 #37 Tainted: G        W
---------------------------------------------
filemonkey/122 is trying to acquire lock:
 (s_active#13){++++.+}, at: [<c01a3d28>] sysfs_remove_dir+0x9c/0xb4

but task is already holding lock:
 (s_active#13){++++.+}, at: [<c01a22f0>] sysfs_write_file+0xe8/0x140

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(s_active#13);
  lock(s_active#13);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

2 locks held by filemonkey/122:
 #0:  (&buffer->mutex){+.+.+.}, at: [<c01a2230>] sysfs_write_file+0x28/0x140
 #1:  (s_active#13){++++.+}, at: [<c01a22f0>] sysfs_write_file+0xe8/0x140

stack backtrace:
[<c0014fcc>] (unwind_backtrace+0x0/0x120) from [<c00ca600>] (validate_chain+0x6f8/0x1054)
[<c00ca600>] (validate_chain+0x6f8/0x1054) from [<c00cb778>] (__lock_acquire+0x81c/0x8d8)
[<c00cb778>] (__lock_acquire+0x81c/0x8d8) from [<c00cb9c0>] (lock_acquire+0x18c/0x1e8)
[<c00cb9c0>] (lock_acquire+0x18c/0x1e8) from [<c01a3ba8>] (sysfs_addrm_finish+0xd0/0x180)
[<c01a3ba8>] (sysfs_addrm_finish+0xd0/0x180) from [<c01a3d28>] (sysfs_remove_dir+0x9c/0xb4)
[<c01a3d28>] (sysfs_remove_dir+0x9c/0xb4) from [<c02d0e5c>] (kobject_del+0x10/0x38)
[<c02d0e5c>] (kobject_del+0x10/0x38) from [<c02d0f74>] (kobject_release+0xf0/0x194)
[<c02d0f74>] (kobject_release+0xf0/0x194) from [<c0565a98>] (cpufreq_cpu_put+0xc/0x24)
[<c0565a98>] (cpufreq_cpu_put+0xc/0x24) from [<c05683f0>] (store+0x6c/0x74)
[<c05683f0>] (store+0x6c/0x74) from [<c01a2314>] (sysfs_write_file+0x10c/0x140)
[<c01a2314>] (sysfs_write_file+0x10c/0x140) from [<c014af44>] (vfs_write+0xb0/0x128)
[<c014af44>] (vfs_write+0xb0/0x128) from [<c014b06c>] (sys_write+0x3c/0x68)
[<c014b06c>] (sys_write+0x3c/0x68) from [<c000e0e0>] (ret_fast_syscall+0x0/0x3c)

This is because store() in cpufreq.c indirectly calls
kobject_get() via cpufreq_cpu_get() and is the last one to call
kobject_put() via cpufreq_cpu_put(). Sysfs code should not call
kobject_get() or kobject_put() directly (see the comment around
sysfs_schedule_callback() for more information).

Fix this deadlock by introducing two new functions:

	struct cpufreq_policy *cpufreq_cpu_get_sysfs(unsigned int cpu)
	void cpufreq_cpu_put_sysfs(struct cpufreq_policy *data)

which do the same thing as cpufreq_cpu_{get,put}() but don't call
kobject functions.

To easily trigger this deadlock you can insert an msleep() with a
reasonably large value right after the fail label at the bottom
of the store() function in cpufreq.c and then write
scaling_setspeed in one task and offline the cpu in another. The
first task will hang and be detected by the hung task detector.

Change-Id: I7db3608f43ef97d7eb1214598bc39946c82734ee
Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
omap4-common: [moto] update Qualcomm Gobi 2000-driver

error-handling changes from the last XT910 source drop
(9.8.2O-124_SPUL-18 / 9.8.2O-124_SPUEM-14)

Change-Id: I971da6197c2f010aaad012dfc1625602ae1df660
omap: dpll_cascading: module: fix
DPLL, BF: Fix header file
Added todays changelog and updated full history
Revert "targa/edison: diabled smartreflex on init again"

This reverts commit 163ba5afd022cf067f76695408c91f97e69a06c6.