Currently the handler skips calling the update function
but uses the final result from the votable not_ok_to_qnovo_votable.
Fix it by calling the update function so it gets a chance to vote on
not_ok_to_qnovo_votable.
Moreover do not return early from ptrain_done handler without setting
QNI_PT_VOTER's vote on pt_dis_votable. This is a self clearing bit and
unless QNI_PT_VOTER's bit is removed, the next restart may not trickle
down to hw.
Change-Id: I0a860287b638d20b6a4aa05c7bb25e9b81a980d2
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
Usually, DC path is connected to a wireless charger. It is advisable
to disable qnovo when charging wirelessly.
Disable qnovo for dc path unless a property in device tree is set to
specifically enable qnovo for dc path.
Change-Id: I4ca475f30ca0a564f533b4ed8bcd55cfb5da291f
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
If a charger was already present at bootup, we may not delay the start
of qnovo by 15 seconds.
Fix it by setting the chg_ready votable to false during init.
Change-Id: Icf185763576f65028cf2ef0d1c0bbcf6570460ba
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
While shutting down set the not_ok_to_qnovo votable to true, so that
we skip measuring ESR if a pulse train done interrupt triggers right
during the shutdown.
Change-Id: If3a0a8e9b1d60920cbbedc16af91c05caec8dcb2
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
Sometimes we observe that the ptrain_en bit is reset back to 0 while
in restart work.
Set it again if so.
Change-Id: I15d46f96a8b751f0386677e3b6876eec8bba9a1f
Signed-off-by: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
SDM636 inherits all SDM660 GPU properties, but it will support
GPU max frequency 370Mhz and DDR max frequency 1353Mhz.
Change-Id: I35c4e90a264109d9b490eeac762e79440bd46800
Signed-off-by: Hareesh Gundu <hareeshg@codeaurora.org>
If for some reasons like ioctl fuss test or reading dpcd caps failed,
max lane count supported might be zero. In such cases handle link clk
calculation gracefully.
Change-Id: I7cb08abce76025930681f6532c03708793d3acc4
Signed-off-by: Narender Ankam <nankam@codeaurora.org>
Mount QT800S suspend and resume actions to early fb event,
so speed up touch response.
Change-Id: I1ca610131e94af806dab4dfa8709fdd9c0556971
Signed-off-by: Jin Fu <jinf@codeaurora.org>
Update the function return value and input scm_ret variable
type for restore secure configuration in scm_restore_sec_cfg() fn.
Adding scm_ret input variable for scm_get_feat_version() fn.
Change-Id: I5fff488f973b018f898eef616801a4b5e5a900fb
Signed-off-by: Zhiqiang Tu <ztu@codeaurora.org>
Config sleep state for wlan bootstrap pin and add fixed regulator
support for wlan_en.
Change-Id: I1fa7ccb98b6667e2f212a658d02a4c2b68da4f89
Signed-off-by: Zhiqiang Tu <ztu@codeaurora.org>
Revert this change to avoid TZ dependency in OTA upgrades.
This reverts commit 46756eb931
Change-Id: I2227d1dfa19fa75ea25d42702a9757043b8d63dd
Signed-off-by: Tharun Kumar Merugu <mtharu@codeaurora.org>
Synchronize camera_v4l2_open and camera_v4l2_close to avoid use
after free.
Change-Id: I1a203ae0753b265594f616496ab8c57e0521fd9f
Signed-off-by: Trishansh Bhardwaj <tbhardwa@codeaurora.org>
In SDM636 target CPU frequency corners are updated this
calls for a change in memlat and mincpu node cpufreq to
DDR mapping.
Change-Id: Ief1bf8c3b177b35e6ad178656c736b68401a1845
Signed-off-by: Santosh Mardi <gsantosh@codeaurora.org>
As per the hardware documentation, operating limits of WLED is
from 0.4% to 100%. Cap the lower limit to 0.4% to ensure proper
operation.
Change-Id: I7ee2684ea2186d4fdda5cea9a4d421b429a6d4fd
Signed-off-by: Subbaraman Narayanamurthy <subbaram@codeaurora.org>
During Modem graceful shutdown, QMI messages from WLAN FW can
still be delivered to host even after icnss receives Modem
shutdown notification from SSR framework. So prevent processing
any such messages from FW after Modem shutdown.
CRs-Fixed: 2095386
Change-Id: Ice21d043393b0f7b97aaccd68e1b28702cc9e393
Signed-off-by: Sameer Thalappil <sameert@codeaurora.org>
The invalid slave_info is used by msm_sensor_driver_probe.
This causes crash when ioctl VIDIOC_MSM_SENSOR_INIT_CFG is
called repeatedly.
CRs-fixed: 2090483
Change-Id: I467c0a19d84658fb33da9677dcb904ebf49e4800
Signed-off-by: Rahul Sharma <sharah@codeaurora.org>
No upper-bound validation is performed when reading number of
extended CEA blocks from the untrusted source (EDID). Add a check
to limit the number of CEA extension blocks.
Change-Id: I69f09ed0ad28a4c267cf3e8f7a12efe46f75e244
Signed-off-by: Narender Ankam <nankam@codeaurora.org>
Change IPA firmware loading on MDM devices to use
Linux PIL instead of manual loading.
Loading with PIL is more secure. Firmware needs
to be signed and then authenticated by Trust Zone.
Change-Id: If8bda76795dcd000327c6f6345a9b38474b609fd
Signed-off-by: Ghanim Fodi <gfodi@codeaurora.org>
If glue driver's probe failed, it tries to remove child devices
as part of of_platform_depopulate during cleanup. This results in
calling dwc3 core platform device's remove callback dwc3_remove().
This function is calling phy_set_suspend() for both HSPHY and SSPHY
to suspend them. But it is resulting in crash due to unclocked access.
Remove those calls, which are not required as glue driver will take
care of suspend/resume PHYs.
Change-Id: I3e107c4beb29373d4a1c783bd2be7a128f52317e
Signed-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>
Adding a NULL check before disable regulator to make sure
that its not released before
Change-Id: I21ff1649db3e00588f1c320418fca270bc0264bc
Signed-off-by: Vijay kumar Tumati <vtumati@codeaurora.org>
spcom_device_poll() return POLLERR rather than -EINVAL.
Change-Id: Ifce0fa9c6a0a5136ae1d109543a9345ad77359bf
Signed-off-by: Amir Samuelov <amirs@codeaurora.org>
As part of optimization in msa permissions assignment
source and destination vmids are introduced as uninitialized
arrays.
The fix is for initialization of the array as zero initially
so that variables doesnot have the garbage value from the stack.
Change-Id: Ie30d61f3be9ed5a5a2cef2e63348d987e894c22a
CRs-fixed: 2096940
Signed-off-by: Anurag Chouhan <achouhan@codeaurora.org>
Update the TUNE2 parameter by adjusting the programmed tune2 value
with the correction value, if mentioned in dtsi to improve rise/fall times.
In case efuse register value is zero after correction, write previous TUNE2
register value as it is instead of writing hardcoded value. And correction
value should be between [-10 5] in order to take into consideration while
updating TUNE2 register with fused value.
Change-Id: Iaf61705bfd0c7b2cb62de8816c912f05876f001c
Signed-off-by: Vijayavardhan Vennapusa <vvreddy@codeaurora.org>
