Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

On Wed, Jun 29, 2016 at 04:04:31PM +0200, Hans de Goede wrote: > Add a brcm,nvram_file_name dt property to allow overruling the default > nvram filename for sdio devices. The idea is that we can specify a > board specific nvram file, e.g. brcmfmac43362-ap6210.txt for boards > with an ap6210 wifi

[PATCH v2] cfg80211: Add mesh peer AID setting API

Previously, mesh power management functionality works only with kernel MPM. Because user space MPM did not report mesh peer AID to kernel, the kernel could not identify the bit in TIM element. So this patch adds mesh peer AID setting API. Signed-off-by: Masashi Honma ---

[no subject]

-- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

[PATCH] mwifiex: mask PCIe interrupts before removal

The PCIe driver didn't mask the host interrupts before trying to tear down. This causes lockups at reboot or rmmod when using MSI-X on 8997, since the MSI handler gets confused and locks up the system. Also tested on 8897, which does not support MSI-X (and wasn't experiencing this same bug). No

building brcmfmac driver for iMX6 Ultralite platform

I am trying to bring up the brcmfmac driver on an iMX6 Ultralite board. I have both a 43341 and 43362 Wi-Fi SDIO module up and running on this platform already using the standard bcmdhd. I am told by some Broadcom folks that the brcmfmac driver should support concurrent connections which is

Re: [PATCH v3] ath10k: Fix 10.4 extended peer stats update

On Thu, Jun 30, 2016 at 11:09:31AM +, Valo, Kalle wrote: > Mohammed Shafi Shajakhan writes: > > > Hi Kalle, > > > > On Thu, Jun 30, 2016 at 10:49:02AM +, Valo, Kalle wrote: > >> Kalle Valo writes: > >> > >> >> @@ -261,6 +263,7 @@ static

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

On 30-6-2016 13:31, Arnd Bergmann wrote: > On Thursday, June 30, 2016 12:25:15 PM CEST Hans de Goede wrote: >>> So then how about making use of a more specific compatible string? >>> >>> e.g. >>> >>> brcmf { >>> compatible = "foo,ap6210", "brcm,bcm4329-fmac"; >>> ... >>> }; >>>

Re: [PATCH 1/2] mwifiex: add hostcmd wext ioctl support

Hi, [auto build test ERROR on wireless-drivers-next/master] [also build test ERROR on v4.7-rc5 next-20160630] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Amitkumar-Karwar/mwifiex-add-hostcmd

Re: [PATCH 1/2] mwifiex: add hostcmd wext ioctl support

Hi, [auto build test ERROR on wireless-drivers-next/master] [also build test ERROR on v4.7-rc5 next-20160630] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Amitkumar-Karwar/mwifiex-add-hostcmd

[PATCH] wcn36xx: Implement print_reg indication

Some firmware versions sends a "print register indication", handle this by printing out the content. Cc: Nicolas Dechesne Signed-off-by: Bjorn Andersson --- drivers/net/wireless/ath/wcn36xx/hal.h | 16

Re: [PATCH v3] wlcore: Add support for get_expected_throughput opcode

Hi, [auto build test ERROR on wireless-drivers-next/master] [also build test ERROR on v4.7-rc5 next-20160630] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Maxim-Altshul/wlcore-Add-support

[PATCH] mwifiex: Change default firmware for PCIe8997 chipset

PCIe-USB8997 variant is being used in the product. Let's change default firmware from PCIe-UART to PCIe-USB. So by default PCIe-USB firmware would be downloaded if version register doesn't give any information. Signed-off-by: Amitkumar Karwar ---

[RFC] nl80211: Allow GET_INTERFACE dumps to be filtered

This patch allows GET_INTERFACE dumps to be filtered based on NL80211_ATTR_WIPHY or NL80211_ATTR_WDEV. The documentation for GET_INTERFACE mentions that this is possible: "Request an interface's configuration; either a dump request on a %NL80211_ATTR_WIPHY or ..." However, this behavior has not

[PATCH v3] wlcore: Add support for get_expected_throughput opcode

Adding this opcode, allows the TI wireless driver, to report throughput directly from FW to mac80211. This is used mainly for mesh metric calculation. Signed-off-by: Maxim Altshul --- Removed ret and NULL test. drivers/net/wireless/ti/wlcore/main.c | 11 +++ 1

[PATCH 0/2] mwifiex: manufacturing mode

This patch series adds support for loading the driver in manufacturing mode. It's needed to perform certain factory tests. Amitkumar Karwar (1): mwifiex: add manufacturing mode support Xinming Hu (1): mwifiex: add hostcmd wext ioctl support drivers/net/wireless/marvell/mwifiex/cmdevt.c |

[PATCH v2] mac80211: mesh: Add support for HW RC implementation

Mesh HWMP module will be able to rely on the HW RC algorithm if it exists, for path metric calculations. This allows the metric calculation mechanism to calculate a correct metric, based on PER and last TX rate both via HW RC algorithm if it exists or via parameters collected by the SW.

ath9k: EEPROM format / byte swapping

Hello, I have a question regarding the ath9k EEPROM format. Most EEPROM versions have two magic bytes at the beginning, indicating the endianness of the data in this EEPROM. Let's take the AR9287 EEPROM as an example: during ath9k initialization ath9k/eeprom_9287.c:ath9k_hw_ar9287_check_eeprom

Re: [PATCH v2] wlcore: Add support for get_expected_throughput opcode

On Thu, 2016-06-30 at 17:49 +0300, Maxim Altshul wrote: > Adding this opcode, allows the TI wireless driver, > to report throughput directly from FW to mac80211. > > This is used mainly for mesh metric calculation. > > Signed-off-by: Maxim Altshul > --- > Changed the units

[PATCH 1/2] mwifiex: add hostcmd wext ioctl support

From: Xinming Hu This patch adds ndo_ioctl support to mwifiex netdev handlers. This will be used to download hostcmds to firmware from userspace. This is needed for manufacturing mode support in mwifiex. ndo_ioctl is allowed only when mfg mode is enabled via module load

[PATCH 2/2] mwifiex: add manufacturing mode support

By default normal mode is chosen when driver is loaded. This patch adds a provision to choose manufacturing mode via module parameters. Command to load driver in manufacturing mode insmod mwifiex.ko mfg_mode=1 and mfg_firmware=mrvl/firmware. Tested-by: chunfan chen

Re: [PATCHV2 1/3] ath10k: move firmware_swap_code_seg_info to ath10k_fw_file

writes: > From: Tamizh chelvam > > Preparation to make use of firmware_swap_code_seg_info for > UTF binary. > > Signed-off-by: Tamizh chelvam This patchset crashes my x86 laptop once I start hostapd. Unfortunately I

Re: [PATCH] cfg80211: Add mesh peer AID setting API

On 2016年06月30日 20:11, Bob Copeland wrote: Let's call it peer_aid or mesh_peer_aid or something like that, per my email on hostapd list. Also you probably saw kbuild robot pointed out missing documentation for the field. Yes. I will modify this also. We need a check against IEEE80211_MAX_AID

Re: [PATCHV2 3/3] ath10k: add testmode support for 10.4 firmware

writes: > From: Tamizh chelvam > > This patch adds testmode support for QCA99X0 chipsets which uses > 10.4 firmware and added code swap support for UTF binary. > > Signed-off-by: Tamizh chelvam There were few

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

On Thursday, June 30, 2016 12:25:15 PM CEST Hans de Goede wrote: > > So then how about making use of a more specific compatible string? > > > > e.g. > > > > brcmf { > > compatible = "foo,ap6210", "brcm,bcm4329-fmac"; > > ... > > }; > > > > and if the compatible has more than one

Re: [PATCH 1/2] ath10k: remove unused

Sergei Shtylyov writes: > On 6/21/2016 2:45 PM, Chaehyun Lim wrote: > >> is not used anymore, so just remove it. > >s/it/#include/? Fixed that in the pending branch. -- Kalle Valo-- To unsubscribe from this list: send the line "unsubscribe

Re: ath9k: Fix programming of minCCA power threshold

Sven Eckelmann wrote: > The function ar9003_hw_apply_minccapwr_thresh takes as second parameter not > a pointer to the channel but a boolean value describing whether the channel > is 2.4GHz or not. This broke (according to the origin commit) the ETSI > regulatory compliance on

Re: ath9k: return false when reading wrong eeprom offset

Eduardo Abinader wrote: > Just setting the proper return for reading beyond the eeprom data. > > Signed-off-by: Eduardo Abinader > Reviewed-by: Julian Calaby Thanks, 1 patch applied to ath-next branch of

Re: [PATCH] cfg80211: Add mesh peer AID setting API

On Thu, Jun 30, 2016 at 06:00:58PM +0900, Masashi Honma wrote: > diff --git a/include/net/cfg80211.h b/include/net/cfg80211.h > index 7bbb00d..2fa5896 100644 > --- a/include/net/cfg80211.h > +++ b/include/net/cfg80211.h > @@ -805,6 +805,7 @@ struct station_parameters { > u32 sta_modify_mask;

Re: [PATCH v3] ath10k: Fix 10.4 extended peer stats update

Mohammed Shafi Shajakhan writes: > Hi Kalle, > > On Thu, Jun 30, 2016 at 10:49:02AM +, Valo, Kalle wrote: >> Kalle Valo writes: >> >> >> @@ -261,6 +263,7 @@ static const struct ath10k_hw_params >> >> ath10k_hw_params_list[] = { >> >>

Re: [v2] ath10k: Fix some typo in spectral code commments

Mohammed Shafi Shajakhan wrote: > From: Mohammed Shafi Shajakhan > > Found this obvious typo while going through the spectral > code design in ath10k > > Signed-off-by: Mohammed Shafi Shajakhan Thanks, 1 patch

Re: ath10k: Disable TX_STBC for tx chainmask of 1

Mohammed Shafi Shajakhan wrote: > From: Mohammed Shafi Shajakhan > > Disable TX_STBC for both HT and VHT if the devices tx chainmask is '1' > TX_STBC is required only for devices with tx_chainmask > 1. This fixes > a ping failure for QCA9887

Re: [PATCH v3] ath10k: Fix 10.4 extended peer stats update

Hi Kalle, On Thu, Jun 30, 2016 at 10:49:02AM +, Valo, Kalle wrote: > Kalle Valo writes: > > >> @@ -261,6 +263,7 @@ static const struct ath10k_hw_params > >> ath10k_hw_params_list[] = { > >>.board = QCA4019_HW_1_0_BOARD_DATA_FILE, > >>

Re: ath10k: Enable beacon loss detection support for 10.4

Mohammed Shafi Shajakhan wrote: > From: Mohammed Shafi Shajakhan > > Enable beacon loss detection support for 10.4 by handling > roam event. With this change QCA99X0 station is able to > detect beacon loss when the AP is powered off > >

Re: [v2] ath10k: Fix crash during card removal

Mohammed Shafi Shajakhan wrote: > From: Mohammed Shafi Shajakhan > > Usually when the firmware crashes we check for the value > 'FW_IND_EVENT_PENDING' in 'FW_INDICATOR_ADDRESS' and proceed with > disabling the irq and dumping firmware 'crash

Re: ath10k: fix potential null dereference bugs

Bob Copeland wrote: > Smatch warns about a number of cases in ath10k where a pointer is > null-checked after it has already been dereferenced, in code involving > ath10k private virtual interface pointers. > > Fix these by making the dereference happen later. > > Addresses

Re: ath10k: Remove unneccessary WARN_ON_ONCE in rx during ACS

Mohammed Shafi Shajakhan wrote: > From: Mohammed Shafi Shajakhan > > The below warning message seems to hit occasionally with the following > combination (IPQ4019 + ACS scan) where we receive packets as a self peer > when hostapd does ACS

Re: [PATCH v3] ath10k: Fix 10.4 extended peer stats update

Kalle Valo writes: >> @@ -261,6 +263,7 @@ static const struct ath10k_hw_params >> ath10k_hw_params_list[] = { >> .board = QCA4019_HW_1_0_BOARD_DATA_FILE, >> .board_size = QCA4019_BOARD_DATA_SZ, >>

Re: [PATCH v3] ath10k: Fix 10.4 extended peer stats update

Mohammed Shafi Shajakhan writes: > From: Mohammed Shafi Shajakhan > > 10.4 'extended peer stats' will be not be appended with normal peer stats > data and they shall be coming in separate chunks. Fix this by maintaining > a separate linked

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Hi, On 30 June 2016 at 12:04, Hans de Goede wrote: > Hi, > > > On 30-06-16 11:58, Kalle Valo wrote: >> >> Hans de Goede writes: >> >>> Hi, >>> >>> On 30-06-16 11:02, Kalle Valo wrote: Priit Laes writes: >> What is

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Hi, On 30-06-16 12:18, Jonas Gorski wrote: Hi, On 30 June 2016 at 12:04, Hans de Goede wrote: Hi, On 30-06-16 11:58, Kalle Valo wrote: Hans de Goede writes: Hi, On 30-06-16 11:02, Kalle Valo wrote: Priit Laes writes:

Re: [PATCH 2/2] ath10k: Fix sending NULL/ Qos NULL data frames for QCA99X0 and later

Ben Greear writes: > Is there a better way than posting to the ath10k mailing list? There are > quite > a few more of my patches that are stuck in pending or ignored state. If you > could review some of them and add them to your testing trees then it might > help >

Re: [PATCH] mac80211: fix fq lockdep warnings

On Wed, 2016-06-29 at 14:00 +0200, Michal Kazior wrote: > Some lockdep assertions were not fulfilled and > resulted in a kernel warning/call trace if driver > used intermediate software queues (e.g. ath10k). > > Existing code sequences should've guranteed safety > but it's always good to be extra

Re: [PATCH] mac80211: use common cleanup for user/!user_mpm

On Sat, 2016-06-25 at 19:14 -0400, Bob Copeland wrote: > We've accumulated a couple of different fixes now to > mesh_sta_cleanup() > due to the different paths that user_mpm and !user_mpm cases take -- > one > fix to flush nexthop paths and one to fix the counting. > > The only caller of

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Hans de Goede writes: > Hi, > > On 30-06-16 11:02, Kalle Valo wrote: >> Priit Laes writes: >> What is the size of this nvram file? As it's board specific, I wonder if we can simply include it inside of the DT verbatim. I remember doing that

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Hi, On 30-06-16 11:58, Kalle Valo wrote: Hans de Goede writes: Hi, On 30-06-16 11:02, Kalle Valo wrote: Priit Laes writes: What is the size of this nvram file? As it's board specific, I wonder if we can simply include it inside of the DT verbatim. I

Re: [PATCH] cfg80211: Add mesh peer AID setting API

-Add-mesh-peer-AID-setting-API/20160630-171005 base: https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git master reproduce: make htmldocs All warnings (new ones prefixed by >>): >> include/net/cfg80211.h:827: warning: No description found for parameter

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Hi, On 29-06-16 20:51, 'Arend Van Spriel' via linux-sunxi wrote: On 29-6-2016 20:01, Hans de Goede wrote: Hi, On 29-06-16 19:00, Kalle Valo wrote: Hans de Goede writes: Hi, On 29-06-16 16:42, Jonas Gorski wrote: Hi, On 29 June 2016 at 16:04, Hans de Goede

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Hi, On 30-06-16 11:02, Kalle Valo wrote: Priit Laes writes: What is the size of this nvram file? As it's board specific, I wonder if we can simply include it inside of the DT verbatim. I remember doing that (in the pre-dtb days, on real open firmware) for the "spidernet"

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Hi, On 30-06-16 10:46, Kalle Valo wrote: Arend Van Spriel writes: Since we are dealing with a per-board config-file here, which is loaded from the os filesystem we really need to specify a basename here as the list of possible boards is endless, so we cannot

Re: [PATCH] mwifiex: Fixed endianness for event TLV type TLV_BTCOEX_WL_SCANTIME

On Thu, Jun 30, 2016 at 1:05 PM, Amitkumar Karwar wrote: > Hi Prasun, > >> From: Prasun Maiti [mailto:prasunmait...@gmail.com] >> Sent: Friday, June 24, 2016 12:27 PM >> To: Amitkumar Karwar; Nishant Sarmukadam; Kalle Valo >> Cc: Linux Wireless; Linux Next; Linux Kernel >>

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Priit Laes writes: >> What is the size of this nvram file? As it's board specific, I wonder >> if we can simply include it inside of the DT verbatim. I remember >> doing that (in the pre-dtb days, on real open firmware) for the >> "spidernet" >> ethernet driver. > > It contains

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Arend Van Spriel writes: >>> Typical wifi devices will have some sort of non volatile storage >>> on board to not only store the ethernet(mac) address, but also >>> to contain e.g. info about the antenna gain so that the firmware >>> and/or the driver can take the

[PATCH] cfg80211: Add mesh peer AID setting API

Previously, mesh peer AID is not reported to kernel when local mesh STA is created without iw command. The mesh peer AID is needed by mesh peer power management functionality to identify a AID in a TIM element. This patch creates mesh peer AID setting API. Signed-off-by: Masashi Honma

RE: [PATCH v2] mwifiex: Fix endianness for event TLV type TLV_BTCOEX_WL_SCANTIME

Hi Prasun, > -Original Message- > From: Prasun Maiti [mailto:prasunmait...@gmail.com] > Sent: Thursday, June 30, 2016 2:01 PM > To: Amitkumar Karwar > Cc: Nishant Sarmukadam; Linux Wireless; Linux Next; Linux Kernel; Kalle > Valo > Subject: [PATCH v2] mwifiex: Fix endianness for event TLV

Re: [linux-sunxi] Re: [PATCH 1/4] brcmfmac: Add brcm,nvram_file_name dt property

Arend Van Spriel writes: >> Since we are dealing with a per-board config-file here, which is >> loaded from the os filesystem we really need to specify a basename >> here as the list of possible boards is endless, so we cannot >> have a lookup table in the driver. >

Re: [PATCH v2] mwifiex: Fix endianness for event TLV type TLV_BTCOEX_WL_SCANTIME

On Thu, Jun 30, 2016 at 2:07 PM, Amitkumar Karwar wrote: > Hi Prasun, > Updated change looks fine to me. > > Acked-by: Amitkumar Karwar > > Regards, > Amitkumar Hi AmitKumar, Thanks for your verification. -- Thanks, Prasun -- To unsubscribe from this

[PATCH v2] mwifiex: Fix endianness for event TLV type TLV_BTCOEX_WL_SCANTIME

The two members min_scan_time and max_scan_time of structure "mwifiex_ie_types_btcoex_scan_time" are of two bytes each. The values are assigned directtly from firmware without endian conversion handling. So, wrong datas will get saved in big-endian systems. This patch converts the values into

RE: [PATCH] mwifiex: Fixed endianness for event TLV type TLV_BTCOEX_WL_SCANTIME

Hi Prasun, > From: Prasun Maiti [mailto:prasunmait...@gmail.com] > Sent: Friday, June 24, 2016 12:27 PM > To: Amitkumar Karwar; Nishant Sarmukadam; Kalle Valo > Cc: Linux Wireless; Linux Next; Linux Kernel > Subject: Re: [PATCH] mwifiex: Fixed endianness for event TLV type >