Enable the various settings to enable A540 DRM/GPU driver on
msm8998.
Change-Id: Ic0dedbadf7d4dbaaa75c24dde64ff13faf1283b9
Signed-off-by: Jordan Crouse <jcrouse@codeaurora.org>
Add memset of adm open v5 and v6 structure before
value assignment to avoid warning of uninitialized stack.
CRs-fixed: 1112462
Change-Id: I18681f6b191e96118fde9ae774d105dc6b677858
Signed-off-by: Derek Chen <chenche@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>
Save the previous satates of HVX . enable or disable
hvx only if the previous state is different from current state.
Change-Id: I24081d1fccff17a0da26ff213df056c7a1cb6388
Signed-off-by: Senthil Kumar Rajagopal <skrajago@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>
There is no bound check on dual_hw_ms_cmd->num_src,
which is coming from userspace
num_src is used as the limit for the for loop.
The max num_src can hold is 255 (type uint8_t).
This implies that i can go upto to 254.
However dual_hw_ms_cmd->input_src can only hold 5 bytes.
So, we may acces out of bound array.
CRs-Fixed: 2006169
Change-Id: If5927e06e70cce4afb0ae9f2cdfec80f76f83771
Signed-off-by: Senthil Kumar Rajagopal <skrajago@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>
Unsanitized pointer after kfree leads to potential risk.
Set pointer to NULL.
CRs-Fixed: 2008031
Change-Id: Ia59a57fcd142a6ed18d168992b8da4019314afa4
Signed-off-by: Xiaojun Sang <xsang@codeaurora.org>
Add the minimum and maximum fps supported and enable dynamic
fps and esd for fhd video mode panel. Enable ESD, ULPS for
NT and Truly command mode panels. Enable partial update for
truly fhd command mode panel.
Change-Id: I0fe5502d74903e13544603154e853f4b486ca7be
Signed-off-by: Ashish Garg <ashigarg@codeaurora.org>
OLEDB driver needs the LAB_VREG_OK status to program the PD_CTL
register after the oledb module is enabled. As this status register
is not accessible from the OLEDB driver, register a notifier callback
with LABIBB driver to get LAB_VREG_OK status.
Change-Id: I85009688a2accb6246135d22e08ee21fb8296f62
Signed-off-by: Kiran Gunda <kgunda@codeaurora.org>
With QUP in shared mode, enabling and disabling the
resources in runtime pm will cause failure of
transactions over the QUP that are running on other
execution environment. To avoid the failure
enable/disable gpios and clocks of QUP per transfer.
Also move the clock prepare and unprepare calls
to runtime pm APIs from the transfer API to
reduce the latencies in the transactions.
Change-Id: Ic697cdc544405d86ec7c675922c18c00fec451a6
Signed-off-by: Dilip Kota <dkota@codeaurora.org>
Signed-off-by: Shrey Vijay <shreyv@codeaurora.org>
Add sub-device node to allow mba to be able to load in carveout
memory region for SDM660.
Change-Id: I0e9932a0a779a66b7a3d4b682a60885cb7d799c5
Signed-off-by: Gaurav Kohli <gkohli@codeaurora.org>
This reverts commit 3e47c53624 ("firmware_class: Add an
additional path to fw_path list").
Adding /firmware/images entry in fw_path is introducing selinux
denials as the access was happening under the client process
context. Removing the entry from fw_path structure.
Change-Id: I359f8defe49595a7e53558992080cb94eba42451
Signed-off-by: Satya Durga Srinivasu Prabhala <satyap@codeaurora.org>
Commit dbca823c25bf ("f_gsi: Don't send end xfer command when USB is
into U3 state") consolidated below usecases path for RNDIS:
1. USB RNDIS adaptor disable/enable case
2. USB RNDIS suspend/resume case
3. USB cable connect case
Due to USB GSI endpoints are getting disabled as part of above usecase
1 i.e. adaptor disable, it is required to reconfigure and re-enable USB
GSI endpoints when adaptor is enabled. USB GSI endpoints are re-configured
but not re-enabled for above usecase 3 although it is already configured
and enabled as pat of set_alt(1). Hence USB GSI endpoint are partially
configured causing no USB data transfer between USB GSI and IPA GSI which
fails IP address assignment. Fix this issue by making sure that USB GSI
endpoints are not reconfigured in above usecase 3.
CRs-Fixed: 1095920
Change-Id: I67068bac21274d715f61f9e5b83fae54e2c8e22d
Signed-off-by: Mayank Rana <mrana@codeaurora.org>
It is recommended to avoid sending end xfer command with USB GSI
endpoint when USB is into U3 state (i.e. bus suspended) as USB
controller may hang. USB GSI driver sends end xfer command with
suspend implementation when remote wakeup is not allowed. Hence
update IPA driver about remote wakeup status to suspend or
disconnect IPA GSI channel whereas remove sending end xfer command
to USB controller when remote wakeup is not allowed.
CRs-Fixed: 1077546
Change-Id: I3ac3714ccaf4ac9f16c26f59b9550aa825483344
Signed-off-by: Mayank Rana <mrana@codeaurora.org>
USB function driver uses usb_gadget_autopm_get() API to increments
USB controller device's PM runtime usage and child count, and also
expects that USB controller is resumed. Late suspend disables USB
controller device's PM runtime functionality by incrementing
disable_depth count and early resume enables it back once system is
resumed. This results into pm_runtime_get_sync() returning -EACCESS
when APPS is power collapsed and it is resuming due to USB bus resume
case. usb_gadget_autopm_get() API is decrementing device's PM runtime
usage count if it receives error value from pm_runtime_get_sync() API.
USB function driver doesn't check return value which results into
continuing USB operation. On next bus suspend, it decrements usage count
although it was not incremented in previous resume case which makes PM
runtime usage count negative. This can cause multiple issues as below:
1. USB bus resume may take more time causing host re-enumerating USB
gadget device
2. Unclock register access on remote wakeup case
3. USB host mode enumeration may fail due to dwc3 device usage count
is negative.
Fix this issue by making usb ipa wq as freezable workqueue which will
make sure that ipa_work_handler() work is executed only after system is
resumed and USB controller device's PM runtime is enabled.
CRs-Fixed: 1075002, 1074383
Change-Id: I300d1a0081fafcbef3c00c63cddd49be54a651e5
Signed-off-by: Mayank Rana <mrana@codeaurora.org>
usb_func_ep_queue() returns -EAGAIN if usb is function suspended and
successfully remote wakeup is performed. This change fixes error
handling with USB GSI function driver to make sure caller knows that
request is actually queued or not from this context. This makes sure
that USB request is queued once USB host has resumed USB bus.
CRs-Fixed: 1033093
Change-Id: I3f3cb1b6b42530bfa93e0d4badacfe651b6bbb4c
Signed-off-by: Mayank Rana <mrana@codeaurora.org>
Unregister glink notification handle after SSR as otherwise it results
in the link up notification to be skipped resulting in incorrectly
completing the port open notification.
Change-Id: I668de44163a702faade1f170a74f66fb5a0c5571
Signed-off-by: Sathish Ambley <sathishambley@codeaurora.org>
Increment GSI command timeout. This is needed since during Q6 GSI FW
authentication GSI HW is disabled and the response for the HW may be
delayed.
CRs-Fixed:
Change-Id: Ia9ed0f0163abbfd3e242c38a9aea084c1c37e8fd
Signed-off-by: Gidon Studinski <gidons@codeaurora.org>:
