Skip pci link recovery for EACCES error returned
from msm_pcie_prevent_l1. Do link recovery only
if the error is EIO.
Change-Id: I037a729e282e22e8c7174f83c61a58fa0faad579
Signed-off-by: Mohammed Siddiq <msiddiq@codeaurora.org>
While trusted touch is underway, block resume work
to flush touch FIFO since ownership of register space
is with Trusted VM. Additionally add extra regulator
vote before starting TUI.
Change-Id: I50e94400e467194b5caf615bdbd0d2f4d8630a96
Signed-off-by: Shashank Babu Chinta Venkata <sbchin@codeaurora.org>
While trusted touch is underway, block resume work
to flush touch FIFO since ownership of register space
is with Trusted VM.
Change-Id: Ibcd7274c560ddc9eae4eb9218198ab5039acdc18
Signed-off-by: Shashank Babu Chinta Venkata <sbchin@codeaurora.org>
Signed-off-by: Ritesh Kumar <riteshk@codeaurora.org>
Checking if there is enough room in between the offset of the
two subsequent field so that data of field 2 will not overlap
the data of field 1.
Change-Id: I96f656bb25878a302e7de109dd8f981045ed52e7
Signed-off-by: Nitin LNU <nlakra@codeaurora.org>
GSI Driver get the usage count in work handler when set_alt 1 happens
and this counter will decrement in disconnect work due to cable disconnect
or in gsi_suspend for suspended state.
In this case set alt to 0 came for MBIM interface and clear the
data_interface_up flag. After that suspend happens and does not decrement
the counter in gsi_suspend. This causes a mismatch of usage count and
usb not entering to low power mode.
Fix this by checking for USB_PROT_GPS_CTRL instead of data_interface_up.
Change-Id: Iaabf3de46ed72e33980d1e3e386e8ca0ae651c74
Signed-off-by: Chandana Kishori Chiluveru <cchiluve@codeaurora.org>
Some hosts enable function remote-wakeup immediately after
enumeration. But they don't perform function_suspend before U3
and also don't disable function remote-wakeup even if entering
deep sleep state and don't intend to wakeup from USB. One of the
reason could be that they rely on device to initiate remote-wakeup
only if it function suspended. Hence, update the check to initiate
function remote-wakeup only if device is function suspended.
Change-Id: I3d6bb817d9174f94051b1e1ef74dc9c941c66f4c
Signed-off-by: Manu Gautam <mgautam@codeaurora.org>
Remove debug measure support for clocks that are not registered with the
clock framework. While at it update the external clocks in debugcc to
measure only clocks.
Change-Id: Icd6d59a098d116074403d24d9bc990fdebd7bdd7
Signed-off-by: Jagadeesh Kona <jkona@codeaurora.org>
Currently, certain controllers with lower core clock rates, takes
more than 32ms to set the halted bit. This results in XHCI halt
timeout.
Fix this by increasing the timeout to 48ms.
Change-Id: I2f2715a11a947e01303c659e257ef0cabb311cac
Signed-off-by: Harsh Agarwal <harshq@codeaurora.org>
Add MSS_Q6_BIMC_AXI and MSS_CFG_AHB clock IDs for GCC and clients
to be able to request for clocks from these clock controllers.
Change-Id: I2a7315d8d40348cf08515be9a43ad004f0c1d064
Signed-off-by: Rakesh Kota <kotarake@codeaurora.org>
Add GPIO to PDC wakeirq map.
While at this also update direct connect irq map.
Change-Id: I6c1f485f33077f95473c93b981ab7bec683ccf9f
Signed-off-by: Maulik Shah <mkshah@codeaurora.org>
Enable config to support basic network functionality
Acked-by: Utkal shah <c_ushah@qti.qualcomm.com>
Change-Id: Id04a561687924aafd6342a4cf833ee695609db7a
Signed-off-by: Paras Singh Jain <parassin@codeaurora.org>
Fix out-of-bound array access by using the right
offset-mask in getting the OTST status.
Change-Id: I89a4176251ea9157c5dd997b3c11bfcb07420a4f
Signed-off-by: Kiran Gunda <kgunda@codeaurora.org>
This changes avoids device crash if Rf card is not present
in device.
Change-Id: I4b22ad0023a38e5b3ef49d6bf0e404b00c608115
Signed-off-by: Sandeep Singh <sandsing@codeaurora.org>
Return EACCESS instead of EIO when link access is not
allowed at prevent l1, so client driver will procced
based on the return value.
Change-Id: Iee3b9a65609db1272be550089948d07527c7e134
Signed-off-by: Vivek Pernamitta <vpernami@codeaurora.org>
UFS controller in the newer target supports UFS HCI specs
version 3.0. Hence Adding UFS3.0 in UFS HCI version check
to avoid logging the error message.
Change-Id: Ibbbb482a26a3ffd50667615bf2795404381a4111
Signed-off-by: Nitin Rawat <nitirawa@codeaurora.org>
SLIMBUS_MSM_NGD should be m not y for the current
device to be normally boot up and function.
Explicitly mark CONFIG_SLIMBUS as m as well for
normal function.
Change-Id: I09502c2300f9ee5fe06a82146b5832a13a576cff
Signed-off-by: Maria Yu <aiquny@codeaurora.org>
