While preparing page tables for fastmap, last level ptes
are not being cache cleaned. Fix this.
Change-Id: I97f894b52484d0d223b15090b94c186bba9af734
Signed-off-by: Shiraz Hashim <shashim@codeaurora.org>
SMB1381 acts as a slave charger in SDM630 QRD board. Add device node
to support it.
CRs-Fixed: 2012488
Change-Id: I03803eddc9db5f9bc7901225fa2defd8bcf0e32d
Signed-off-by: Yingwei Zhao <cyizhao@codeaurora.org>
Currently BCL LMH algorithm enable request goes for every time BCL
threshold enablement. It needs to be enabled only once. So Enable
BCL LMH algorithm only once.
Change-Id: I94c7326b7730830f71b71c92df21a589ddd2347b
Signed-off-by: Manaf Meethalavalappu Pallikunhi <manafm@codeaurora.org>
Just after enabling BCL, reading and evaluating current battery SoC
is bypassed. Because of this, during this same time if battery SoC
is less than preset threshold, BCL doesn't mitigate until next battery
SoC change notification comes. Fix battery SoC read and evaluation
path whenever BCL is enabled.
CRs-Fixed: 2007133
Change-Id: I65639ab078875dc3f6940fd1a89201af98e40881
Signed-off-by: Manaf Meethalavalappu Pallikunhi <manafm@codeaurora.org>
Presently fastmap iommu feature allocates page tables for
full 4GB virtual address space. This can be optimized to
consider virtual address range [base, size] needed by
client and prepare page tables only for applicable
region.
Change-Id: Ie6c23cb8e1702a823567e126f452b1e72d851f71
Signed-off-by: Shiraz Hashim <shashim@codeaurora.org>
If ESR value goes to 0 because of some hardware issue, there is
no way to recover it back from that state. This causes incorrect
SOC reporting leading to a bad user experience. Hence add support
to clamp ESR value based on user defined DT property so that ESR
can be clamped to this value once it is found to go below it.
Since this change modifies ESR value in SRAM, having FG_SRAM_ESR
property would make encode and decode the value easier. Hence
remove fg_get_battery_esr() and get it from FG_SRAM_ESR property.
CRs-Fixed: 2011200
Change-Id: I96250b44f52d6208f3c64fb9e61f70ea41f54f4e
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
Driver is not calling ipc_log_context_destroy in driver
cleanup which leaves the context allocated.
Change-Id: Ic1a74b530836d142c9f1db2143b5700e8b6c3321
Signed-off-by: Hemant Kumar <hemantk@codeaurora.org>
Add sysfs files for user applications to restrict
the battery charge current (FCC). The two files in
/sys/class/qcom-battery/ are -
1. restricted_charging: To enable/disable this feature
2. restricted_current: Restricted FCC (uA)
The default restricted_current value is 1A.
CRs-Fixed: 1113761
Change-Id: I23a6796eaa0c41c2e93a52c45f6200326d262e99
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>
qpnp-fg and qpnp-smbcharger are not supported anymore. Remove them.
Change-Id: Icc010cd77d9d1e839a6dfa681b65e19b8978fb56
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
To trigger WLAN host initiated WLAN FW recovery, platform driver
needs to have service notifier handle. Service notifier handle is
obtained only when service locator locates the WLAN user PD. If
service locator doesn't locate the WLAN user PD then service
notifier handle can be NULL. Add sanity check to make sure PDR is
enabled in platform driver before triggering PD restart.
Change-Id: I5524060cc1f4bfff7faf7f3736455beb73801f4a
CRs-fixed: 2012995
Signed-off-by: Prashanth Bhatta <bhattap@codeaurora.org>
If MHI failed to queue the buffer, do not attempt to re-queue.
Instead wait for transfer completion event and restart
the UL queue.
Change-Id: Id57db52e0eb2e5930ec228a920d109fef941389f
CRs-Fixed: 1055681
Signed-off-by: Sujeev Dias <sdias@codeaurora.org>
On memory stress conditions, host could
fails to allocate memory on atomic context.
Schedule a background worker to allocate
memory in such conditions.
CRs-Fixed: 1037593
Change-Id: Ia48b31622fcb043d31d197fab0a84ab40fc5c0ba
Signed-off-by: Sujeev Dias <sdias@codeaurora.org>
The debug message does not accurately describe the reason
for rmnet to reschedule the request.
CRs-Fixed: 1016968
Change-Id: I49fa6a0dbdd9dec7a36f5705b9e8d27bc7352286
Signed-off-by: Tony Truong <truong@codeaurora.org>
Signed-off-by: Sujeev Dias <sdias@codeaurora.org>
Enable the DRM KMS/GPU driver for the mediabox configuration.
Change-Id: Ic0dedbadf5d12793c13563059872d2970bea8398
Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org>
Enable the various settings to enable A540 DRM/GPU driver on
msm8998.
Change-Id: Ic0dedbadf7d4dbaaa75c24dde64ff13faf1283b9
Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org>
Avoid retry logic in swr_startup API as it results
in speaker mute on sdm660 external codec.
CRs-Fixed: 2012814
Change-Id: Ic8876fd6e62081253a46e4e896d154043d5170db
Signed-off-by: Laxminath Kasam <lkasam@codeaurora.org>
"No Snoop" for RX transactions was previously set as a WA for a
PCIe HW issue. As the PCIe HW issue is fixed, the WA no longer
required.
Removal of the "No Snoop" bit will allow enabling DMA coherency
when SMMU is enabled.
Change-Id: I2030ea7182316ae18483ffb79d0a1de4d90f2fda
Signed-off-by: Maya Erez <merez@codeaurora.org>
if WARN() is called under spinlock, it will lead crash due to
watchdog timeout. Hence fix it by releasing spinlock before calling
WARN(). And also check cdev->config is NULL or not before calling
WARN().
Change-Id: Iebd00932b94164e9f40aa6126a2352437b1141ed
Signed-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>
Update actuator cci master for aux camera sensor of
SDM660 QRD device.
Change-Id: I9426b6cad5ed162f086b434950d2c854a9ba5223
Signed-off-by: Kui Wang <kuiw@codeaurora.org>
Enable config ARM64_STRICT_BREAK_BEFORE_MAKE to detect
break-before-make violations in set_pte and print a warning.
Change-Id: Idb7f5a7a1e46b6738659931188e143acd31a7ffa
Signed-off-by: Srinivas Ramana <sramana@codeaurora.org>
TPDM driver is allocating memory for TPDM datasets at two places which
leads to a memory leak issue.
Fix this issue by getting rid of one allocation call.
Change-Id: I9ac26cabe09dcbabeafd5a14aa85fc59a966d4dd
Signed-off-by: Saranya Chidura <schidura@codeaurora.org>
Thermal clients will be monitoring thermistors for
temperature mitigations. Add emmc_therm support for PM660.
Change-Id: I71f109a3a99b5d962c7101f348141a4cae921a8d
Signed-off-by: Rama Krishna Phani A <rphani@codeaurora.org>