PM / cpufreq: Initialise the cpu field during conservative governor start

This change initialises the cpu id field of cs_cpu_dbs_info structure in
conservative governor and keep this consistent with other governors.
Similar initialisation is present in ondemand governor.

Change-Id: I2806fe15b94e92e160e38fa62172ac0f7ee311f5
Signed-off-by: Amit Daniel Kachhap <amit.daniel@samsung.com>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
(cherry picked from commit 0720b53d48f7b32d078a1b9bf24de7238f7a8dfa)
(cherry picked from commit 443aac6309d26154b064e45e29142f0fb7d026b5)
cpufreq: conservative: update frequency when limits are relaxed

Reevaluate CPU load and update frequency immediately whenever limits
are changed. Currently conservative doesn't do that when limits are
relaxed, wasting power on systems with relatively low sampling rate.

Change-Id: I271d36b9c61b2746b035ca5b6214e699c8034d42
Signed-off-by: Michal Pecio <mpecio@nvidia.com>
Reviewed-by: Thomas Renninger <trenn@suse.de>
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
(cherry picked from commit ad1c3a2f43acd7e26881bd941e77a6fb0535f6a9)
(cherry picked from commit 9198d8fcd90f0ad96af762358754d06a42310cea)
Merge "PM / cpufreq: Initialise the cpu field during conservative governor start" into cm-10.1
Merge pull request #16 from LegacyXperia/cm-10.1

Latest changes from LX