ALUCARD HOTPLUG: fix typo in function. thanks @alucard
net: wireless: bcmdhd: Fix Batch scan get bug

Legacy Batch scan code would issue mutex unlock w/o a lock

bug: 17021370

Signed-off-by: Ashwin <ashwin.bhat@broadcom.com>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

https://github.com/neobuddy89/hammerhead_kernel_caf/commit/e26e9d653532621f009d3ef1a0e5b7f07da59713

Dorimanx:
finnaly this shit is fixed! :)
cpufreq: cpuboost: Make cpu boost driver aware of LCD events

* We previously removed "placebo" wake boost from intelli
  hotplug driver and stated we may add same to MSM Limiter
  driver.
* However, we already have good boost driver in place.
  So we use same to apply CPU boost whenever screen is
  turned on!
* Tested and worked well.
https://github.com/neobuddy89/hammerhead_kernel_caf/commit/69378c9d6f86fecd4c6bc9bdacd9b8dc58a0f1d6

* This is needed to unify boost functions in cpu boost
  and hotplug drivers.
https://github.com/neobuddy89/hammerhead_kernel_caf/commit/ac3c3098b5b1eebda50445226481c07c355e652f

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

Dorimanx.
Merged latest ver from neo!
cpufreq: cpu-boost: Unify input and hotplug boost

* This doesn't make sense to have mirror functions
  operating different boost frequencies.
* If input_boost_freq > hotplug_boost_freq, hotplug
  boost will be rendered useless in most case since
  parallel input boost will be doing it work.
* So instead having separate boost functions,
  keep only single boost function "do_input_boost"
  and let hotplug callback access this boost.
* Disable hotplug boost by default and provide
  attribute for same.

* Increased migration_load_threshold to prevent
  not-so-needed and recurring migrations.

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

https://github.com/neobuddy89/hammerhead_kernel_caf/commit/0e8176ecaaceec30e38f676d1849a7e8cc7664d4
https://github.com/neobuddy89/hammerhead_kernel_caf/commit/6c498d78c2d1eae0b5d0b1eeda21fd894787f9ab
msm: hotplug: Use wakeup_boost hint and other fixes

* In current scenario, we boost (turn all cores online)
  whenever LCD turns on. This is really not required when
  we have good hotplug mechanism in place. The mechanism
  should detect load and put appropriate cpus online.
* Boosting CPUs each time will increase battery consumption
  (maybe not so much but we should prevent this)
* So boost CPUs and apply downlock only in two cases viz.
  hotplug was suspended and user requested wakeup_boost
  via cpu-boost driver from userspace.
* Also, it is observed that suspend_defer_time is not
  working as required. It should suspend as soon as defer
  time is completed. Therefore, make use of separate freezable
  workqueue to do this smoothly.
* Organize sequence for initiating and cancelling work.

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
intelli_plug: Fixes for suspend/resume work rare issues

* It is observed that suspend_defer_time is not
  working as required. It should suspend as soon as defer
  time is completed. Therefore, make use of separate freezable
  workqueue to do this smoothly.
* Organize sequence for initiating and cancelling work.

Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>

Dorimanx:
Code style mods and cleanups.