Limit max secure concurrent instances to 6 due to
system wide limitations like memory, performance etc.
CRs-Fixed: 1083289
Change-Id: I2dde6542a31fb7b2f0d4c7a3d599c1f78999e4fe
Signed-off-by: Saurabh Kothawade <skothawa@codeaurora.org>
Use the src clock binding to read the cpp src clock rate intead of
using the list rate api from clock driver.
CRs-Fixed: 1079648
Change-Id: I2ebdc0c41c521e56a400d685b6254174cffdc14b
Signed-off-by: Krishnankutty Kolathappilly <kkolatha@codeaurora.org>
Add cpp src clock rates to device node configuration.
Add separate cpp node for msmcobalt v2 as there is difference
in clock rates.
CRs-Fixed: 1079648
Change-Id: I436ad7fca01e599714f1bcb0abc06e5bc1165350
Signed-off-by: Krishnankutty Kolathappilly <kkolatha@codeaurora.org>
Some USB OTG devices fail to start due to high capacitance on VCONN which
causes an in-rush of current and triggers the over-current protection.
Increase the softstart to mitigate the current in-rush caused by these
devices.
Change-Id: Ia29c08702db44538fcb467fc38d3933be9df26d7
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
show_resume_irq is used to debug interrupts that cause wakeup.
Support it for spmi arbiter's interrupt controller.
Change-Id: I52d51c09d7ff316248542c84a1cd65a28e2283da
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
Add SDE rotator register read/write access in the debugfs for debugging
support and verification purpose.
CRs-Fixed: 1083137
Change-Id: Ib6c18253f5d8be0f6eba4cfb741c4492b33a4c3f
Signed-off-by: Benjamin Chan <bkchan@codeaurora.org>
The fmax & num_fmax have been updated to reflect the new variable names.
Also update the new frequency of 700MHz to be supported by gfx3d clock.
Change-Id: I57297df9f2819e7d774dbb21302b55ede61a37b2
Signed-off-by: Taniya Das <tdas@codeaurora.org>
Clients that want to influence the size I-Frames emitted by the encoder
can set V4L2_CID_MPEG_VIDC_VIDEO_VENC_IFRAMESIZE_TYPE.
Change-Id: I4e6853022b558069304cde4cff7bc1445fd66213
Signed-off-by: Deepak Kushwah <dkushwah@codeaurora.org>
Disable lpm sleep modes for msmfalcon emulation platform
at boot time as PMIC related functionality is not emulated.
Change-Id: If2309a590ad37547354c0917dd11a202daa9abe4
Signed-off-by: Raju P.L.S.S.S.N <rplsssn@codeaurora.org>
As before, add mtp_tx_req_len for Tx transfer length, while
mtp_write & send_file_work still use MTP_BULK_BUFFER_SIZE for
Tx transfer length, need to correct it.
Change-Id: Ib078cf01871c50e6eec7002a38391d4c41d4d45a
Signed-off-by: zhaoyuan <yzhao@codeaurora.org>
Add UFS and sdhc2 node for QRD interposer msmcobalt. Config
corresponding GPIO to no pull and change its polarity to
enable SD card detection.
CRs-Fixed: 1086932
Change-Id: Ibf9ac87dc605266a90f7364b6618297e66902b39
Signed-off-by: xiaonian <xiaonian@codeaurora.org>
A306a GPU have the two different frequency plans. The frequency
plan needs to be loaded dynamically based on the speed bin
information. Add support for A306a gpu to read the speed bin
information and choose frequency plan dynamically.
Change-Id: Iba53d4381d61f23ce1195a147493b0d292cd3723
Signed-off-by: Hareesh Gundu <hareeshg@codeaurora.org>
Add device tree support for msmcobalt interposer platform
using msmfalcon QRD.
CRs-Fixed: 1086541
Change-Id: If17aa7a60832b71a94d75718da07158e1474ef31
Signed-off-by: Zhenhua Huang <zhenhuah@codeaurora.org>
In case of large value for bufcnt_t or bufcnt,
cmd_size may overflow. Buffer size allocated by cmd_size might
be not as expected.
Possible buffer overflow could happen.
CRs-Fixed: 1084210
Change-Id: I9556f18dd6a9fdf3f76c133ae75c04ecce171f08
Signed-off-by: Xiaojun Sang <xsang@codeaurora.org>
Fix fake button press when headset is inserted by properly
disabling micbias after the detection is completed.
CRs-Fixed: 1086418
Change-Id: I241a49dd36746c083b410a58c8c899ee0e9390ad
Signed-off-by: Phani Kumar Uppalapati <phaniu@codeaurora.org>
There is a race between watchdog being enabled by hotplug and core
isolation disabling the watchdog. When a CPU is hotplugged in and
the hotplug lock has been released the watchdog thread might not
have run yet to enable the watchdog. We have to wait for the
watchdog to be enabled before proceeding.
Change-Id: I88f73603b6d389a46f8e819d9b490091d5ba4fe9
Signed-off-by: Olav Haugan <ohaugan@codeaurora.org>
To move tasks off a cpu when offlining the rq needs to be offlined to
un-throttle tasks. However, tasks might still run on the CPU even after
the CPU has been isolated (per-CPU threads). Thus we should leave the rq
in online state after tasks have been moved.
Change-Id: I61486e8648af0dbb82595fe699e1bc158e837362
Signed-off-by: Olav Haugan <ohaugan@codeaurora.org>
There is a race condition between checking for whether an active load
balance request has been set and clearing the request. A cpu might have
an active load balance request set and queued but not executed yet.
Before the load balance request is executed the request flag might be
cleared by cpu isolation. Then subsequently the load balancer or tick
might try to do another active load balance. This can cause the same
active load balance work to be queued twice causing report of list
corruption.
Fix this by moving the clearing of the request to the stopper thread and
ensuring that load balance will not try to queue a request on an
already isolated cpu.
Change-Id: I5c900d2ee161fa692d66e3e66012398869715662
Signed-off-by: Olav Haugan <ohaugan@codeaurora.org>
The current value is leading to spurious fault interrupts
from the GPU. Increase the threshold 4 times so that hardware
fault detection won't be triggered as quickly.
CRs-Fixed: 1073836
Change-Id: Ie780cec4de818c94a407461580f9d80de7e4ec84
Signed-off-by: Harshdeep Dhatt <hdhatt@codeaurora.org>
The scheduler allocates memory for the task load structures during
fork. It then relies to sched_exit() to be called to free that memory.
However, if the fork itself fails at any point after the allocation,
the memory is left unclaimed forever. Fix this memory leak by freeing
the allocated memory under error conditions.
Change-Id: I14a8290c9fcc4174ec80560e9f9d7bcdb119761f
Signed-off-by: Syed Rameez Mustafa <rameezmustafa@codeaurora.org>
Task load structure allocations can consume a lot of memory as the
number of tasks begin to increase. Also they might exhaust the atomic
memory pool pretty quickly if a workload starts spawning lots of
threads in a short amount of time thus increasing the possibility of
failed allocations. Move the call to init_new_task_load() outside
atomic context and start using GFP_KERNEL for allocations. There is
no need for this allocation to be in atomic context.
Change-Id: I357772e10bf8958804d9cd0c78eda27139054b21
Signed-off-by: Syed Rameez Mustafa <rameezmustafa@codeaurora.org>
