Previously ASPM L1-Sub-States control registers (CTL1 and CTL2)
weren't saved and restored during suspend/resume leading to ASPM-L1SS
configuration being lost post resume. Save the ASPM-L1SS control
registers so that the configuration is retained post resume.
Change-Id: Iaf8e873aca798557eb38c2ea105dcaadff998e86
Signed-off-by: Hemant Kumar <hemantk@codeaurora.org>
Make sure the right sequence of virtio i2c access.
Change-Id: I786ee11c5a3166db52531e271a22d53cc607e9a6
Signed-off-by: Yimin Peng <yiminp@codeaurora.org>
The new version of the compliance suite expects each
interface that advertises the remote wakeup capability
to generate a remote wakeup event in Superspeed mode.
The compliance suite ensures this by selectively
suspending each interface at a time and then expects
the interface to initiate a remote wakeup.
The current debugfs implementation though initiates
remote wakeup only on the first connected interface.
Hence change the implementation to initiate remote
wakeup by the interface which is selectively suspended
by the host in Superspeed mode. Whereas in Highspeed
mode initiate remote wakeup on the first connected
interface.
Change-Id: I45797e867aee17c5dcc592fe1e08b5a3943b4a8b
Signed-off-by: Sriharsha Allenki <sallenki@codeaurora.org>
Signed-off-by: Mayank Rana <mrana@codeaurora.org>
Before initiating trusted touch, wait for suspend or resume to
complete. Similarly, before starting suspend or resume, wait for
trusted touch session to complete.
Change-Id: Ic79f92545ef70a815fb63772b94274959974ea75
Signed-off-by: Ritesh Kumar <riteshk@codeaurora.org>
This change declares set of APIs to fix linking errors seen with client
driver compilation when CONFIG_QCOM_LLCC is not enabled.
llcc manager's client driver doesn't use core llcc driver APIs. Hence
it doesn't need to include llcc-qcom.h. This results into below warning
while compiling client driver.
warning: declaration of 'struct llcc_slice_config' will not be
visible outside of this function [-Wvisibility]
Hence include llcc-qcom.h within llcc-slice.h file. So llcc manager's
client driver doesn't need to directly include llcc-qcom.h file as it
doesn't use any of core driver APIs.
Change-Id: If7232818856876be170af9d2fa7633ff3791d3f2
Signed-off-by: Mayank Rana <mrana@codeaurora.org>
