An older accidentally changed this to executable, so fix it back up.
Gotta love windows editors...
Change-Id: I6a142f3506dcccdb35f56e8e27fe7706321882ac
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Git-commit: f75baf8d90bf45221694a1a5f0e5acdcb3245760
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Signed-off-by: Shiraz Hashim <shashim@codeaurora.org>
CPP driver was accessing gdsc registers directly
which is not allowed with upstream clock changes
So use the regulator API to set the mode.
CRs-Fixed: 1105858
Change-Id: I7ff0771fc842913f7fae87e0a0836365fb81c4db
Signed-off-by: Krupal Divvela <kdivvela@codeaurora.org>
Enable CONFIG_MMC_CQ_HCI to support command queue
mode for sdm660.
Change-Id: I72d1ae5a743e1fa7b171e9556cbf261321a0fa87
Signed-off-by: Sayali Lokhande <sayalil@codeaurora.org>
Add sdhc2 support to enable sdcard for
sdm660.
Change-Id: I7038590135bef2981735156a18c3104b0fc9f709
Signed-off-by: Sayali Lokhande <sayalil@codeaurora.org>
Add sdhc1 to support eMMC for sdm660 mtp and
cdp platforms. Also add some missing device
properties for sdm660 simulator and rumi platforms.
Change-Id: I4bea35ebea8e710d82724a3d5098d952b71875f4
Signed-off-by: Sayali Lokhande <sayalil@codeaurora.org>
There is a circular dependency between cpu_hotplug.lock and
HMP scheduler policy mutex. Prevent this by enforcing the
same lock order.
Here CPU0 and CPU4 are governed by different cpufreq policies.
---------------- --------------------
CPU 0 CPU 4
--------------- --------------------
proc_sys_call_handler() cpu_up()
--> acquired cpu_hotplug.lock
sched_hmp_proc_update_handler() cpufreq_cpu_callback()
--> acquired policy_mutex
cpufreq_governor_interactive()
get_online_cpus() sched_set_window()
--> waiting for cpu_hotplug.lock --> waiting for policy_mutex
Change-Id: I39efc394f4f00815b72adc975021fdb16fe6e30a
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
For commit 44aa223a3e ("clk: move check for CLK_ENABLE_HAND_OFF at
unused tree") at unused tree level, prepare and enable counts are
only decrementing for handoff enabled clock(having CLK_ENABLE_HAND_OFF
flag) and counts are not decrementing for their parent clock.
So fixing the same by adding clk_core_unprepare/disable at unused tree
level for handoff enabled clocks so that parent handoff counts also
gets decrement.
Change-Id: Ib238540b2addbe8c9ff7f2e34428169c76e3f44b
Signed-off-by: Amit Nischal <anischal@codeaurora.org>
Remove the unused audio_cal_info_metainfo structure pointer
as it leads to a NULL pointer access and to a crash.
CRs-Fixed: 1105060
Change-Id: I6c7ce3976ac87a7b83a83dbd4ad8f46466f6f813
Signed-off-by: Aditya Bavanari <abavanar@codeaurora.org>
UFS driver can receive a request during memory reclaim by kswapd.
So when ufs driver puts the ungate work in queue, and if there are no
idle workers, kthreadd is invoked to create a new kworker. Since
kswapd task holds a mutex which kthreadd also needs, this can cause
a deadlock situation. So ungate work must be done in a separate
work queue with WQ__RECLAIM flag enabled.Such a workqueue will have
a rescue thread which will be called when the above deadlock
condition is possible.
Change-Id: I91c5bff812be403addc98fbb8c620e67cf28f5d9
Signed-off-by: Vijay Viswanath <vviswana@codeaurora.org>
Modify the driver to support the new lab/ibb
hardware changes supported on PM660A.
New hardware supports the following features:
1) Smart pulse skip mode
2) LDO mode for LAB
3) PFM mode
4) PBS sequencer handling SWIRE decoding
5) Default output voltage configuration
Change-Id: I5461995cc0ac930dd354c63b97223085306e869d
Signed-off-by: Kiran Gunda <kgunda@codeaurora.org>
In polling mode, driver is using the top level busy and
error status for completion check. This is not correct
for regdma because it has separate status register and
software timestamp. This patch corrects regdma to wait
for the appropriate status register and checks for software
timestamp for timeout.
CRs-Fixed: 1096834
Change-Id: I18f8ab14be1db4d24954115b763e6ac749b71b4d
Signed-off-by: Alan Kwong <akwong@codeaurora.org>
Signal retire fence on first vsync after frame has been programmed to
hardware. This indicates when the frame starts being fetched by
MDSS hardware.
CRs-Fixed: 1081525
Change-Id: Ib69f64ff17a1609b67ff34ef277f658bfa5cfb5a
Signed-off-by: Adrian Salido <salidoa@google.com>
(cherry picked from commit 80d5d7558ac98c56527cb1040dab3fc5f438ab51)
Signed-off-by: Abhijit Kulkarni <kabhijit@codeaurora.org>
Just wait for the display to idle instead and immediately start
the next commit. This reduces the depth of the commit pending
queue.
CRs-Fixed: 1081525
Change-Id: Ic4ee6f738f5fa77890e806b55d9a0304915761ea
Signed-off-by: Naseer Ahmed <naseer@codeaurora.org>
Signed-off-by: Abhijit Kulkarni <kabhijit@codeaurora.org>
Add required panel sequences and timings for command mode
and video mode 2k truly panel in dsc compression mode.
Change-Id: I81eed3495f8be633d2b3fd92d63cd280fce7b4f0
Signed-off-by: Ashish Garg <ashigarg@codeaurora.org>
GPU subsystem in sdm660 is supplied by either LDO300(VDD_GFX) in
LDO mode or VDD_CX in BHS mode. This LDO300 is CPR managed and supports
CPR closed-loop operation. Add CPR device node with required configuration
for supporting CPR closed-loop operation for sdm660.
CRs-Fixed: 1068294
Change-Id: Id12a50563f6cef196ef76816fcf8e177b9a3fa97
Signed-off-by: Tirupathi Reddy <tirupath@codeaurora.org>
This patch frees up the dynamically allotted memory
when met with error condition and function return.
CRs-Fixed: 1106180
Change-Id: I01446fbdbb422dcb025ee50929b32f40a5a78681
Signed-off-by: Manoj Prabhu B <bmanoj@codeaurora.org>
Presently we read a length of 80 character to dump subsystem
crash reason in case of err fatal on subsystem. Making it 130
character to dump additional info provided by subsystem.
CRs-Fixed: 1083000
Change-Id: Icaf4c27862984148c7125332ef7531b2a61f4ea2
Signed-off-by: Avaneesh Kumar Dwivedi <akdwived@codeaurora.org>
This patch addresses the scheduling conflicts of
control channel removal work by listening
to peripheral events.
CRs-Fixed: 1081265
Change-Id: Ib9f2448e564c4800535bd80d13c9bda5cc283c3c
Signed-off-by: Manoj Prabhu B <bmanoj@codeaurora.org>
In certain cases, an RCG might be prone to being enabled even
though the overlying software thinks that it disabled the RCG.
In order to avoid letting the RCG go into an invalid state, support
parking it at a safe frequency during clk_disable() and deferring
all the RCG configuration updates to be done during clk_enable(),
if a scaling request comes in whilst the clock is disabled.
Change-Id: I55f1d1d346182a2b480127c57d6659fc9a63331b
Signed-off-by: Deepak Katragadda <dkatraga@codeaurora.org>
