Re: fixed bit rate 9Mbps set as 24Mbps in g mode(legacy)

On Tue, 27 Feb 2018 08:41:50 -0800, Ben Greear wrote > On 02/27/2018 12:49 AM, KAVITA MATHUR wrote: > > Hi, > > > > I have configured AP in g mode and tested legacy rates.All basic rates and > > supported > > rates(1,2,5.5,11,6,9,12,18,24,36,48,54) are set except 9Mbps. > > > > When fixed bit

Re: [PATCH v12] ath10k: add LED and GPIO controlling support for various chipsets

Am 27.02.2018 um 23:08 schrieb Rafał Miłecki: On 26 February 2018 at 09:44, wrote: From: Sebastian Gottschall Adds LED and GPIO Control support for 988x, 9887, 9888, 99x0, 9984 based chipsets with on chipset connected led's using WMI

[RFC] ath10k: Attempt to work around napi_synchronize hang.

From: Ben Greear Calling napi_disable twice in a row (w/out starting it and/or without having NAPI active leads to deadlock because napi_disable sets NAPI_STATE_SCHED and NAPI_STATE_NPSVC when it returns, as far as I can tell. So, guard this call to napi_disable. I

RFC: Possible napi deadlock work-around?

Does this look like a good idea? [greearb@ben-dt3 ath10k]$ git diff diff --git a/drivers/net/wireless/ath/ath10k/core.h b/drivers/net/wireless/ath/ath10k/core.h index 72b4495..c7ba49f 100644 --- a/drivers/net/wireless/ath/ath10k/core.h +++ b/drivers/net/wireless/ath/ath10k/core.h @@ -1205,6

Re: Deadlock debugging help.

On 02/27/2018 01:42 PM, Ben Greear wrote: On 02/27/2018 12:49 PM, Ben Greear wrote: I notice I can reliably lock up the kernel if I rmmod ath10k while it is under heavy tx/rx traffic. First, this causes the firmware to crash, and then right after (or possibly during?) the related kernel

Re: [PATCH v12] ath10k: add LED and GPIO controlling support for various chipsets

On 26 February 2018 at 09:44, wrote: > From: Sebastian Gottschall > > Adds LED and GPIO Control support for 988x, 9887, 9888, 99x0, 9984 based > chipsets with on chipset connected led's > using WMI Firmware API. > The LED device will get

Re: Deadlock debugging help.

On 02/27/2018 12:49 PM, Ben Greear wrote: I notice I can reliably lock up the kernel if I rmmod ath10k while it is under heavy tx/rx traffic. First, this causes the firmware to crash, and then right after (or possibly during?) the related kernel threads deadlock. This is with my hacked driver

Deadlock debugging help.

I notice I can reliably lock up the kernel if I rmmod ath10k while it is under heavy tx/rx traffic. First, this causes the firmware to crash, and then right after (or possibly during?) the related kernel threads deadlock. This is with my hacked driver and hacked firmware. In particular, the

Re: [PATCH v12] ath10k: add LED and GPIO controlling support for various chipsets

Am 27.02.2018 um 18:03 schrieb Steve deRosier: On Mon, Feb 26, 2018 at 12:44 AM, wrote: From: Sebastian Gottschall Adds LED and GPIO Control support for 988x, 9887, 9888, 99x0, 9984 based chipsets with on chipset connected led's using

Re: [PATCH v12] ath10k: add LED and GPIO controlling support for various chipsets

On Mon, Feb 26, 2018 at 12:44 AM, wrote: > > From: Sebastian Gottschall > > Adds LED and GPIO Control support for 988x, 9887, 9888, 99x0, 9984 based > chipsets with on chipset connected led's > using WMI Firmware API. > The LED device will

Re: ath10k: update the IRAM banks number for QCA9377

ryan...@codeaurora.org wrote: > Preparation for a new QCA9377 firmware release. The new firmware release > requires more IRAM banks, hence update that on ath10k. > > The IRAM banks promotion won't break any backwards compatibility, as those > IRAM > banks were not getting used in previous

Re: ath10k: Fix log message for hif power on failure

Govind Singh wrote: > HIF power-on failure is applicable to each underlying > bus type. Fix log message for hif power on failure. > > Signed-off-by: Govind Singh > Signed-off-by: Kalle Valo Patch applied to ath-next branch

Re: fixed bit rate 9Mbps set as 24Mbps in g mode(legacy)

On 02/27/2018 12:49 AM, KAVITA MATHUR wrote: Hi, I have configured AP in g mode and tested legacy rates.All basic rates and supported rates(1,2,5.5,11,6,9,12,18,24,36,48,54) are set except 9Mbps. When fixed bit rate 9Mbps is set, it gets set as 24 Mbps. This issue has been observed in

Re: [PULL] ath10k firmware 20180219

the latest 9984 firmware firmware-5.bin_10.4-3.5.3-00053 will crash under certain configuration. it was configured as wds ap with vht 160. client (wds sta) was a wrt3200 with 88W8964

fixed bit rate 9Mbps set as 24Mbps in g mode(legacy)

Hi, I have configured AP in g mode and tested legacy rates.All basic rates and supported rates(1,2,5.5,11,6,9,12,18,24,36,48,54) are set except 9Mbps. When fixed bit rate 9Mbps is set, it gets set as 24 Mbps. This issue has been observed in backports-4.4.2-1 as well as latest git version of

Re: [PULL] ath10k firmware 20180219

what about this? [   90.164755] ath10k_pci 0001:03:00.0: firmware crashed! (uuid n/a) [   90.170845] ath10k_pci 0001:03:00.0: qca9984/qca9994 hw1.0 target 0x0100 chip_id 0x sub 168c:cafe [   90.180747] ath10k_pci 0001:03:00.0: kconfig debug 1 debugfs 1 tracing 0 dfs 0 testmode 0 [