Re: [PATCH 2/2] ath10k: DFS Host Confirmation

Adrian Chadd writes: > On Mon, 14 May 2018 at 11:25, Kalle Valo wrote: > >> Adrian Chadd writes: > >> > May we have a little more information about how this is supposed to > work? >> > >> > It looks like we're supposed to send the

Re: [PATCH 2/2] ath10k: DFS Host Confirmation

On Mon, 14 May 2018 at 11:25, Kalle Valo wrote: > Adrian Chadd writes: > > May we have a little more information about how this is supposed to work? > > > > It looks like we're supposed to send the information about the matched > > radar pattern back

Re: [PATCH 2/2] ath10k: DFS Host Confirmation

Which regulatory enforcement are you talking to? Are you talking about such "prevent users from changing regulatory domain" or "don't provide a manner to change regulatory domain or channel list" ? If not, can you share the section of document? Sorry, I don't have any references about that.

Re: Support for QCA9377

On Mon, May 14, 2018 at 12:50 PM, Patrick Doyle wrote: > On Mon, May 14, 2018 at 3:28 PM, Gangadharan Vemula > wrote: >> Hi, >> >> Silex patch-set was applied to master-pending branch of ath.git. Now, >> it is in the process of getting into

Re: Support for QCA9377

On Mon, May 14, 2018 at 3:28 PM, Gangadharan Vemula wrote: > Hi, > > Silex patch-set was applied to master-pending branch of ath.git. Now, > it is in the process of getting into mainline, Mr. Kvalo is working on > it. Thank you. I will check that out. > Need to

Re: Support for QCA9377

Hi, Silex patch-set was applied to master-pending branch of ath.git. Now, it is in the process of getting into mainline, Mr. Kvalo is working on it. As silex patches were developed on top of ath10k (which has others developers patches from community), need to have those patches as well. The

Re: [PATCH 2/2] ath10k: DFS Host Confirmation

Adrian Chadd writes: > May we have a little more information about how this is supposed to work? > > It looks like we're supposed to send the information about the matched > radar pattern back to the firmware for confirmation? What's the intended > behaviour from the

Re: [PATCH 2/2] ath10k: DFS Host Confirmation

Peter Oh writes: > On 05/02/2018 04:27 AM, Kalle Valo wrote: >> Peter Oh writes: >> >>> On 04/30/2018 10:45 AM, Sriram R wrote: In the 10.4-3.6 firmware branch there's a new DFS Host confirmation feature which is advertised using

Support for QCA9377

Hello All, Where can I look to learn about support for the QCA9377. I would like to evaluate this module with an SDIO interface to an embedded (Atmel/Microchip) processor running a 4.9.x kernel. I found https://patchwork.kernel.org/patch/9979563/, along with 10 other patches submitted by Silex

[PATCH v2 2/3] ath10k: Don't try un-supported idle_ps_config command.

From: Ben Greear The warning the the logs does not give user a clue as to what command is failing, so it is worth it to check for un-supported command before trying the call. And add return-code to survey error message. Signed-off-by: Ben Greear

[PATCH v2 3/3] ath10k: Support survey dump for ath10k-ct 10.1 firmware.

From: Ben Greear Recent ath10k-ct 10.1 firmware supports survey results, and advertises the appropriate service flags. This confuses the ath10k driver because the 10.1 wmi commands are not set up for survey information. So, this patch adds support for handling survey

[PATCH v2 1/3] ath10k: Add ath10k-ct firmware feature flags and descriptions.

From: Ben Greear These feature flags are used by ath10k-ct firmware. Add these so we can use them in future patches and so there are no warnings about feature flags on loading ath10k-ct firmware. Signed-off-by: Ben Greear --- v2: Fix warings

Re: [PATCH 1/2] ath: Add support to get the detected radar specifications

Peter Oh writes: > On 04/30/2018 10:45 AM, Sriram R wrote: >> This enables ath10k/ath9k drivers to collect the specifications of the >> radar type once it is detected by the dfs pattern detector unit. >> Usage of the collected info is specific to driver

Re: [PATCH v3 00/12] *** Add support for wifi QMI client driver ***

Govind Singh writes: > Add QMI client driver for Q6 integrated WLAN connectivity subsystem. > This module is responsible for communicating WLAN control messages to FW > over QMI interface. > > “QUALCOMM Messaging Interface”(QMI) provides the control interface between >

Re: [PATCH 07/12] ath10k: Add MSA handshake QMI mgs support

Hi Bjorn, Thanks for the review. On 2018-05-12 00:13, Bjorn Andersson wrote: On Sun 25 Mar 22:40 PDT 2018, Govind Singh wrote: HOST allocates 2mb of region for modem and WCN3990 secure access and provides the address and access control to target for secure access. Add MSA handshake

Re: [PATCH 04/12] ath10k: add support to start and stop qmi service

On 2018-05-11 23:13, Bjorn Andersson wrote: On Sun 25 Mar 22:39 PDT 2018, Govind Singh wrote: Add support to start qmi service to configure the wlan firmware component and register event notifier to communicate with the WLAN firmware over qmi communication interface. Signed-off-by: Govind

Re: [PATCH 01/12] ath10k: Add qmi service for wlan qmi client

Bjorn Andersson writes: >> new file mode 100644 >> index 000..5857c0c >> --- /dev/null >> +++ b/drivers/net/wireless/ath/ath10k/qmi_svc_v01.c >> @@ -0,0 +1,2323 @@ >> +/* >> + * Copyright (c) 2018 The Linux Foundation. All rights reserved. >> + * >> + * Permission

Re: [PATCH 03/12] ath10k: Add ath10k QMI client driver

Hi Bjorn, Thanks for the review. On 2018-05-11 22:55, Bjorn Andersson wrote: On Sun 25 Mar 22:39 PDT 2018, Govind Singh wrote: Add QMI client driver for Q6 integrated WLAN connectivity subsystem. This module is responsible for communicating WLAN control messages to FW over QUALCOMM MSM