- 15 Apr, 2016 10 commits
-
-
Jes Sorensen authored
Longer term we should switch all the chips over to use this function instead of the random chip specific ifdef hacks. Signed-off-by:
Jes Sorensen <Jes.Sorensen@redhat.com> Signed-off-by:
Kalle Valo <kvalo@codeaurora.org>
-
Jes Sorensen authored
This further reorganizes the init code flow to match that of the 8192eu vendor driver. This helps diffing the register write log against that of the vendor driver. Signed-off-by:
-
Jes Sorensen authored
In order to debug 8192eu support, reorder some init code to match the flow of the vendor driver. Signed-off-by:
-
Andreas Fenkart authored
after factoring out mwifiex_cancel_pending_scan_cmd the function is not called outside of cmdevt file moved function to head of file to avoid forward declaration, also moved mwifiex_recycle_cmd_node since they are very similar Signed-off-by:
Andreas Fenkart <afenkart@gmail.com> Signed-off-by:
-
Andreas Fenkart authored
Releasing the scan_pending lock in mwifiex_check_next_scan_command introduces a short window where pending scan commands can be removed or added before removing them all in mwifiex_cancel_pending_scan_cmd. I think this is safe, since the worst thing to happen is that a pending scan cmd is removed by the command handler. Adding new scan commands is not possible while one is pending, see scan_processing flag. Since all commands are removed from the queue anyway, we don't care if some commands are removed by a different code path earlier, the final state remains the same. I assume, that the critical section needed for the check has been extended over clearing the pending scan queue out of convenience. The lock was already held and releasing it and grab it again was just more work. It doesn't seem to be necessary because of concurrency. Signed-off-by:
-
Andreas Fenkart authored
improves readability Reviewed-by:
Julian Calaby <julian.calaby@gmail.com> Signed-off-by:
-
Andreas Fenkart authored
merge copy/paste code Signed-off-by:
-
Andreas Fenkart authored
"x ? x : y" can be simplified as "x ? : y" https://gcc.gnu.org/onlinedocs/gcc/Conditionals.html#ConditionalsReviewed-by:
-
Andreas Fenkart authored
Signed-off-by:
-
Andreas Fenkart authored
given this structure: struct foo { struct bar { int baz; } } these accesses are equivalent: (*(foo->bar)).baz foo->bar->baz Signed-off-by:
-
- 14 Apr, 2016 30 commits
-
-
Vishal Thanki authored
During system suspend, there is a kernel WARNING issued if there is a pending command present. By marking the wait queue disabled after calling the command completion routine fixes it. Signed-off-by:
Vishal Thanki <vishalthanki@gmail.com> Signed-off-by:
-
Amitkumar Karwar authored
IEEE80211_CHAN_NO_HT40PLUS and IEEE80211_CHAN_NO_HT40PLUS channel flags tell if HT40 operation is allowed on a channel or not. This patch ensures ht_capability information is modified accordingly so that we don't end up creating a HT40 connection when it's not allowed for current regulatory domain. Signed-off-by:
Amitkumar Karwar <akarwar@marvell.com> Signed-off-by:
Cathy Luo <cluo@marvell.com> Signed-off-by:
-
Xinming Hu authored
Host hang is observed if card is removed before firmware download gets completed. In this case, firmware will be failed to download and adapter structure gets freed. In other thread, mwifiex_remove_card() waits on semaphore until the firmware download fails. This wait is not necessary and may result in invalid adapter access. This patch uses down_trylock to return immediately so that hang issue won't occur. Signed-off-by:
Xinming Hu <huxm@marvell.com> Signed-off-by:
-
Shengzhen Li authored
This patch adds default setting for pcie firmware download name in case that there are newer chipset version. Signed-off-by:
Shengzhen Li <szli@marvell.com> Signed-off-by:
-
Shengzhen Li authored
This patch adds support for downloading usb/uart firmware for 8997 chipset by reading the chip version. Signed-off-by:
-
Amitkumar Karwar authored
This patch adds missing break statement at the end of PCIE_DEVICE_ID_MARVELL_88W8897 switch section. Signed-off-by:
-
Arend van Spriel authored
In receive path brcmf_proto_hdrpull() needs to be called and handled similar in brcmf_rx_frame() and brcmf_rx_event(). Move that duplicated code in separate function. Reviewed-by:
Hante Meuleman <hante.meuleman@broadcom.com> Reviewed-by:
Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com> Reviewed-by:
Franky Lin <franky.lin@broadcom.com> Signed-off-by:
Arend van Spriel <arend@broadcom.com> Signed-off-by:
-
Arend van Spriel authored
Move event handling out of brcmf_netif_rx() avoiding the need to pass a flag. This flag is only ever true for USB hosts as other interface use separate brcmf_rx_event() function. Reviewed-by:
-
Arend van Spriel authored
The code for ampdu-rx host reorder is related to the firmware signalling supported in BCDC protocol. This change moves the code to fwsignal module. Reviewed-by:
-
Franky Lin authored
Firmware uses asynchronized events as a communication method to the host. The event packets are marked as ETH_P_LINK_CTL protocol type. For SDIO and PCIe bus, this kind of packets are delivered through virtual event channel not data channel. This patch adds a screening logic to make sure the event handler only processes the events coming from the correct channel. Reviewed-by:
-
Hante Meuleman authored
When p2p connection setup is performed without having ever done an escan a null pointer exception can occur. This is because the ifp to abort scanning is taken from escan struct while it was never initialized. Fix this by using the primary ifp for scan abort. The abort should still be performed and all scan related commands are performed on primary ifp. Reviewed-by:
-
Hante Meuleman authored
Some nvram files/stores come without the boardrev information, but firmware requires this to be set. When not found in nvram then add a default boardrev string to the nvram data. Reported-by:
Rafal Milecki <zajec5@gmail.com> Reviewed-by:
-
Hante Meuleman authored
Newer firmwares require the usage of the wowl wakeind struct as size for the iovar to clear the wake indicators. Older firmwares do not care, so change the used size. Reviewed-by:
-
Hante Meuleman authored
When the event_msgs iovar is set an array is used to configure the enabled events. This arrays needs to nulled before configuring otherwise unhandled events will be enabled. This solves a problem where in case of wowl the host got woken by an incorrectly enabled event. Reviewed-by:
-
Jes Sorensen authored
Adjust AFE before enabling PLL on 8192eu, probably also needed for 8723bu. Signed-off-by:
-
Jes Sorensen authored
8192eu has it's own IQK calibration procedure, and notably uses undocumented RF register 0x56 in the process. Signed-off-by:
-
Jes Sorensen authored
Fixup another case where the hard coded register value was used instead of the name. Signed-off-by:
-
Jes Sorensen authored
Set REG_QUEUE_CTRL and REG_ACLK_MON for 8192eu. Signed-off-by:
-
Jes Sorensen authored
Implement workaround for LDPC RX hands on 8192eu. This was inspired by workaround found in the 8192eu vendor driver. Signed-off-by:
-
Jes Sorensen authored
The vendor driver set register 0xfe58 REG_USB_HWPWM in it's init sequence for 8192eu. Do the same here. Signed-off-by:
-
Jes Sorensen authored
Set HIMR[01] on 8192eu instead of HISR/HIMR. It's not obvious this really matters for USB devices, but this matches the register writes performed by the vendor driver. Signed-off-by:
-
Jes Sorensen authored
Set REG_AFE_XTAL_CTRL on 8192eu to the vendor driver value, and do not skip setting REG_MAX_AGGR_NUM on 8192eu. Signed-off-by:
-
Jes Sorensen authored
The 8192eu requires clearing/restoring bit 17 in REG_FPGA0_POWER_SAVE before/after writing RF registers. Signed-off-by:
-
Jes Sorensen authored
The 8192eu does not use REG_AFE_PLL_CTRL in it's BB init sequence, so provide device specific handling. Signed-off-by:
-
Jes Sorensen authored
The 8192eu efuse only has power data for path A and B. It follows the same layout as 8723bu. Signed-off-by:
-
Jes Sorensen authored
Pick PHY init table based on device before distinguishing between 1T/2T/high PA tables. The latter is only currently used for 8188cu/8192cu/8188ru. Signed-off-by:
-
Jes Sorensen authored
The 8192eu also requires it's own PHY init table. Signed-off-by:
-
Jes Sorensen authored
A device specific AGC table is required for the 8192eu as well. Signed-off-by:
-
Jes Sorensen authored
Add the required radio init tables for 8192eu devices. Signed-off-by:
-
Jes Sorensen authored
The 8192eu also has it's own TRXFF boundary value to set. Signed-off-by:
-
