CURRENT_QNOVO - force fast charge current value
VOLTAGE_QNOVO - force float voltage value
CRs-Fixed: 2004173
Change-Id: I7569052fd2cb6d1ce9a3a8e69e79b950a6c62d57
Signed-off-by: Harry Yang <harryy@codeaurora.org>
FCC_MAX votable was introduced as an intermediate votable used by
Qnovo driver for fast charge current vote, but does not fit in
the new requirement that Qnovo force its vote value.
Remove it.
CRs-Fixed: 2004173
Change-Id: Iff8b74113550f808546d61ef864f3935fc5d61fa
Signed-off-by: Harry Yang <harryy@codeaurora.org>
Input suspend on fake battery feature is by default enabled in the
software, add a DT property to enable/disable the feature.
Change-Id: I06bda6c72010699f4be24ff6044fe3bb248b06fb
Signed-off-by: Ashay Jaiswal <ashayj@codeaurora.org>
Signed-off-by: Harry Yang <harryy@codeaurora.org>
As per the hardware recommendation, a delay of 500 us is needed
after LMH mitigation is enabled by software and before the flash
LED is strobed. Add it.
Change-Id: Ib70efbb7267510ffb9d95c4aba8566bf6e777c0f
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
Incorrect checks in MHI drivers may crash the system.
Fix these checks so that MHI drivers will handle the
errors gracefully.
Change-Id: I462263799c2e76573300ed43b51e39ecba42914b
Signed-off-by: Tony Truong <truong@codeaurora.org>
Kernel address is relocated to the VMALLOC region. Update the check
to use KIMAGE_VADDR.
Change-Id: Ie2539a78a8180a3dbc2c8075a891e99892d809f2
Signed-off-by: Runmin Wang <runminw@codeaurora.org>
On pipe setup, enable data path should happen for after
all pipe resources are allocated.
This change prevents a race condition where the pipe is enabled
before RX buffers are submitted to IPA.
Then, when buffers are submitted to IPA there is a race between
submitting the buffers and getting RX packets.
CRs-Fixed: 1096357
Change-Id: Ic32924b6893bb8c7813b1b8e68e03b5e09560b69
Acked-by: Ady Abraham <adya@qti.qualcomm.com>
Signed-off-by: Skylar Chang <chiaweic@codeaurora.org>
Enable QCOM_EL2_TLB_HANDLER so that tlb conflict is handled
by EL2.
Change-Id: I8af8be929293e5419d58712d742cb62fb82f8897
Signed-off-by: Runmin Wang <runminw@codeaurora.org>
Raise exception to EL2 for every EL1 sync data aborts,
so that EL2 handles the TLB conflicts.
Change-Id: Ib140599e23c399b23c12ddbeb59979d6caf5d38e
Signed-off-by: Prasad Sodagudi <psodagud@codeaurora.org>
Signed-off-by: Runmin Wang <runminw@codeaurora.org>
HL1.0 wmi type configuration is overlapped with wmi
TLV type configuration.
converge TLV and HL1.0 params and API to remove
redundant code.
Change-Id: Ia41b300ca810495acfdab9f014f59d8cfa839ae3
Signed-off-by: Govind Singh <govinds@codeaurora.org>
Clock trace events related to msm clock framework are
not required to be part of available events other that
CLK_MSM config so add the support for the same by
adding a config check.
Change-Id: I93e8d9604a58c0cb48be723d5845591e7a4b7861
Signed-off-by: Amit Nischal <anischal@codeaurora.org>
Execute pinctrl operations at correct place in
suspend/resume procedure of gpio_keys driver.
Change-Id: Ic393778e35f52859512bd32ccbf6c4d1079a7e37
Signed-off-by: Shantanu Jain <shjain@codeaurora.org>
Update the dtsi property to limit the maximum pixel clock frequency
supported on Display Port for SDM660 to 300 MHz.
Change-Id: Iaacb08a310debd0d470d2f16c794fe70b09af2f5
Signed-off-by: Padmanabhan Komanduru <pkomandu@codeaurora.org>
The fractional divider values for DP pixel clock RCG needs to be
determined dynamically. Add the recalc_rate operation for the DP
PLL mux clock dp_vco_divided_clk_src_mux which is the parent of
DP pixel clock RCG. This enables the RCG clock to calculate the
fractional dividers correctly. Modify the determine rate op for the
mux clock to also set the new parent after performing the determine
rate operation.
Change-Id: Id931a60677380ecee28eb9aec6468548898b812b
Signed-off-by: Padmanabhan Komanduru <pkomandu@codeaurora.org>
Add mdss node for sdm630 which is used by
display driver.
Change-Id: Ie5b6448a9a6da59ea1a134db3c700e35f89da50b
Signed-off-by: Jayant Shekhar <jshekhar@codeaurora.org>
Signed-off-by: Sandeep Panda <spanda@codeaurora.org>
MSM GPIO 64 is connected to camera focus button and MSM GPIO 113 is
connected to camera snapshot button. Add the device nodes for these
buttons for SDM630 devices.
Change-Id: I7f58f3ed6e7cfa49f03ebea23cff4eae417a071b
Signed-off-by: Shantanu Jain <shjain@codeaurora.org>
GPU subsystem in sdm630 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.
CRs-Fixed: 2000929
Change-Id: I94d6739f9abbdba3918b118eaa29fc0bc5cbd6e7
Signed-off-by: Tirupathi Reddy <tirupath@codeaurora.org>
CTM needs to vote for USB ICL. Add support for it.
Change-Id: I88b146000f7327cf5dc7310fb721309f08dc3035
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
POWER_SUPPLY_PROP_CTM_CURRENT_MAX is needed by CTM to limit USB input
current. Add it.
Change-Id: I8aac65a91959300676cf7e1c2685a557f322c509
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
The die and connector health properties expose the comparator output of
the thermal regulation. If both die and skin temperature regulation is
enabled then the output of the comparator will be the higher of the two.
The property values can be one of: Unknown, Cool, Warm, Hot, Overheat.
Change-Id: Ic92c9cb08ec42fd2c2f26a54687a17e3b05b388f
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
The DIE_HEALTH and CONNECTOR_HEALTH properties are used to show the
output of the thermal regulation TEMP_RANGE.
Change-Id: Ice3f159b7775084bdd0099047d4660a1e5edce98
Signed-off-by: Nicholas Troast <ntroast@codeaurora.org>
Add support to vote for ICL based on charger type.
Following are the current limit for chargers:
Legacy adapters:
CDP: 1500mA, DCP: 1800mA, HVDCP: 3000mA
TypeC Adapters:
Based on the current advertised by the adapter.
Change-Id: Ia5dbf73c29949a94e096ca6233a33c40da744140
Signed-off-by: Ashay Jaiswal <ashayj@codeaurora.org>
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
The tz_log driver is responsible for allocating the memory for the
'qsee_log' buffer. If tz_log driver is disabled and some part of the
bootchain has set the qsee_log address before Linux booted, then that
previous address will continue being used. If that address overlaps
with memory used for some other purpose, logging to qsee_log may
scribble on memory and cause a crash.
Change-Id: I10d69355beeb252115a0d91cfabfa8b9e729c969
Signed-off-by: Matt Wagantall <mattw@codeaurora.org>
Use NOM ACC settings up to TURBO voltage corner for APC0/1 for
sdm630.
CRs-Fixed: 2005083
Change-Id: Ifa50b62c5b8ae46a691d260f3517a4bc410d19c3
Signed-off-by: Tirupathi Reddy <tirupath@codeaurora.org>
Add the sdm630 compatible string to MDSS PLL driver
of_device_id table list, so that initialization of
MDSS PLL driver takes place for sdm630 platform.
Change-Id: I284ff9c07a4a971260ade399a2f7a605003ccf1d
Signed-off-by: Sandeep Panda <spanda@codeaurora.org>
