GitHub PushEvent at 2014-01-15 06:12:04
Repository: android_kernel_htc_m7
Actor: dastin1015
Payload: {"shas":[["86c8142508665f1a91d55d9c31c00a28053668d0","2afa83dd02a4531013cf9ecb24e39a5ca10af967@codeaurora.org","msm: vidc: Set input buffer size dynamically\n\nThis change supports overriding of default input\nbuffer size using a set parameter call from the\nclient.\n\nChange-Id: I5225ec53ba16b68aeedd4c30897bd291e81b4b09\nSigned-off-by: Deepak Verma <dverma@codeaurora.org>","Deepak Verma",true],["c0ee9a95c05a863fdb59ed8517d7e6db0d61d06a","b8b7e8a1740f4a6484e6faf986cb2a9e5fbce020@codeaurora.org","msm: vidc: estimate min_dpb for smooth streaming mode\n\nIn case of smoothstreaming:\n[1] get dpb requirement for the firmware\n[2] get count in resource resource tracker\nUse higher of the above\n\nb/10192531\n\nSigned-off-by: Deepak Verma <dverma@codeaurora.org>\nSigned-off-by: Praveen Chavan <pchavan@codeaurora.org>\n\nmsm: vidc: Add some missed code during merge\n\nChange-Id: I89b355e69b051d510b7936a7cf83ec3d19c0e324","Praveen Chavan",true],["c3fe202fa759e3b9e9455f39cc0082c2d0981894","ce25c3cee4cc6c4c8acfc1680b3ed89cf644dba3@codeaurora.org","cpufreq: Save user policy min/max instead of policy min/max during hotplug\n\nWhen a CPU is hotplugged off, various fields of the policy are saved so\nthat they can be restored when the CPU is hotplugged back in.\n\nThe existing code saves the policy min/max field during hotplug remove and\nrestores it into user policy min/max during hotplug add. This results in\nthe loss of the user policy min/max values across a hotplug remove/add.\n\nFix it by saving the user policy min/max instead of policy min/max during\nhotplug remove. During a hotplug add, after user policy min/max is\nrestored, the policy min/max is already recomputed. So, there's no risk of\ngoing beyound any limits imposed by the CPUFREQ_ADJUST/INCOMPATIBLE\nnotifiers.\n\nChange-Id: Ib8e09fa324c1f80f095c5754b5dcf2685e8e4a66\nSigned-off-by: Saravana Kannan <skannan@codeaurora.org>","Saravana Kannan",true],["3722f8ec77c8945cabcbe806bbd3cf443db98c23","9296a0ca31e8299ed6ec39daa4ff56fd47a51cb6@codeaurora.org","cpufreq: interactive: Add a sampling_down_factor for max frequencies\n\nChange min_sample_time to 100ms when running at max\n\nChange-Id: Ia7e35b0625bedf20e7ef3a1f52e5828ffbfed93e\nSigned-off-by: Rohit Gupta <rohgup@codeaurora.org>","Rohit Gupta",true],["1465a672efa48aefc0a21a5fb0686fb435c06f7c","9296a0ca31e8299ed6ec39daa4ff56fd47a51cb6@codeaurora.org","cpufreq: interactive: Allow 1 ms error in above_hispeed_delay comparisons\n\nAllow for an error of 1 ms while taking into account\nabove_hispeed_delay for a frequency\n\nChange-Id: I744e44387152e4efb5978df4f2b9533bf79d4582\nSigned-off-by: Rohit Gupta <rohgup@codeaurora.org>","Rohit Gupta",true],["53ee2fc70f6ae1786f22c8ba60904240ba40d3fc","9296a0ca31e8299ed6ec39daa4ff56fd47a51cb6@codeaurora.org","cpufreq: interactive: Reset floor_validate_time if busy at max for 100ms\n\nWhen the interactive governor selects to run at max frequency it doesn't\nre-schedule the timer until it hits an idle. This change checks if the CPU\nhas been continuously busy for last 100ms on hitting an idle start. If yes,\nthen floor_validate_time is reset so that the CPU stays at max frequency\nfor at least another 100 ms before stepping down.\nThis is an important feature for detecting CPU intensive workloads which\nrequire high frequencies for achieving better performance.\n\nChange-Id: I7d48ffbc3d50a80af9be3bf94667ee3d0120b763\nSigned-off-by: Rohit Gupta <rohgup@codeaurora.org>","Rohit Gupta",true],["0d24c48dd0bb2ae6f4badd3a50cd5c6fa6d96809","9296a0ca31e8299ed6ec39daa4ff56fd47a51cb6@codeaurora.org","cpufreq: interactive: sync freq feature for interactive governor\n\n1) Add load info to cpufreq_interactive_cpuinfo\n2) If load on any other online cpu exceeds sync_freq_load_threshold,\n   do not allow the frequency to drop below sync_freq\n\nChange-Id: I3617e10f87b85178914a18bcf04ac2a31a4f1ec1\nSigned-off-by: Rohit Gupta <rohgup@codeaurora.org>\n(cherry picked from commit c26e25944543c61b34b1830938bb6f353a2580ac)","Rohit Gupta",true],["007deeebb85729089c375427fcd7f1fd05b7e0c8","9296a0ca31e8299ed6ec39daa4ff56fd47a51cb6@codeaurora.org","cpufreq: interactive: Remove trace event from idle_start handler\n\nRemoved the trace_cpufreq_interactive_idle_start.\nAlso fix a crash resulting from accessing NULL policy before taking\nthe pcpu->enable_sem lock. The policy can be NULL if the core is\nhotplugged out before the enable_sem lock is taken.\n\nChange-Id: I7e2809cc016b3b383a44cdf3c697013e2d2b5417\nSigned-off-by: Rohit Gupta <rohgup@codeaurora.org>\n(cherry picked from commit 3b7992b90216c74a9ae9ce0df90bc446687a2313)","Rohit Gupta",true],["6c806ac7e0e741c471ca7a451fee41bb74c3a0f6","de1403edd397698bdf6eb99e490c5825516a9a17@codeaurora.org","cpufreq: ondemand: fix timer-related list corruption in store_powersave_bias()\n\nThe dbs_timer_init() call in store_powersave_bias() re-initializes the\ndbs_info workqueue, call on dbs_timer_exit() to ensure\noutstanding work is cleared prior to making this call. Also, grab the\npercpu timer_mutex lock to avoid race conditions with respect to the\ndbs timer.\n\nChange-Id: I79f3d43eeb51d2d8e21edd0fe043d6583333951f\nSigned-off-by: Osvaldo Banuelos <osvaldob@codeaurora.org>","Osvaldo Banuelos",true],["a5496a6c98b0918c5b90e6dcf72507f783c5d671","4258600f287a48a44d763bba39a8aaac2ea2f457@codeaurora.org","ondemand: add sysfs entry for down_diff_multi_core\n\nThis change adds sysfs entry for the ondemand governor's attribute\ndown_differential_multi_core. This is required to be able to program\nthis knob to attain better perf/power for use cases like camcorder.\n\nCRs-fixed: 561456\nChange-Id: Ib7c1223215c6b714c286c231ed37f3abfae741c6\nSigned-off-by: Krishna Vanka <kvanka@codeaurora.org>","Krishna Vanka",true],["f9e6c8f40c7391a8bfc36ada72e2bcc5549bff6a","9296a0ca31e8299ed6ec39daa4ff56fd47a51cb6@codeaurora.org","cpufreq: interactive: Modifying sync_freq implementation\n\n1. Check for up_threshold_any_cpu_freq instead of sync_freq to\n   boost the frequency to sync_freq.\n2. Change the load threshold name from sync_freq_load_threshold to\n   up_threshold_any_cpu_load\n3. Do not consider CPUs with load less than up_threshold_any_cpu_load\n   while evaluating max load across CPUs\n\nChange-Id: Ia0e537edbf38a5006c1a22f5c472daa0d086ffc9\nSigned-off-by: Rohit Gupta <rohgup@codeaurora.org>","Rohit Gupta",true],["f28fa8103eebdb887ced091ec86d86ff67e00d5c","9296a0ca31e8299ed6ec39daa4ff56fd47a51cb6@codeaurora.org","cpufreq: interactive: Use default min_sample_time if SDF is zero\n\nUse min_sample_time to step down from max frequencies if\nsampling_down_factor is set to zero.\n\nChange-Id: I2e89bef6220557cb95efd20d658e0c05753b4c3c\nSigned-off-by: Rohit Gupta <rohgup@codeaurora.org>","Rohit Gupta",true],["bd9b3a473461984235c076b9e81e97f14e259bec","7f5bb03cf507c861269be561971108be8f37d832@chemlab.org","video: msm: Restore overmapping changes\n\nRevert \"Revert \"msm: msm_fb: Map RGB layers to the max possible size.\"\"\n\nThis reverts commit 17fff7a48a443a4cbe98afa123186d46e33a6e29.\n\nRevert \"Revert \"msm: msm_fb: Fix Regressions because of overmap changes.\"\"\n\nThis reverts commit 0aa8ee050aab61af029a6f34f42632df65f7aa65.\n\nChange-Id: I34b136c479a381fdec50c48c2e56fb46df73c59c","Steve Kondik",true],["27df0ddf9b99cc80acc72356bf788f497749d307","bf1b3d55c9688c44c47080bb956e0b5fa97ddc18@codeaurora.org","Revert \"[ARM] msm: iommu_domains: replace vmalloc with kmalloc\"\n\nWhen overmapping is used, system can request higher order page allocaitons.\nthis can lead to page allocation failure if kmalloc is used\n\nCRs-Fixed: 571753\n\nThis reverts commit 191a48ee7bda08bf88a61b48fd0433627c5918dc.\n\nChange-Id: I4d44bf88d84d96d315f89a1304a2d25b75be79d8\nSigned-off-by: Srinivasarao P <spathi@codeaurora.org>","Srinivasarao P",true],["bad2c9bd4415266c7c81aa3c02169e8c9b41b69c","0d1dae58f23e775314d087dff72f8e136928d2cc@codeaurora.org","msm: msm_fb: Update panel info in case of resolution change.\nIn case of resolution change, panel_info and mfd are updated with latest resolution.\n\nChange-Id: I4958b8adc1650ec01c331b1a1ab695c5fd5add9b\nSigned-off-by: raghavendra ambadas <rambad@codeaurora.org>","raghavendra ambadas",true],["c72ce53acbf2b486c37338985d625083e03df5de","ce25c3cee4cc6c4c8acfc1680b3ed89cf644dba3@codeaurora.org","cpufreq: Fix policy getting stuck when user & kernel min/max don't overlap\n\nEvery __cpufreq_set_policy starts with checking the new policy min/max has\nsome overlap with the current policy min/max. This works out fine until we\nend up with the policy min/max being set to a range that doesn't overlap\nwith the user policy min/max. Once we get into this situation, the check at\nthe start of __cpufreq_set_policy fails and prevents us from getting out of\nthis state.\n\nThis only happens when one of the CPUFREQ_ADJUST/CPUFREQ_INCOMPATIBLE\nnotifiers called inside __cpufreq_set_policy pick a min/max outside the\nrange of user policy min/max.\n\nThe real intent of the check at the start of __cpufreq_set_policy is to\nmake sure userspace can't set user policy min > user policy max. Since\n__cpufreq_set_policy always gets called only with current user policy\nmin/max except when the actual user space policy min/max is changed, we can\nfix the issue by simply checking the new policy min/max against current\nuser policy min/max.\n\nChange-Id: Iaac805825e64d7985c41fb9052bd96baacdf3d6f\nSigned-off-by: Saravana Kannan <skannan@codeaurora.org>","Saravana Kannan",true]],"size":16,"ref":"refs/heads/cm-11.0","head":"c72ce53acbf2b486c37338985d625083e03df5de"}