- 30 Mar, 2015 7 commits
-
-
Oleksij Rempel authored
Signed-off-by:
Oleksij Rempel <linux@rempel-privat.de> Signed-off-by:
Kalle Valo <kvalo@codeaurora.org>
-
Oleksij Rempel authored
Signed-off-by:
-
Oleksij Rempel authored
Signed-off-by:
-
Oleksij Rempel authored
This function uses mixed styles for register names/numbers which is make harder reading and optimisation. Signed-off-by:
-
Oleksij Rempel authored
Since usb bus add extra delay on each request, a command with read + write requests is too expensive. We can dramtically reduce usb load by moving this command to firmware. In my tests, this patch will reduce channel scan time for about 5-10 seconds. Signed-off-by:
-
Taehee Yoo authored
I changed REG_CR+2 and (MSR) to MSR because MSR is defined as (REG_CR + 2). Signed-off-by:
Taehee Yoo <ap420073@gmail.com> Acked-by:
Larry Finger <Larry.Finger@lwfinger.net> Signed-off-by:
-
Stanislaw Gruszka authored
Seems H/W report correctly firmware Autorun value only at initialization stage. When we close interface and open it again, Autorun value is 0 and we try to load firmware what kills the device. To fix clear REQUIRE_FIRMWARE firmware flag, to do not load firmware again, once we discover Autorun mode. Reported-and-tested-by:
Sebastian Andrzej Siewior <bigeasy@linutronix.de> Signed-off-by:
Stanislaw Gruszka <sgruszka@redhat.com> Signed-off-by:
-
- 21 Mar, 2015 1 commit
-
-
Sujith Manoharan authored
AIC needs to be registered only when BTCOEX is enabled. This fixes the error reported by kbuild: >> ERROR: "ar9003_hw_attach_aic_ops" [drivers/net/wireless/ath/ath9k/ath9k_hw.ko] undefined! Signed-off-by:
Sujith Manoharan <c_manoha@qca.qualcomm.com> Signed-off-by:
-
- 20 Mar, 2015 32 commits
-
-
Rafał Miłecki authored
Some BCM47XX SoC routers have LEDs connected to extra PCIe bcma buses. Handling them in arch code requires predictable GPIO numbers. Signed-off-by:
Rafał Miłecki <zajec5@gmail.com> Signed-off-by:
-
Avinash Patil authored
With patch '960d6d08 "mwifiex: delay skb allocation for RX until cmd53 over"' we no more pass skb parameter to MP aggregation setup helper function. We instead pass length to be aggregated. This patch fixes an issue where we were passing length parameter of NULL skb to aggregation routine resulting into crash. We should instead pass rx_len received from mp_regs. Signed-off-by:
Avinash Patil <patila@marvell.com> Signed-off-by:
Amitkumar Karwar <akarwar@marvell.com> Signed-off-by:
-
Arend van Spriel authored
There are no known BCM4354 PCIe devices released so removing support from the driver until proven otherwise. Reviewed-by:
Hante Meuleman <meuleman@broadcom.com> Reviewed-by:
Pieter-Paul Giesberts <pieterpg@broadcom.com> Signed-off-by:
Arend van Spriel <arend@broadcom.com> Signed-off-by:
-
Arend van Spriel authored
Recently support was added for the BCM4345 SDIO chipset by commit 9c510265 ("brcmfmac: Add support for BCM4345 SDIO chipset") however this was verified using a BCM43455 device, which is a more recent revision of the chip. This patch assure that older revisions are not probed as they would fail. Reviewed-by:
Syed Asifful Dayyan <syedd@broadcom.com> Reviewed-by:
-
Arend van Spriel authored
This patch added support for the BCM43430 802.11n SDIO chipset. Reviewed-by:
Daniel (Deognyoun) Kim <dekim@broadcom.com> Reviewed-by:
Franky (Zhenhui) Lin <frankyl@broadcom.com> Reviewed-by:
-
Arend van Spriel authored
The BCM4356 PCIe wireless device was added recently but overlooked the fact that the MODULE_FIRMWARE() macros were missing for the firmwares needed by this device. Reviewed-by:
-
Hante Meuleman authored
Reviewed-by:
-
Hante Meuleman authored
Reviewed-by:
-
Hante Meuleman authored
SDIO uses a thread to handle all communication with the device, for this data is exchanged between threads. This data needs proper memory barriers to make sure that data "exchange" is going correct. Reviewed-by:
-
Arend van Spriel authored
Several host controllers supporting runtime-pm are causing issues with our sdio wireless cards because they disable the sdio interrupt upon going into runtime suspend. This patch avoids that by doing a pm_runtime_forbid() call during the probe. Tested with Sony Vaio Duo 13 which uses sdhci-acpi host controller. Reviewed-by:
-
Dan Carpenter authored
It's clear from the indenting that curly braces were intended here. Fixes: e35000ea ('mwifiex: preprocess packets from TX queue') Signed-off-by:
Dan Carpenter <dan.carpenter@oracle.com> Signed-off-by:
-
Scott Branden authored
Add the USB Id to link the D-Link DWA 130 USB Wifi adapter to the rt2830 driver. Signed-off-by:
Scott Branden <sbranden@broadcom.com> Signed-off-by:
Pieter Truter <ptruter@broadcom.com> Signed-off-by:
-
Vladimir Kondratiev authored
Multicast is not yet properly supported for all connection types; actually, only non-secure AP is supported. For all other cases, fall back to old "pseudo-DMS" approach. Namely, for: - PBSS - secure connection When re-routing MCAST Rx->Tx on the AP, do not Tx back to the origin of the frame Signed-off-by:
Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com> Signed-off-by:
-
Vladimir Kondratiev authored
Use dedicated vring for multicast frames; this vring allocated for AP and PBSS (both P2P GO and client) configurations For short frames, use MCS0; for long - MCS1 Signed-off-by:
-
Vladimir Kondratiev authored
Sync with the wmi definitions from the firmware team Signed-off-by:
-
Vladimir Kondratiev authored
Fix checkpatch warning: WARNING: Prefer ether_addr_copy() over memcpy() if the Ethernet addresses are __aligned(2) Signed-off-by:
-
Vladimir Kondratiev authored
For the networking code and for hardware network accelerators, it is better to have IP header 4*n aligned. On the other side, DMA on Rx path require buffer to be aligned on 4*n as well. Having 14 bytes of Ethernet header, these 2 alignment requests are in contradiction. To solve this, order hardware offload block to not remove SNAP header. This adds extra 6 bytes between addresses and ethertype, making it 20 bytes total. This way, both buffer and IP header are 4*n aligned. Remaining is only to remove SNAP by shifting addresses 6 bytes. This involves data copying, so this feature should be disabled unless required by the platform. Module parameter "rx_align_2" (bool, default - false) introduced to control this feature. Feature is completely disabled when parameter is false. Signed-off-by:
-
Vladimir Kondratiev authored
"echo" used to be called when no firmware loaded to the NIC, this causes error output. Probe firmware with "echo" only after it returned "ready" event. Signed-off-by:
-
Vladimir Kondratiev authored
Use temporal variable for often used vring->swhead; and use proper index in debug printing - vring->swhead used before was modified in wil_vring_advance_head and then increased value was used in debug print Signed-off-by:
-
Lars-Peter Clausen authored
The cw1200 driver implements suspend and resume callbacks and assigns them to the suspend and resume fields of the device_driver struct. These callbacks are never actually called by anything though. Modify the driver to properly use dev_pm_ops so that the suspend function is actually executed upon suspend and drop the empty resume function. Signed-off-by:
Lars-Peter Clausen <lars@metafoo.de> Signed-off-by:
-
Jeff Layton authored
I've been getting this error when building mainline kernels using Fedora's config files: drivers/net/wireless/rtlwifi/rtl8188ee/hw.c: In function ‘_rtl88ee_init_mac’: drivers/net/wireless/rtlwifi/rtl8188ee/hw.c:853:2: error: implicit declaration of function ‘rtl_hal_pwrseqcmdparsing’ [-Werror=implicit-function-declaration] if (!rtl_hal_pwrseqcmdparsing(rtlpriv, PWR_CUT_ALL_MSK, ^ cc1: some warnings being treated as errors scripts/Makefile.build:258: recipe for target 'drivers/net/wireless/rtlwifi/rtl8188ee/hw.o' failed I'm not sure if this is the correct fix, but it does seem to allow the build to complete. I suspect that this was broken by commit 34ed780a (rtlwifi: Fix problems with building an allyesconfig). Most of the files that removed the include of pwrseqcmd.h, added one for ../pwrseqcmd.h. The rtl8188ee driver had it removed it but didn't add the include of the file in the parent directory. Signed-off-by:Jeff Layton <jeff.layton@primarydata.com> Acked-by:
-
Sujith Manoharan authored
When a MCI reset is done, make sure that AIC is started. Signed-off-by:
-
Sujith Manoharan authored
Add the main AIC calibration function to handle MCI_STATE_AIC_CAL. Signed-off-by:
-
Sujith Manoharan authored
This patch adds a function to handle the MCI message MCI_STATE_AIC_START. Signed-off-by:
-
Sujith Manoharan authored
Add a routine to handle the MCI_STATE_AIC_CAL_RESET message. Signed-off-by:
-
Sujith Manoharan authored
Since various MCI messages need to be handled, along with driver-level support in upper layers, disable AIC for now. Signed-off-by:
-
Sujith Manoharan authored
This patch adds support for post-processing the AIC calibration results. Signed-off-by:
-
Sujith Manoharan authored
Set the appropriate bits in the HW after AIC calibration is done. Signed-off-by:
-
Sujith Manoharan authored
This patch adds routines to handle the MCI message AIC_CAL_SINGLE, starting the required HW calibration. Signed-off-by:
-
Sujith Manoharan authored
Various registers to control and check AIC status. Signed-off-by:
-
Sujith Manoharan authored
AIC can be disabled or enabled on a per-card basis using MCI configuration, so register a function to check its status. Signed-off-by:
-
Sujith Manoharan authored
These are necessary for implementing AIC, supported by chips like WB222. Signed-off-by:
-
