| Commit message (Collapse) | Author | Age |
| ... | |
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add WMI_MAWC defs.
CRs-Fixed: 865207
Change-Id: I0aa757006a20d613f1ae54b5006109562db52849
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
For debug purpose, print some key ROME config space and SOC registers
if it fails to write/read the register to enable ROME side interrupt
during resume.
Change-Id: I789f3200712ec59d2e08995c60ad0de2250b7ade
CRs-fixed: 919466
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Host avoid SSR injection ioctl using hdd->isLoadInProgress,
But ol_target_failure handler checks for the
vos_is_load_unload_in_progress. As these two flags are not
set back to back so there is possible time window in which
SSR ioctl is allowed but ol target failure handling is not
allowed.
Change-Id: Ib97d3693f82f6ca94fa048a8120786065e99087a
CRs-Fixed: 913741
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
while processing ft pre auth response, if memory allocation fails
then host is not setting psavedFTPreAuthRsp to null. Later sme is
freeing same memory as freeing pMsg->bodyptr. Hence on next
disconnect, sme_FtReset try to free psavedFTPreAuthRsp which is
already free.
As a part of this fix, host ensure to set psavedFTPreAuthRsp
Null in all cases.
Change-Id: I144786cd4206bf273d2ffa63889af109cd2744dd
CRs-Fixed: 916416
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Watchdog thread is not needed for qcacld driver, hence disable it by
gEnableLogp ini flag.
Change-Id: I7fb0d48fb0af04c462477a23ed81386470df41d2
CRs-fixed: 917266
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Release 4.0.10.193
Change-Id: I09f9ae621879e2a1b81e51b3c55e78fad00a9221
CRs-Fixed: 688141
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Runtime PM creates context for the wakelock during their initialization.
The Context uses adf memory allocation API's which adds the memory pointer
to the list to track the memory leaks in Slub debug builds.
The List's are initialized late in the sequence after wlan wakelock
is initialized, this results in a stability crash.
Fix it by initializing the Timer list and memory list early in the driver
load sequence.
Change-Id: I0fe836bcc637f2e555daca32cf1c12f706d2063a
CRs-Fixed: 918440
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As per current implementation MC thread is blocked for 60 sec on
TX management frame download failure. Continuous instances of the
above issue is resulting in active command timeout.
Inject firmware crash on continuous management tx failure to get
firmware dump which will help in debugging the issue.
Change-Id: Ib86ad472ac2e4dc3b3d0758278162c68365130fb
CRs-Fixed: 911580
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add support to configure RM enabled capbility information element
through INI.
Using the introduced INI config option(rm_capability), we can set
or unset any bit in the IE. Default value for the config parameter
is set based on rrmInitialize routine.
Change-Id: Ia2a4352760db77ab71dad4757eb603d7539ffefa
CRs-Fixed: 918667
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Update RM enabled capabilities IE as per latest specification.
RM enabled capabilities structure is udpated as per the draft
version Draft P802.11REVmc_D4.2.
Change-Id: I8e8f3b48a23251907eebb482df45952c75e64b9e
CRs-Fixed: 918667
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Instead using Rx packet count which host driver received from FW,
changed to use IPA Rx exception packet count.
Change-Id: Iadba0234eff5456478eefcac0107818f72b44d37
CRs-Fixed: 918779
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This fix allows station to roam to the AP which has same pmf profile
or configuration as current connected AP.
CRs-Fixed: 871445
Change-Id: Iec0905e1ff33c46f93f3d5f159d155e37a28f470
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
prima to qcacld-2.0 propagation
When disassoc request is received from peer and at the same time
if deauth request is received from supplicant, LIM cleanup
may not happen properly as there is a chance of session deletion
in limSendSmeDeauthNtf while cleanup in progress from
limProcessSmeDisassocCnf. This can result in not sending delbss to FW.
Hence, FW can crash when config bss is sent for new connection.
Following changes are added to handle this.
1. Add state eLIM_SME_WT_DISASSOC_STATE in __limProcessSmeDeauthReq
and allow host to post LIM_MLM_DEAUTH_REQ instead of invoking
limSendSmeDeauthNtf, where session is deleted.
2. Send eWNI_SME_DEAUTH_RSP if cleanup is already in progress to avoid
cleanup again. If mlm state is not eLIM_MLM_LINK_ESTABLISHED_STATE,
then it means cleanup is already in progress.
3. Return from __limProcessSmeDisassocCnf if cleanup is already in
progress.
4. Add check in limProcessMlmDeauthCnf to send deauth confirmation even
if state is eLIM_SME_WT_DISASSOC_STATE.
5. Add similar checks in limProcessMlmDisassocReqNtf to handle disassoc
from peer and supplicant simultaneously.
Change-Id: Ie19a7b79d835a5e5a77ef48f9379c1cf90dc38d7
CRs-Fixed: 878334
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Release 4.0.10.192
Change-Id: Iae14d7d392d3701f8472b05f0679d46efe4b0e8f
CRs-Fixed: 688141
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
while filling the tx_bundle_stats of HTC_TARGET, host is
corrupting next four bytes due to inappropriate boundary
check.
Change-Id: I603ed4621183c16df154309d31d3f5b6f2265d48
CRs-Fixed: 913050
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The MAC is not started upon FTM start.
Similarly stopping is not needed during FTM stop.
CRs-Fixed: 917306
Change-Id: I72ee4a58c88b54c1dad1b82f749274e0c2e8a9ce
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Handle STA State in hdd_RoamSetKeyCompleteHandler for WEP case.
In WEP case Key are set in following order.
1)Group key
2)Unicast Key
In WEP case STA was moved to AUTHENTICATED prior to
setting the unicast key and it was resulting in sending
few un-encrypted packet. Now STA state will be moved to
AUTHENTICATED after we set the unicast and group
key in WEP case.
Change-Id: I7471bc76b10be31c4a2dbb52286c7f808fa27306
CRs-Fixed: 906555
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Firmware is returning the timestamp offset from start of
extscan instead of start from wifi on for extscan cached results.
Thus, change the boot time since wifi on to maintain boot time
since extscan start.
CRs-Fixed: 917695
Change-Id: I9689f09463bfb2c1859acbabad866c09da7c50f1
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When allocate HTT descriptor, instead of allocating
large single chunk of memory, allocate small sized multiple
chunk of memory. Then not need to allocate order 5 memory.
Will have less chance to have out of memory problem.
Change-Id: Ib9d4a3f10adbc0656e1418cf3a67429322bb7164
CRs-fixed: 845666
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fix Compilation errors due to Runtime PM for SDIO and USB Drivers.
Change-Id: Id1d66eaac8fa5a7a3cfddb8a9517e8e42f222c4e
CRs-Fixed: 908372
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Release 4.0.10.191
Change-Id: I7e24fdfcc243128942b5c0f80251998acc54e196
CRs-Fixed: 688141
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Driver holds wakelocks to prevent system suspend intending
to access bus or expecting some activity with FW.
With Runtime PM enabled, holding wakelocks doesn't prevent
runtime suspend. Existing API's take the global usage count
for all Wakelocks.
On Race conditions, we see usage count going negative. This is
because we are doing get/put operations with global context.
Take usage count with a wakelock context and maintain usage count
per wakelock context.
All client needs to have their runtime pm context to use the
prevent/allow Runtime API's.
Change-Id: I1159f5725581ba86200a2881490363cbf2dbf7b4
CRs-Fixed: 908372
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
prima to qcacld-2.0 propagation
Decrement active session count before sending disconnect if the
session is in associated state.
Change-Id: I36ed13655d630ec09e84ee2d70b13749d9d954cb
CRs-Fixed: 907394
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
prima to qcacld-2.0 propagation
Currently while populating ext rate set, local rate array
has size as 8.But max 12 ext rates can be copied in this
local rate array.If it is greater than 8, then it leads
to crash.
To resolve this issue, increase the local rate array from
8 to 12.
Change-Id: I2097cc4feb7fa669a970de5463130bb4bbf6401c
CRs-Fixed: 903816
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
prima to qcacld-2.0 propagation
Currently if EnterBmps is failed, pmm state is changed to
ePMM_STATE_BMPS_WAKEUP.Now if disconnect happens, then enter
imps is not allowed if pmm state is ePMM_STATE_BMPS_WAKEUP.
To resolve this issue
1) Update the pmm state to READY if enterBmps is failed.
2) Update the pmm state to ePMM_STATE_BMPS_SLEEP if exitBmps
is failed.
3) Update the pmm state to READY if enterimps is failed.
Change-Id: Ie04d555a338ba232a497a3d1f93173b15f1499ed
CRs-Fixed: 905355
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add WMI_SERVICE_READY_EXT message def.
CRs-Fixed: 865207
Change-Id: I9b60836c3ed79cc7fdf4bb85da362f6dab2fdc8e
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Since PCIe link is always up, host can continue to proceed wlan_tasklet
when enter/exit D0WOW. This can avoid CE running out of buffers caused
by that FW keeps sending WMI events to host. This can also avoid the case
that host driver may drop back to back interrupts during D0WOW.
Change-Id: Ibbef8fa7278d217344d5f1bbf6ccb2ee9fe256dd
CRs-fixed: 755147
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If self-recovery flag is enabled in ini file, recover if host driver
timeouts for resume event or no credit from FW during D0WOW resume,
otherwise do VOS_BUG. Also do SOC reset at the beginning of recovery.
Change-Id: I3bc6fee968b1491b476dd9050c4f7e72996a048c
CRs-fixed: 916030
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When a radar is injected with primary at +/-30MHz from center freq
incorrect pulse duration is reported in the phyerrors and causes
reduction in the radar detection probability.
Fix the issue by modifying the pulse duration when pulses with
certain characteristics encounter host and thereby increase
the radar detection rate.
Change-Id: Id1f96ca42d16c511003aacc14dc7eaf1374bd5e9
CRs-Fixed: 916055
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As per the current implementation wmmAcTspecValid is reset during roaming
and set after establishing TSpec but currently wmmAcTspecValid is not
considered before classifying the data frames based on AC and UP.
Due to above issue after roaming we are still sending packets with UP
for which tspec session is not established.
Address the above issue by checking wmmAcTspecValid for AC before
classifying the frame.
Change-Id: I99174738f5b8cf0d3850e079045288efb3b4dcc7
CRs-Fixed: 915555
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Currently supplicant is not notified of new PMKSA candidate information
after receiving preauth response during OKC+PMF connection, hence we are
not populating PMKID in re-association request resulting in complete
EAP handshake after roaming to new AP.
Address the above issue by notifying supplicant about the new PMKSA
candidate.
Change-Id: I87b4e60694214598fe0cc9ddba9a87e6884451d5
CRs-Fixed: 914005
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Current implementation of initial 2g only scan is broken
in following ways:
1) Scan Id recycles so, keeping FIRST_SCAN_ID macro as 0x0001 will
make scan that comes after recyle of 0xFFFF behave as initial scan
2) function csrScan2GOnyRequest() is broken as it assigns a local
variable to channel list and when scan command is released later
it tries to free a non accessible memory and crashes.
This patch fixes both of these issues.
Change-Id: I93c99df2198c6e0b78e1c879e7b6f5e55bb8f122
CRs-Fixed: 829292
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is prima to qcacld-2.0 propagation.
In case DUT is connected to AP with RSN security and AP doesn't have
the RSN IE in beacon but it is present in probe responses,
On receiving the first beacon after connection, DUT detect that the
psession security doesnt match with that of beacon and issues a
disconnect.
To handle this, if security doesnt match with the beacon, send a
unicast probe request to AP and take decision based on the probe
response from AP.
Prima-Change-Id: I2b75caeb7a2b9972729c0aea46605e5c618d3e5a
Change-Id: Ia464905a5585480bde84d23be6085e4ef7721ebf
CRs-fixed: 777077
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is prima to qcacld-2.0 propagation.
Added a support to check the change in security in beacon and if security
is changed disconnect from AP. Following security changes are handled:
WPA <-> WEP/WAPI
RSN <-> WEP/WAPI
WPA/RSN <-> WEP/WAPI
Logic to handle security change from OPEN to other and vice versa
is arleady present.
This patch also fixes the wrong handling of WAPI security change for WAPI.
Prima-Change-ID: I756686c2d9a0caaec32ff646f3a4d892a5cf8101
Change-Id: Ie4bb517ff1ccfa97412425f98e3eb5ea5f7d5b1c
CRs-Fixed: 757941
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Discard invalid txrx_fw_stats in HOST driver
to have coherent Runtime PM uses count.
Wrong value requested in txrx_fw_stats result
in increment of Runtime PM uses count, which will
never be decremented in future.
Change-Id: I2170897cbe93fc66a5e44835c28680c7f9c0178b
CRs-Fixed: 912059
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
DEBUG_RX_RING_BUFFER flag is used to enable
rx ring buffer dump.DEBUG_RX_RING_BUFFER will
be defined for eng and user-debug build, not
for user build.
Change-Id: I25b13f7d488d11e09c6e4f5b4b0265b72051f47a
CRs-Fixed: 912317
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Release 4.0.10.190
Change-Id: Ifdb170d7cd0b0b7f091c39a67f4ca5f8140b9603
CRs-Fixed: 688141
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
After successfully handling first connection from the function
hdd_ipa_uc_handle_first_con, the log print is accessing an already
freed IPA message. Also moved the log print to failure case.
Change-Id: I21642e7743e3cd83cb7d3333ca2dc1baba7302c0
CRs-Fixed: 907000
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Currently tpAniSirGlobal pnoOffload value is initialized with
FW caps first time only and resetting to 0 while starting a bss in
go mode. Existing value of pnoOffload is not retained while
getting config for tSmeConfigParams.
Added changes to retain current value of pnoOffload from
tpAniSirGlobal while getting config for new tSmeConfigParams.
Change-Id: I0eda12ec1c69aeca4465d41f3e3ba96b8e1944cb
CRs-Fixed: 913994
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As per current implementation we avoid flushing lim scan
cache before scanning since lim scan cache might also contain
candidate AP's that we can roam. Due to this behaviour we end up
including BSS entry of AP which we disconnected due to
heartbeat failure.
Flush lim scan cache during disconnection with AP due to heartbeat
failure to avoid sending stale AP entries to the upper layer.
Change-Id: Icc7012168f354605435e20acf690cf59076d8788
CRs-Fixed: 913999
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
prima to qcacld-2.0 propagation
Kernel updates RSN IEs in BSS table only if it receives the Probe response.
Hence set fProbeRsp flag in BssDescriptor if PNO found indication is due to
probe response.
CRs-Fixed: 907635
Change-Id: I2bfee96c5a2abc6b0730c11e0c694ede81a69a21
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
If ap switches channel, sta will follow ap, as ap may change phymode
and channel width in new channel, so host needs set new phymode and
channel mode to fw.
Change-Id: I87b28119e0f4a8005f9c80f8f32912747b28306c
CRs-Fixed: 913325
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
prima to qcacld-2.0 propagation
If AP advertize the same rate in supported rates IE,
it will cross the max number of rates which is 12.
To fix it skipping the duplicate rates.
Change-Id: I5144ceba1b75cb7fdcfab0d8041e3e0020e900b0
CRs-Fixed: 889781
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Enable mobile router feature for mdmcalifornium.
Change-Id: If7761cba8559c4a08fb4f1223da47d07693c6e2d
CRs-fixed: 915964
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add a check to fix crash caused due to unregistered callback
while handling eWNI_SME_EXTSCAN_FULL_SCAN_RESULT_IND and
eWNI_SME_EPNO_NETWORK_FOUND_IND.
Change-Id: Ibd5e717d1e7f6ade3afdce9b7460eae5b0c9ca97
CRs-Fixed: 899468
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
prima to qcacld-2.0 propagation
Channel 144 is not present in WNI_CFG_SCAN_CONTROL_LIST and due
to this if STA is connected to AP on channel 144 the passive to
active conversion does not happens for channel 144 as it is not
present in WNI_CFG_SCAN_CONTROL_LIST.
Added channel 144 in WNI_CFG_SCAN_CONTROL_LIST.
Change-Id: I046ca6c3cf0a0b739c12a04d75c0b464b83cb492
CRs-fixed: 725102
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When a radar is injected with primary at +/-30MHz from center
frequency in JP domain incorrect pulse duration is reported
and causes reduction in radar detection probability.
Fix to modify the pulse duration when a pulse with certain
characteristics is reported on the host to increase the radar
detection probability
Change-Id: Ic3b6f8af392a720684d044c5c82956d269c76270
CRs-Fixed: 914388
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The string table for WMA messages is outdated. This patch updates
the string table for WMA messages to string converstion.
Change-Id: I3aef08b4c5ab8f9ab94d538dee1646eff829c55b
CRs-Fixed: 893502
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Release 4.0.10.189
Change-Id: Ib245f147713e02f515ec266acc4556646d3d040a
CRs-Fixed: 688141
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
During runtime suspend, if PCIe D3hot state is entered
prematurely then in cnss_auto_suspend, config space save takes
longer time because PCIe endpoint would be aggressive to go to
low power mode. cnss_auto_suspend and cnss_auto_resume takes care
of entering and exiting D3hot state along with pci_disable_device
and pci_enable_device respectively.
Change-Id: I5e6909ed5ff90349122285491047e89e50a33ca3
CRs-fixed: 915426
|