Variable current_image can be modified by multiple threads.
This change will protect current_image getting modified
by multiple threads.
Change-Id: I33df463311b24f73b1ba124d388731a72bd13263
CRs-Fixed: 2016485
Signed-off-by: Swetha Chikkaboraiah <schikk@codeaurora.org>
This patch checks the buffer for NULL
pointer to prevent undefined access.
CRs-Fixed: 2032374
Change-Id: I1a1c4ca24e5c3d538ea93685de304dd186968308
Signed-off-by: Manoj Prabhu B <bmanoj@codeaurora.org>
Trigger preemption from the interrupt handler. This allows us
to aggressively change ringbuffers especially to lower priority
ones and finish working on pending commands.
Change-Id: Ic05213f3d02b1bb7400461edd0d19e38d5b01ec2
Signed-off-by: Sharat Masetty <smasetty@codeaurora.org>
The txpower is being recalculated when adding interface to make sure
txpower won't overshoot the spec, and when removing the interface,
the txpower should again to be recalculated to restore the correct value
from the active interface list.
Following is one of the scenario
vdev0 is created as STA and connected: txpower:23
vdev1 is created as P2P_DEVICE for control interface: txpower:0
vdev2 is created as p2p go/gc interface: txpower is 21
So the vdev2@txpower:21 will be set to firmware when vdev2 is created.
When we tear down the vdev2, the txpower needs to be recalculated to
re-set it to vdev0@txpower:23 as vdev0/vdev1 are the active interface.
ath10k_pci mac vdev 0 peer create 8c:fd:f0:01:62:98
ath10k_pci mac vdev_id 0 txpower 23
... (adding interface)
ath10k_pci mac vdev create 2 (add interface) type 1 subtype 3
ath10k_pci mac vdev_id 2 txpower 21
ath10k_pci mac txpower 21
... (removing interface)
ath10k_pci mac vdev 2 delete (remove interface)
ath10k_pci vdev 1 txpower 0
ath10k_pci vdev 0 txpower 23
ath10k_pci mac txpower 23
Signed-off-by: Ryan Hsu <ryanhsu@qca.qualcomm.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git
Git-commit: d679fa1b3c8997e3a371da3cca08c44a38054c34
CRs-Fixed: 2027293
Change-Id: I56befd4c4fd80ab77ed65926663a1f2471701f68
Signed-off-by: Rajeev Kumar Sirasanagandla <rsirasan@codeaurora.org>
Update QP Control value and sanitise QP values for
Initial QP properly.
Change-Id: I870a4f33a0dfbfd3a95970bb9cf319855fba746f
CRs-Fixed: 2027340
Signed-off-by: Deepak Kushwah <dkushwah@codeaurora.org>
Ath10k reports the phy capability that supports P2P_DEVICE interface.
When we use the P2P supported wpa_supplicant to start connection, it'll
create two interfaces, one is wlan0 (vdev_id=0) and one is P2P_DEVICE
p2p-dev-wlan0 which is for p2p control channel (vdev_id=1).
ath10k_pci mac vdev create 0 (add interface) type 2 subtype 0
ath10k_add_interface: vdev_id: 0, txpower: 0, bss_power: 0
...
ath10k_pci mac vdev create 1 (add interface) type 2 subtype 1
ath10k_add_interface: vdev_id: 1, txpower: 0, bss_power: 0
And the txpower in per vif bss_conf will only be set to valid tx power when
the interface is assigned with channel_ctx.
But this P2P_DEVICE interface will never be used for any connection, so
that the uninitialized bss_conf.txpower=0 is assinged to the
arvif->txpower when interface created.
Since the txpower configuration is firmware per physical interface.
So the smallest txpower of all vifs will be the one limit the tx power
of the physical device, that causing the low txpower issue on other
active interfaces.
wlan0: Limiting TX power to 21 (24 - 3) dBm
ath10k_pci mac vdev_id 0 txpower 21
ath10k_mac_txpower_recalc: vdev_id: 1, txpower: 0
ath10k_mac_txpower_recalc: vdev_id: 0, txpower: 21
ath10k_pci mac txpower 0
This issue only happens when we use the wpa_supplicant that supports
P2P or if we use the iw tool to create the control P2P_DEVICE interface.
Signed-off-by: Ryan Hsu <ryanhsu@qca.qualcomm.com>
Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git
Git-commit: 88407beb1b1462f706a1950a355fd086e1c450b6
CRs-Fixed: 2027293
Change-Id: Ib56352e1601e7400b856cfafe67503bee98d5ced
Signed-off-by: Rajeev Kumar Sirasanagandla <rsirasan@codeaurora.org>
Add the RRADC die_temp channel details to the FG node for
the FG standby oscillator frequency drift WA.
Change-Id: I78d385afc82f9d8b7b6cdc64de59dfe964d2b50b
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>
It is observed that on certain foundry devices, frequency of the
standby oscillator drifts with die temperature. Compensate
for this by correcting the FG time-base based on die temperature.
Change-Id: I0de19b9c342bf50568502b4de96897e159a8e143
Signed-off-by: Anirudh Ghayal <aghayal@codeaurora.org>
Add the missing callback functions on 32bit systems that can be used to
set the dma_mask and get the dma error information.
Change-Id: I69c454ea8cbceb4301ec812c5f74f6a751fc7df1
Signed-off-by: Charan Teja Reddy <charante@codeaurora.org>
Add the I/O coherency support for devices that can issue a cache
coherent transactions.
Change-Id: I01b1dca4d72395df41ac5b882dcd3fd75a682b8c
Signed-off-by: Charan Teja Reddy <charante@codeaurora.org>
This adds defines and nl80211 extensions to allow FILS Authentication to
be implemented similarly to SAE. FILS does not need the special rules
for the Authentication transaction number and Status code fields, but it
does need to add non-IE fields. The previously used
NL80211_ATTR_SAE_DATA can be reused for this to avoid having to
duplicate that implementation. Rename that attribute to more generic
NL80211_ATTR_AUTH_DATA (with backwards compatibility define for
NL80211_SAE_DATA).
Also document the special rules related to the Authentication
transaction number and Status code fiels.
Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Git-commit: 11b6b5a4ced2f2c76073b97ee08ca0eab8358fde
Git-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
CRs-Fixed: 2028536
Change-Id: Icc8bbdf3530c46048239ca88bfcb8b100a7f0822
Signed-off-by: Vidyullatha Kanchanapally <vidyullatha@codeaurora.org>
Smem item is searched in cached region only, however it depends on remote
processor if smem exist in cache region or non cache region of smem memory.
Check for smem item in both cached and non cached region.
CRs-Fixed: 2031705
Change-Id: Ib11fd15c6c49353950c0892b45d0eec1fbc33f46
Signed-off-by: Dhoat Harpal <hdhoat@codeaurora.org>
