ariesve: Some changes to gp4 voltage regulators

These changes allow to prevent these errors when setting touchscreen voltage:
<3>[    0.063964] ldo10: requested voltage range [1800000, 1800000] does not fit within previously voted range: [2600000, 2600000]
<3>[    0.064086] oliver_tsp_ldo_on: vreg LDO2 set level failed (-22)

The touchscreen after getting this error uses the wrong voltage of
2600000 uV instead of 18000000 uV.

The regulator's core has been changed and the voltage range that doesn't
fit the previously set voltage range is not allowed, so we need to correct
the other occurrences where gp4 regulator has been registered.
ariesve: Some changes to the touchscreen power-on routine
msm: qdsp5v2: Increase buffersize of hostPCM interface.

The default audio sample rate of audioflinger is increased
from 44.1k to 48k.Increase the buffersize to take
advantage of that.

Change-Id: I7ffc6c697cb32b6983c9bb5cc6ea73a7a55b5006
Signed-off-by: Sidipotu Ashok <sashok@codeaurora.org>
ariesve: Some board cleanup

Moved the config_gpio_table method outside of the CONFIG_MSM_CAMERA block,
because this method is used by other drivers init methods, too.
ariesve: Fixed some warnings reported during board compilation
ariesve: Some board cleanup

Initialize TV Encoder only if TV Out config option has been enabled.
ariesve: Fix display regulators init
ariesve: Update lcd regulator
video: Power management support on S6E63M0 display driver
ariesve: Fix double activation of the regulators of the display
ashmem: avoid deadlock between read and mmap calls

Avoid holding ashmem_mutex across code that can page fault.  Page faults
grab the mmap_sem for the process, which are also held by mmap calls
prior to calling ashmem_mmap, which locks ashmem_mutex.  The reversed
order of locking between the two can deadlock.

The calls that can page fault are read() and the ASHMEM_SET_NAME and
ASHMEM_GET_NAME ioctls.  Move the code that accesses userspace pages
outside the ashmem_mutex.

Bug: 9261835
Change-Id: If1322e981d29c889a56cdc9dfcbc6df2729a45e9
Signed-off-by: Todd Poynor <toddpoynor@google.com>
apache: Change to correct camera sensor for this phone
misc: uidstat: avoid create_stat() race and blockage.

* create_stat() race would lead to:
  [   58.132324] proc_dir_entry 'uid_stat/10061' already registered

* blocking kmalloc reported by sbranden
 tcp_read_sock()
  uid_stat_tcp_rcv()
    create_stat()
      kmalloc(GFP_KERNEL)

Signed-off-by: JP Abgrall <jpa@google.com>
Squashed update of BFQ-v6 to BFQ-v6r1

- Fix use-after-free of queues in __bfq_bfqq_expire(). It may happen that
  a call to bfq_del_bfqq_busy() puts the last reference taken on a queue
  and frees it. Subsequent accesses to that same queue would result in a
  use-after-free. Make sure that a queue that has just been deleted from
  busy is no more touched.
- Use the uninitialized_var() macro when needed. It may happen that a
  variable is initialized in a function that is called by the function
  that defined it. Use the uninitialized_var() macro in these cases.
cpufreq: interactive: handle errors from cpufreq_frequency_table_target

Add checks for error return from cpufreq_frequency_table_target, and be
less noisy on the existing call with an error check.  CPU hotplug and
system shutdown may cause this call to return -EINVAL.

Bug: 8613560
Change-Id: Id78d8829920462c0db1c7e14e717d91740d6cb44
Signed-off-by: Todd Poynor <toddpoynor@google.com>
cpufreq: interactive: reduce chance of zero time delta on load eval

Reschedule load sampling timer after timestamp of sample start taken,
hold spinlock across entire sequence to avoid preemption.  Avoid the
WARN for zero time delta in the load sampling timer function.

Change-Id: Idc10a756f09141decb6df92669521a1ebf0dbc10
Signed-off-by: Todd Poynor <toddpoynor@google.com>
cpufreq: interactive: avoid underflow on active time calculation

Check for idle time delta less than elapsed time delta, avoid
underflow computing active time.

Change-Id: I3e4c6ef1ad794eec49ed379c0c50fa727fd6ad28
Signed-off-by: Minsung Kim <ms925.kim@samsung.com>
net: wireless: bcmdhd: Disable SUPPORT_PM2_ONLY and DISABLE_FW_ROAM_SUSPEND

Should provide better battery savings.
net: wireless: bcmdhd: Fix data CRC errors

It is probable that enable the CMD14 in sd bus, creates problems.
In the old version of the driver is used only in the BCM4330 chipset.

dmesg:
<3>[  127.747741] mmc0: Data CRC error
<3>[  127.747863] msmsdcc_data_err: opcode 0x00000035
<3>[  127.747924] msmsdcc_data_err: blksz 4, blocks 1
Squashed update of BFQ-v6r1 to BFQ-v6r2