sync dvfs patches

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

patch.sh

@@ -343,7 +343,10 @@ patch -s -p1 < "${DIR}/patches/dvfs/0049-omap3-sr_device-warn-in-log-that-sr-nta
 patch -s -p1 < "${DIR}/patches/dvfs/0050-omap3-sr-make-enable-patch-use-volt_data-pointer.patch"
 patch -s -p1 < "${DIR}/patches/dvfs/0051-omap3-voltage-add-transdone-apis.patch"
 patch -s -p1 < "${DIR}/patches/dvfs/0052-omap3-dvfs-introduce-api-to-protect-sr-ops.patch"
-patch -s -p1 < "${DIR}/patches/dvfs/0053-omap3-add-sr1.5.patch"
+patch -s -p1 < "${DIR}/patches/dvfs/0053-omap3630-sr-add-support-for-class-1.5.patch"
+patch -s -p1 < "${DIR}/patches/dvfs/0054-omap3430-sr-class3-restrict-cpu-to-run-on.patch"
+patch -s -p1 < "${DIR}/patches/dvfs/0055-omap3-smartreflex-enable-disable-iff-voltage-data-pr.patch"
+patch -s -p1 < "${DIR}/patches/dvfs/0056-sr1.5-dont-trust-sr-layer.patch"
 
 #patch -s -p1 < "${DIR}/patches/dvfs/0001-OMAP3-beagle-xm-enable-upto-1GHz-OPP.patch"
 patch -s -p1 < "${DIR}/patches/dvfs/0001-omap3-Add-basic-support-for-720MHz-part.patch"

patches/defconfig

 #
 # Automatically generated make config: don't edit
 # Linux/arm 2.6.38-rc6 Kernel Configuration
-# Thu Feb 24 16:28:28 2011
+# Mon Feb 28 16:01:54 2011
 #
 CONFIG_ARM=y
 CONFIG_SYS_SUPPORTS_APM_EMULATION=y
@@ -299,7 +299,8 @@ CONFIG_ARCH_OMAP2PLUS=y
 #
 CONFIG_OMAP_SMARTREFLEX=y
 CONFIG_OMAP_SMARTREFLEX_CLASS3=y
-# CONFIG_OMAP_SMARTREFLEX_CLASS1P5 is not set
+CONFIG_OMAP_SMARTREFLEX_CLASS1P5=y
+CONFIG_OMAP_SR_CLASS1P5_RECALIBRATION_DELAY=86400000
 CONFIG_OMAP_RESET_CLOCKS=y
 CONFIG_OMAP_MUX=y
 # CONFIG_OMAP_MUX_DEBUG is not set

patches/dvfs/0001-MAINTAINERS-change-Kevin-s-email-for-OMAP-PM-section.patch

 From 76679cf056343e104f0001d014b85f8060b34ed5 Mon Sep 17 00:00:00 2001
 From: Kevin Hilman <khilman@ti.com>
 Date: Tue, 4 Jan 2011 15:33:08 -0800
-Subject: [PATCH 01/53] MAINTAINERS: change Kevin's email for OMAP PM section
+Subject: [PATCH 01/56] MAINTAINERS: change Kevin's email for OMAP PM section
 
 Change my email to TI email address for OMAP PM maintenance.
 

patches/dvfs/0002-OMAP3-CPUIdle-prevent-CORE-from-going-off-if-doing-s.patch

 From 36ba533eb897e9c37cff0be6c986d10701bd86aa Mon Sep 17 00:00:00 2001
 From: Tero Kristo <tero.kristo@nokia.com>
 Date: Fri, 21 Jan 2011 12:37:05 +0200
-Subject: [PATCH 02/53] OMAP3: CPUIdle: prevent CORE from going off if doing so would reset an active clockdomain
+Subject: [PATCH 02/56] OMAP3: CPUIdle: prevent CORE from going off if doing so would reset an active clockdomain
 
 On OMAP3 SoCs, if the CORE powerdomain enters off-mode, many other
 parts of the chip will be reset.  If those parts of the chip are busy,

patches/dvfs/0003-OMAP-CPUfreq-ensure-driver-initializes-after-cpufreq.patch

 From 8b81d955ac5fe39251ab109e0281c4c79266f049 Mon Sep 17 00:00:00 2001
 From: Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com>
 Date: Wed, 11 Aug 2010 17:02:43 -0700
-Subject: [PATCH 03/53] OMAP: CPUfreq: ensure driver initializes after cpufreq framework and governors
+Subject: [PATCH 03/56] OMAP: CPUfreq: ensure driver initializes after cpufreq framework and governors
 
 Signed-off-by: Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com>
 Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>

patches/dvfs/0004-OMAP-CPUfreq-ensure-policy-is-fully-initialized.patch

 From 85c175f01a3c09da24ece82103c71daf53cf6bc9 Mon Sep 17 00:00:00 2001
 From: Kevin Hilman <khilman@deeprootsystems.com>
 Date: Wed, 11 Aug 2010 17:05:38 -0700
-Subject: [PATCH 04/53] OMAP: CPUfreq: ensure policy is fully initialized
+Subject: [PATCH 04/56] OMAP: CPUfreq: ensure policy is fully initialized
 
 Ensure policy min/max/cur values are initialized when OMAP
 CPUfreq driver starts.

patches/dvfs/0005-OMAP3-PM-CPUFreq-driver-for-OMAP3.patch

 From ae00997395a30bbccaed8d85bcc39e8a85fcd11f Mon Sep 17 00:00:00 2001
 From: Rajendra Nayak <rnayak@ti.com>
 Date: Mon, 10 Nov 2008 17:00:25 +0530
-Subject: [PATCH 05/53] OMAP3 PM: CPUFreq driver for OMAP3
+Subject: [PATCH 05/56] OMAP3 PM: CPUFreq driver for OMAP3
 
 CPUFreq driver for OMAP3
 

patches/dvfs/0006-OMAP-PM-CPUFREQ-Fix-conditional-compilation.patch

 From 9b9a5eecc3eb65fc24e4a35f7628654c35dd72bc Mon Sep 17 00:00:00 2001
 From: Silesh C V <silesh@ti.com>
 Date: Wed, 29 Sep 2010 14:52:54 +0530
-Subject: [PATCH 06/53] OMAP: PM: CPUFREQ: Fix conditional compilation
+Subject: [PATCH 06/56] OMAP: PM: CPUFREQ: Fix conditional compilation
 
 Fix conditional compilation. A conditional expresiion
 should follow "#elif", in this case #elif clause should

patches/dvfs/0007-cpufreq-fixup-after-new-OPP-layer-merged.patch

 From 8084fac7776050d148626b37f5e3cacf85839300 Mon Sep 17 00:00:00 2001
 From: Kevin Hilman <khilman@deeprootsystems.com>
 Date: Tue, 16 Nov 2010 11:48:41 -0800
-Subject: [PATCH 07/53] cpufreq: fixup after new OPP layer merged
+Subject: [PATCH 07/56] cpufreq: fixup after new OPP layer merged
 
 ---
  arch/arm/plat-omap/cpu-omap.c |    3 ++-

patches/dvfs/0008-OMAP3-PM-CPUFreq-driver-for-OMAP3.patch

 From d836c59ffde41a31ff011cdc5c90d9385c5ff703 Mon Sep 17 00:00:00 2001
 From: Rajendra Nayak <rnayak@ti.com>
 Date: Mon, 10 Nov 2008 17:00:25 +0530
-Subject: [PATCH 08/53] OMAP3 PM: CPUFreq driver for OMAP3
+Subject: [PATCH 08/56] OMAP3 PM: CPUFreq driver for OMAP3
 
 CPUFreq driver for OMAP3
 

patches/dvfs/0009-cpufreq-fixup-after-new-OPP-layer-merged.patch

 From 29318e1a09ad69fdc96ca15e79719715f7c0b8b8 Mon Sep 17 00:00:00 2001
 From: Kevin Hilman <khilman@deeprootsystems.com>
 Date: Tue, 16 Nov 2010 11:48:41 -0800
-Subject: [PATCH 09/53] cpufreq: fixup after new OPP layer merged
+Subject: [PATCH 09/56] cpufreq: fixup after new OPP layer merged
 
 ---
  arch/arm/plat-omap/cpu-omap.c |    1 -

patches/dvfs/0010-OMAP3630-PM-don-t-warn-the-user-with-a-trace-in-case.patch

 From 3f45fb7b89fd08ba2289ed74fab48e1fafcdc2b0 Mon Sep 17 00:00:00 2001
 From: Ricardo Salveti de Araujo <ricardo.salveti@canonical.com>
 Date: Mon, 31 Jan 2011 11:35:25 -0200
-Subject: [PATCH 10/53] OMAP3630: PM: don't warn the user with a trace in case of PM34XX_ERRATUM
+Subject: [PATCH 10/56] OMAP3630: PM: don't warn the user with a trace in case of PM34XX_ERRATUM
 
 In case in user has a OMAP3630 < ES1.2 the kernel should warn the user
 about the ERRATUM, but using pr_warn instead of WARN_ON is already

patches/dvfs/0011-OMAP3-4-OPP-make-omapx_opp_init-non-static.patch

 From 604472251ff314d7a79ace6fe11736e2185d4707 Mon Sep 17 00:00:00 2001
 From: Menon, Nishanth <nm@ti.com>
 Date: Wed, 5 Jan 2011 20:49:35 +0000
-Subject: [PATCH 11/53] OMAP3|4: OPP: make omapx_opp_init non-static
+Subject: [PATCH 11/56] OMAP3|4: OPP: make omapx_opp_init non-static
 
 omap3 and omap4 opp_init should be made non-static to allow
 for platform specific opp table tweaking. making these static

patches/dvfs/0012-OMAP3-beagle-xm-enable-up-to-800MHz-OPP.patch

 From d36526037ea65a7c8bfdf27272d9a475a23b9031 Mon Sep 17 00:00:00 2001
 From: Nishanth Menon <nm@ti.com>
 Date: Fri, 7 Jan 2011 09:41:13 -0600
-Subject: [PATCH 12/53] OMAP3: beagle xm: enable up to 800MHz OPP
+Subject: [PATCH 12/56] OMAP3: beagle xm: enable up to 800MHz OPP
 
 OMP3630 silicon can enable higher frequencies only depending on the board
 characteristics meeting the recommended standards, and has to be selectively

patches/dvfs/0013-OMAP-PM-SmartReflex-fix-potential-NULL-dereference.patch

 From 9f1c7c58af2c9725c4347a4e4a171884ba191da0 Mon Sep 17 00:00:00 2001
 From: Vasiliy Kulikov <segoon@openwall.com>
 Date: Wed, 19 Jan 2011 15:57:22 +0300
-Subject: [PATCH 13/53] OMAP: PM: SmartReflex: fix potential NULL dereference
+Subject: [PATCH 13/56] OMAP: PM: SmartReflex: fix potential NULL dereference
 
 kzalloc() may fail, if so return -ENOMEM.  Also Walter Harms suggested
 to use kasprintf() instead of kzalloc+strcpy+strcat.

patches/dvfs/0014-OMAP2-remove-unused-UART-base-addresses-from-omap_gl.patch

 From d62c777792b4080f5debf93c43d6bf3d3e67c61f Mon Sep 17 00:00:00 2001
 From: Kevin Hilman <khilman@ti.com>
 Date: Fri, 21 Jan 2011 14:30:15 -0800
-Subject: [PATCH 14/53] OMAP2+: remove unused UART base addresses from omap_globals
+Subject: [PATCH 14/56] OMAP2+: remove unused UART base addresses from omap_globals
 
 Now that omap_hwmod + omap_device is used for OMAP UART device and
 driver code, we no longer need the UART physical addresses in

patches/dvfs/0015-perf-add-OMAP-support-for-the-new-power-events.patch

 From c4d0b3d66d6a1e9da549fff36d95c7679c209592 Mon Sep 17 00:00:00 2001
 From: Jean Pihet <j-pihet@ti.com>
 Date: Mon, 24 Jan 2011 15:20:57 +0100
-Subject: [PATCH 15/53] perf: add OMAP support for the new power events
+Subject: [PATCH 15/56] perf: add OMAP support for the new power events
 
 The patch adds the new power management trace points for
 the OMAP architecture.

patches/dvfs/0016-OMAP2-3-PM-remove-unnecessary-wakeup-sleep-dependenc.patch

 From 42d5d9051e5c0b916eb1110bedac47e25f18329b Mon Sep 17 00:00:00 2001
 From: Paul Walmsley <paul@pwsan.com>
 Date: Thu, 27 Jan 2011 02:52:55 -0700
-Subject: [PATCH 16/53] OMAP2/3: PM: remove unnecessary wakeup/sleep dependency clear
+Subject: [PATCH 16/56] OMAP2/3: PM: remove unnecessary wakeup/sleep dependency clear
 
 The OMAP2 and OMAP3 PM code clears clockdomain wakeup and sleep
 dependencies.  This is unnecessary after commit

patches/dvfs/0017-OMAP-Introduce-accessory-APIs-for-DVFS.patch

 From 0f12946af21d71029a74c518f930b1f2cc96167e Mon Sep 17 00:00:00 2001
 From: Vishwanath BS <vishwanath.bs@ti.com>
 Date: Mon, 27 Dec 2010 15:04:06 +0530
-Subject: [PATCH 17/53] OMAP: Introduce accessory APIs for DVFS
+Subject: [PATCH 17/56] OMAP: Introduce accessory APIs for DVFS
 
 This patch introduces accessory APIs for DVFS.
 Data structures added:

patches/dvfs/0018-OMAP-Introduce-device-specific-set-rate-and-get-rate.patch

 From 098ed4423c5997293b3cd71fd5d52ca695952d75 Mon Sep 17 00:00:00 2001
 From: Thara Gopinath <thara@ti.com>
 Date: Mon, 27 Dec 2010 17:04:42 +0530
-Subject: [PATCH 18/53] OMAP: Introduce device specific set rate and get rate in omap_device structure
+Subject: [PATCH 18/56] OMAP: Introduce device specific set rate and get rate in omap_device structure
 
 This patch extends the omap_device structure to contain pointers to scale the
 operating rate of the device and to retrieve the operating rate of the device.