cpufreq: Save user policy min/max instead of policy min/max during hotplug

When a CPU is hotplugged off, various fields of the policy are saved so
that they can be restored when the CPU is hotplugged back in.

The existing code saves the policy min/max field during hotplug remove and
restores it into user policy min/max during hotplug add. This results in
the loss of the user policy min/max values across a hotplug remove/add.

Fix it by saving the user policy min/max instead of policy min/max during
hotplug remove. During a hotplug add, after user policy min/max is
restored, the policy min/max is already recomputed. So, there's no risk of
going beyound any limits imposed by the CPUFREQ_ADJUST/INCOMPATIBLE
notifiers.

Change-Id: Ib8e09fa324c1f80f095c5754b5dcf2685e8e4a66
Signed-off-by: Saravana Kannan <skannan@codeaurora.org>
msm: pil: Add HTC delay for rmt_storage

Change-Id: I553f8015cfd102032c4fa3fa5e4bff3ac81e4819
Merge tag 'v3.4.72' into tmp

This is the 3.4.72 stable release

Conflicts:
	arch/arm/Kconfig
	arch/arm/include/asm/mutex.h
	arch/arm/kernel/perf_event.c
	arch/arm/kernel/traps.c
	arch/arm/mm/dma-mapping.c
	drivers/base/power/main.c
	drivers/bluetooth/ath3k.c
	drivers/bluetooth/btusb.c
	drivers/gpu/drm/radeon/radeon_mode.h
	drivers/mmc/card/block.c
	drivers/mmc/host/sdhci.c
	drivers/usb/core/message.c
	drivers/usb/host/xhci-plat.c
	drivers/usb/host/xhci.h
	drivers/virtio/virtio_ring.c
	fs/ubifs/dir.c
	include/linux/freezer.h
	include/linux/virtio.h
	include/media/v4l2-ctrls.h
	include/net/bluetooth/hci_core.h
	include/net/bluetooth/mgmt.h
	kernel/cgroup.c
	kernel/futex.c
	kernel/signal.c
	net/bluetooth/hci_conn.c
	net/bluetooth/hci_core.c
	net/bluetooth/hci_event.c
	net/bluetooth/l2cap_core.c
	net/bluetooth/mgmt.c
	net/bluetooth/rfcomm/sock.c
	net/bluetooth/smp.c

Change-Id: I4fb0d5de74ca76f933d95d98e1a9c2c859402f34
Revert "ALSA: fix oops in snd_pcm_info() caused by ASoC DPCM"

This reverts commit 5812381adfde20cb352d3047190ab45ea5bb59f2.