[PATCH 1/2] ath10k: add new pdev parameters for fw 10.2

New pdev paramters have been added to firmware 10.2, hence update wmi interfaces to sync with. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/ath10k/wmi.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/net/wireless/ath/ath10k/wmi.h b/drivers/net

[PATCH 2/2] ath10k: add new wmi interface of NF cal period

frequent NF calibration, so that RSSI reported in receive frames is more realistic. Till now calibration was done at 30 seconds. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/ath10k/core.h | 1 + drivers/net/wireless/ath/ath10k/debug.c | 64

Re: [PATCH] ath10k: unregister and remove frag_threshold callback

On 12/10/2014 11:03 AM, Ben Greear wrote: On 12/10/2014 10:33 AM, poh wrote: On 12/05/2014 07:59 PM, Ben Greear wrote: On 12/05/2014 09:16 AM, Peter Oh wrote: Setting fragmentation threshold has not been supported by any of firmware versions, hence unregister the callback and remove

[PATCH] ath10k: set phymode to 11b when NO_OFDM flag set

phymode should use 11b only if NO_OFDM flags is set. Hence check up channel flag for NO_OFDM and set to 11b. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/ath10k/mac.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/net/wireless/ath

Re: [PATCH] ath10k: Replace ioread with wmb for data sync

On 02/02/2015 11:47 AM, Johannes Berg wrote: On Mon, 2015-02-02 at 11:36 -0800, Peter Oh wrote: On 02/02/2015 11:22 AM, Johannes Berg wrote: You basically have the following sequence: iowrite() ioread() If you look, you'll see that iowrite() is actually done (or should be, or perhaps

Re: [PATCH] ath10k: Replace ioread with wmb for data sync

Hi Florian, Very appreciate your explanation in detail. Regards, Peter On 02/02/2015 03:25 PM, Florian Fainelli wrote: On 02/02/15 14:06, Peter Oh wrote: On 02/02/2015 11:47 AM, Johannes Berg wrote: On Mon, 2015-02-02 at 11:36 -0800, Peter Oh wrote: On 02/02/2015 11:22 AM, Johannes Berg

Re: [PATCH] ath10k: Replace ioread with wmb for data sync

On 02/02/2015 02:26 PM, Adrian Chadd wrote: On 30 January 2015 at 18:06, Sujith Manoharan suj...@msujith.org wrote: Peter Oh wrote: Please refer the email thread that I mentioned about other architectures. (dsb is for ARM and other platforms have the equivalent instruction such as sfence

Re: [PATCH] ath10k: Replace ioread with wmb for data sync

On 01/30/2015 06:06 PM, Sujith Manoharan wrote: Peter Oh wrote: Please refer the email thread that I mentioned about other architectures. (dsb is for ARM and other platforms have the equivalent instruction such as sfence, sync, mf, and dcs). Ok. Also the patch is updated with 2nd patch

Re: [PATCH 1/3] ath: Introduce chirp parameter used by DFS

On 02/12/2015 01:17 PM, Peter Oh wrote: Some of radar types such as FCC radar type 5 require to look up chirp in pulse to detect genuine radar and it will prevent DFS channels from false radar detection. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath

[PATCH 3/3] ath: Enhance radar detection by looking up chirp

Certain radar types such as FCC radar type 5 are using chirp in their pulses, hence looking up the chirp status will enhance to avoid false radar detection. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/dfs_pri_detector.c | 4 1 file changed, 4 insertions

[PATCH 1/3] ath: Introduce chirp parameter used by DFS

Some of radar types such as FCC radar type 5 require to look up chirp in pulse to detect genuine radar and it will prevent DFS channels from false radar detection. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/dfs_pattern_detector.c | 52

[PATCH 2/3] ath10k: Update chirp value in pulse event

Firmware reports chirp status in phy error event if it's detected and the chirp status is valuable to distinguish radar types. So save it to use for DFS parttern detector. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/ath10k/wmi.c | 2 +- 1 file changed, 1 insertion

Re: [PATCH] ath10k: Replace ioread with wmb for data sync

On 01/27/2015 01:33 PM, Bob Copeland wrote: On Mon, Jan 26, 2015 at 02:25:18PM -0800, Peter Oh wrote: Using ioread() to perform data sync is excessive. Use compact API, wmb(), that intended to be used for the case. It reduces total 14 CPU clocks per interrupt. Hi, ath10k_pci_write32

Re: [PATCH] ath10k: Replace ioread with wmb for data sync

On 01/27/2015 08:30 PM, Bob Copeland wrote: On Tue, Jan 27, 2015 at 03:53:00PM -0800, Peter Oh wrote: - /* IMPORTANT: this extra read transaction is required to -* flush the posted write buffer. */ - (void)ath10k_pci_read32(ar, SOC_CORE_BASE_ADDRESS

Re: [PATCH v2] ath10k: Replace ioread with mb to drain write buffer

On 01/30/2015 04:14 PM, Peter Oh wrote: Using ioread() to perform draining write buffer is excessive. Use compact API, mb(), that intended to be used for the case. It reduces total 14 CPU clocks per interrupt. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/ath10k

[PATCH v2] ath10k: Replace ioread with mb to drain write buffer

Using ioread() to perform draining write buffer is excessive. Use compact API, mb(), that intended to be used for the case. It reduces total 14 CPU clocks per interrupt. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/ath10k/pci.c | 12 1 file changed, 4

[PATCH] ath10k: Replace ioread with wmb for data sync

Using ioread() to perform data sync is excessive. Use compact API, wmb(), that intended to be used for the case. It reduces total 14 CPU clocks per interrupt. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/ath10k/pci.c | 12 1 file changed, 4 insertions

Re: [PATCH v2 2/2] ath10k: Increase copy engine entries for rx wmi

On 02/08/2015 09:46 PM, Rajkumar Manoharan wrote: Having lower number of copy engine entries for target to host WMI ring is causing drops in receiving management frames. This issue is observed during max clients (128 clients) stress testing. While bursting deauthentication frames from simulated

[PATCH] ath10k: enable channel 144 on 5GHz band

Enable channel 144 on 5GHz band since 802.11ac introduced it. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/ath10k/mac.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/wireless/ath/ath10k/mac.c b/drivers/net/wireless/ath/ath10k/mac.c index 341f3c8

Re: [PATCH] ath: use PRI value given by spec for fixed PRI

On 03/30/2015 02:55 AM, Zefir Kurtisi wrote: On 03/27/2015 05:59 PM, Peter Oh wrote: PRI value is used as divider when DFS detector analyzes candidate radar pulses. If PRI deviation is big from its origin PRI, DFS detector could miss valid radar reports since HW often misses detecting radar

[PATCH 2/2] ath: lower JP W53 band DFS detection threshold around 30%

to achieve the rate. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/dfs_pattern_detector.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/wireless/ath/dfs_pattern_detector.c b/drivers/net/wireless/ath/dfs_pattern_detector.c index 8d1e082

[PATCH v2 2/2] ath: lower JP W53 band DFS detection threshold around 30%

to achieve the rate. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/dfs_pattern_detector.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/wireless/ath/dfs_pattern_detector.c b/drivers/net/wireless/ath/dfs_pattern_detector.c index 2d4ad45

Re: [PATCH] ath: support new FCC DFS Radar Type 1

On 03/02/2015 05:29 PM, Peter Oh wrote: On 02/27/2015 02:45 AM, Zefir Kurtisi wrote: On 02/25/2015 11:17 PM, Peter Oh wrote: Add support for new FCC DFS rules released on August 14, 2014. FCC has added a new radar type named Radar Type 1 and original Radar Type 1 is renamed to Radar Type 0

[PATCH] ath10k: increase relay buffer size of spectral scan

. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/ath10k/spectral.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/net/wireless/ath/ath10k/spectral.c b/drivers/net/wireless/ath/ath10k/spectral.c index d22addf..8dcd424 100644 --- a/drivers/net

Re: [PATCH] ath: use PRI value given by spec for fixed PRI

On 04/15/2015 05:41 AM, Kalle Valo wrote: Peter Oh p...@codeaurora.org writes: As for your patch at hand, I tested it for ETSI and it does not change detector performance, The patch is useful when there are many missing pulses within a burst. It happens almost every time when channel loading

Re: [PATCH] ath: use PRI value given by spec for fixed PRI

Hi, On 04/01/2015 03:04 AM, Zefir Kurtisi wrote: On 03/30/2015 07:57 PM, Peter Oh wrote: On 03/30/2015 02:55 AM, Zefir Kurtisi wrote: [...] That's why I believe we need to be very cautious when changing it to fix / improve minor issues. This patch is not for minor fix. Current DFS detector

Re: [PATCH v2 8/8] ath10k: configure frag desc memory to target for qca99X0

Hi Raja, On 06/22/2015 07:52 AM, Raja Mani wrote: Pre qca99X0 chipsets follows the model where dynamically allocate memory for frag desc on getting new skb for TX. But, this is not going to be the case in qca99X0. It expects frag desc memory to be allocated at boot time and let the driver to

[PATCH 2/3] ath10k: redefine rx_ppdu_end_common structure to cover qca99x0

rx_ppdu_end_common structure is valid for both of qca998x and qca6174, but not for qca99x0 since it has new additional members. Hence update the common structure to cover qca99x0 as well. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/ath10k/rx_desc.h | 12

[PATCH 1/3] ath10k: update tx path to support QCA99X0

corresponding frag data. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/ath10k/htt.h| 13 +++-- drivers/net/wireless/ath/ath10k/htt_tx.c | 29 + 2 files changed, 32 insertions(+), 10 deletions(-) diff --git a/drivers/net/wireless

RE: How to access the CCA related operation

There is WMI_10_x_SET_CCA_PARAMS_CMDID which to enable adaptive CCA in firmware supported since 10.2.4 and all the actual operations are done in firmware with registers as Ben addressed. But I'm not clear how much register doc or firmware doc are opened to public legally. Thanks, Peter

Re: [PATCH] ath10k: Add QCA99X0 to supported device list

On 08/06/2015 12:59 AM, Felix Fietkau wrote: On 2015-08-06 09:43, Vasanthakumar Thiagarajan wrote: On Wednesday 05 August 2015 05:51 PM, Felix Fietkau wrote: On 2015-07-21 13:36, Vasanthakumar Thiagarajan wrote: Add vendor/device id of QCA99X0 V2.0 to pci id table and

[PATCH] ath10k: initialize msdu ext. descriptor before use

behavior, but initializing whole msdu ext. descriptor will help to clear uncertainty of firmware could bring on as it constantly updated. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/ath10k/htt_tx.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

[PATCH v3 2/3] ath10k: redefine rx_ppdu_end_common structure to cover qca99x0

rx_ppdu_end_common structure is valid for both of qca998x and qca6174, but not for qca99x0 since it has new additional members. Hence update the common structure to cover qca99x0 as well. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/ath10k/rx_desc.h | 12

[PATCH v3 3/3] ath10k: add support for qca99x0 Rx descriptors

and QCA6174 will have extra 44 bytes padding in Rx descriptor layout which is harmless. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/ath10k/htt_rx.c | 24 ++--- drivers/net/wireless/ath/ath10k/rx_desc.h | 163 +- 2 files changed, 172

[PATCH v2 1/3] ath10k: update tx path to support QCA99X0

corresponding frag data. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/ath10k/htt.h| 13 +++-- drivers/net/wireless/ath/ath10k/htt_tx.c | 29 + 2 files changed, 32 insertions(+), 10 deletions(-) diff --git a/drivers/net/wireless

[PATCH v2 2/3] ath10k: redefine rx_ppdu_end_common structure to cover qca99x0

rx_ppdu_end_common structure is valid for both of qca998x and qca6174, but not for qca99x0 since it has new additional members. Hence update the common structure to cover qca99x0 as well. Signed-off-by: Peter Oh p...@qca.qualcomm.com --- drivers/net/wireless/ath/ath10k/rx_desc.h | 12

[PATCH] ath10k: Enable VHT for Mesh

in this patch. Signed-off-by: Peter Oh <p...@qca.qualcomm.com> --- drivers/net/wireless/ath/ath10k/mac.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/wireless/ath/ath10k/mac.c b/drivers/net/wireless/ath/ath10k/mac.c index a53e213..d38e4d8 100644 --- a/drivers/net/wireless/ath/ath10k

Re: [PATCH v2] cfg80211: add VHT support for Mesh

On 11/12/2015 01:40 PM, Johannes Berg wrote: On Thu, 2015-11-12 at 13:33 -0800, Peter Oh wrote: At this moment Mesh Point is not able to be brought up by userspace such as wap_supplicant at VHT data rates because there is no events/NL80211 defined that userspace can check out if drivers can

Re: [PATCH v2] cfg80211: add VHT support for Mesh

On 11/12/2015 02:32 PM, Johannes Berg wrote: On Thu, 2015-11-12 at 14:28 -0800, Peter Oh wrote: Exactly the same communication mechanism and purpose are used with NL80211_EXT_FEATURE_VHT_IBSS which is already a part of NL80211 feature flag. The new feature flag, NL80211_EXT_FEATURE_VHT_MESH

[PATCH] ath10k: Enable VHT for Mesh

in this patch. Signed-off-by: Peter Oh <p...@qca.qualcomm.com> --- drivers/net/wireless/ath/ath10k/mac.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/wireless/ath/ath10k/mac.c b/drivers/net/wireless/ath/ath10k/mac.c index a53e213..d38e4d8 100644 --- a/drivers/net/wireless/ath/ath10k

[PATCH] cfg80211: add VHT support for Mesh

Add NL80211_EXT_FEATURE_VHT_MESH flag to allow drivers to indicate support for VHT in Mesh mode. Signed-off-by: Peter Oh <p...@qca.qualcomm.com> --- include/uapi/linux/nl80211.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/uapi/linux/nl80211.h b/include/uapi/linux/nl8

Re: [PATCH] ath10k: use pre-allocated DMA buffer in Tx

, Kalle Valo wrote: Peter Oh <p...@qca.qualcomm.com> writes: ath10k driver is using dma_pool_alloc per packet and dma_pool_free in coresponding at Tx completion. Use of pre-allocated DMA buffer in Tx will improve saving CPU resource by 5% while it consumes about 56KB memory more as tra

Re: [PATCH] ath10k: use pre-allocated DMA buffer in Tx

FYI, pre-allocated dma is coherent dma used in Tx only and only freed when ath10k driver stops. On 10/08/2015 10:17 AM, Peter Oh wrote: Does it happen after you applied copy engine patchset or even without the patchset? I saw ath10k_pci_htt_tx_cb in backtrace which is not merged to master branch

[PATCH v2] ath: use PRI value given by spec for fixed PRI

valid. By using spec defined PRI for fixed PRI, we can correct this error. Signed-off-by: Peter Oh <p...@qca.qualcomm.com> --- drivers/net/wireless/ath/dfs_pattern_detector.c | 6 -- drivers/net/wireless/ath/dfs_pattern_detector.h | 5 + drivers/net/wireless/ath/dfs_pri_detector.c

Re: [PATCH] ath10k: only advertise mesh support in raw mode

Hi, On 09/28/2015 05:59 AM, Bob Copeland wrote: Rather than always advertising mesh support and then generating an error when the user attempts to bring up the device without rawmode, only advertise it when available: that is, if the module is loaded with rawmode=1, the firmware supports it,

Re: [PATCH] ath10k: only advertise mesh support in raw mode

On 09/30/2015 07:54 PM, Bob Copeland wrote: On Mon, Sep 28, 2015 at 10:27:30AM -0700, Peter Oh wrote: I prefer the current design to this new approach because drivers already know if it's mesh capable or not at build time, hence adding runtime configuration is redundant. I do think

[PATCH v2] ath: use PRI value given by spec for fixed PRI

valid. By using spec defined PRI for fixed PRI, we can correct this error. Signed-off-by: Peter Oh <p...@qca.qualcomm.com> --- v2: * replaced numeral 16 with PRI_TOLERANCE macro --- drivers/net/wireless/ath/dfs_pattern_detector.c | 6 -- drivers/net/wireless/ath/dfs_pattern_detector

[PATCH] ath10k: use Rx decap mode configured when driver registered

registration stage in case of using raw mode, so that host driver receives MAC frame header containing necessary fields such as QoS and Mesh Control and uses them in right way to make data traffic work. Signed-off-by: Peter Oh <p...@qca.qualcomm.com> --- drivers/net/wireless/ath/ath10k/wmi

[PATCH] ath10k: allow Mesh Point to install peer security key

supporting secured Mesh at this moment. Signed-off-by: Peter Oh <p...@qca.qualcomm.com> --- drivers/net/wireless/ath/ath10k/mac.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/net/wireless/ath/ath10k/mac.c b/drivers/net/wireless/ath/ath10k/mac.c index bcb364d..b

Re: [PATCH] ath10k: add modparam 'hw_csum' to make HW checksum configurable

On 12/16/2015 12:35 PM, Felix Fietkau wrote: On 2015-12-16 21:29, Peter Oh wrote: On 12/16/2015 10:27 AM, Felix Fietkau wrote: On 2015-12-16 19:20, Peter Oh wrote: Some hardwares such as QCA988X and QCA99X0 doesn't have capability of checksum offload when frame formats are not suitable

Re: [PATCH] ath10k: add modparam 'hw_csum' to make HW checksum configurable

On 12/16/2015 10:27 AM, Felix Fietkau wrote: On 2015-12-16 19:20, Peter Oh wrote: Some hardwares such as QCA988X and QCA99X0 doesn't have capability of checksum offload when frame formats are not suitable for it such as Mesh frame. Hence add a module parameter, hw_csum, to make checksum

[PATCH] ath10k: add modparam 'hw_csum' to make HW checksum configurable

Some hardwares such as QCA988X and QCA99X0 doesn't have capability of checksum offload when frame formats are not suitable for it such as Mesh frame. Hence add a module parameter, hw_csum, to make checksum offload configurable during module registration time. Signed-off-by: Peter Oh &l

Re: [PATCH] ath10k: add modparam 'hw_csum' to make HW checksum configurable

On 12/16/2015 12:53 PM, Felix Fietkau wrote: On 2015-12-16 21:46, Peter Oh wrote: On 12/16/2015 12:35 PM, Felix Fietkau wrote: On 2015-12-16 21:29, Peter Oh wrote: On 12/16/2015 10:27 AM, Felix Fietkau wrote: On 2015-12-16 19:20, Peter Oh wrote: Some hardwares such as QCA988X and QCA99X0

Re: [PATCH] ath10k: add modparam 'hw_csum' to make HW checksum configurable

On 12/16/2015 01:54 PM, Felix Fietkau wrote: On 2015-12-16 22:19, Peter Oh wrote: On 12/16/2015 12:53 PM, Felix Fietkau wrote: On 2015-12-16 21:46, Peter Oh wrote: On 12/16/2015 12:35 PM, Felix Fietkau wrote: On 2015-12-16 21:29, Peter Oh wrote: On 12/16/2015 10:27 AM, Felix Fietkau wrote

Re: [PATCH] ath10k: add modparam 'hw_csum' to make HW checksum configurable

On 12/16/2015 03:59 PM, Felix Fietkau wrote: On 2015-12-17 00:50, Peter Oh wrote: On 12/16/2015 01:54 PM, Felix Fietkau wrote: On 2015-12-16 22:19, Peter Oh wrote: On 12/16/2015 12:53 PM, Felix Fietkau wrote: On 2015-12-16 21:46, Peter Oh wrote: On 12/16/2015 12:35 PM, Felix Fietkau wrote

Re: [PATCH] ath10k: add modparam 'hw_csum' to make HW checksum configurable

On 12/17/2015 02:57 PM, Felix Fietkau wrote: On 2015-12-17 23:01, Peter Oh wrote: On 12/16/2015 03:59 PM, Felix Fietkau wrote: On 2015-12-17 00:50, Peter Oh wrote: On 12/16/2015 01:54 PM, Felix Fietkau wrote: On 2015-12-16 22:19, Peter Oh wrote: On 12/16/2015 12:53 PM, Felix Fietkau wrote

[PATCH] ath10k: Set SM power save disabled to default value

SMPS, because they are capable to switch the mode to dynamic or static either at the end of frame sequence or by using SMPS action frame. Signed-off-by: Peter Oh <p...@qca.qualcomm.com> --- drivers/net/wireless/ath/ath10k/mac.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff

[PATCH 2/3] ath10k: introduce new subtypes for proxy STA and Mesh

QCA988X firmware starting from 10.2.4.70.12-2 supports new vdev subtypes for proxy STA and Mesh, hence add them to be used as needed. Signed-off-by: Peter Oh <p...@qca.qualcomm.com> --- drivers/net/wireless/ath/ath10k/wmi.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drive

[PATCH 1/3] ath10k: update WMI 10.x service map

Update WMI 10.x service map to sync with firmware 10.2.4.70.12-2 released on 11/11/2015 which is the latest QCA988X firmware as of 11/18/2015. Signed-off-by: Peter Oh <p...@qca.qualcomm.com> --- drivers/net/wireless/ath/ath10k/wmi.h | 15 +++ 1 file changed, 15 insertions(+)

Re: [PATCH] ath10k: deliver mgmt frames from htt to monitor vifs only

On 11/30/2015 04:56 AM, Grzegorz Bajorski wrote: Until now only WMI originating mgmt frames were reported to mac80211. Management frames on HTT were basically dropped (except frames which looked like management but had FCS error). To allow sniffing all frames (including offloaded frames)

Re: [PATCH 2/2] ath10k: do not use coherent memory for tx buffers

On 11/23/2015 10:18 AM, Felix Fietkau wrote: On 2015-11-23 18:25, Peter Oh wrote: Hi, Have you measured the peak throughput? The pre-allocated coherent memory concept was introduced as once of peak throughput improvement. It's all still pre-allocated and pre-mapped. Right. I mis-guessed

Re:

On 01/13/2016 09:36 PM, Alexey Ivanov wrote: Yes, you're right, Michał putting cal.bin to lib/firmware/ath10k helped (before I put it to lib/firmware/ath10k/QCA988X/hw2.0/) but the mac address is still 00:03:7F:00:00:00 cal file has a mac address in it and ath10k uses it as default unless

Re: Regulatory Domains and Japan Channel 14

On 01/18/2016 05:46 AM, Tomi Saarnio wrote: Dear All, We are trying to perform scanning at the 2.4GHz band with the JP (Japan) regulatory domain, but it seems that the ath10k refuses to scan the channel 14 although the channel 14 is a valid channel in Japan (with certain rate and transmit

[PATCH v2 2/4] ath10k: update 10.4 WMI service map

Update 10.4 WMI service map to sync to the latest 10.4 firmware as of 1/20/2016. Signed-off-by: Peter Oh <p...@qca.qualcomm.com> --- drivers/net/wireless/ath/ath10k/wmi.h | 11 +++ 1 file changed, 11 insertions(+) diff --git a/drivers/net/wireless/ath/ath10k/wmi.h b/drive

[PATCH v2 4/4] ath10k: add abstraction layer for vdev subtype

. Hence use the abstraction API to get right subtype to use. Signed-off-by: Peter Oh <p...@qca.qualcomm.com> --- drivers/net/wireless/ath/ath10k/mac.c | 15 --- drivers/net/wireless/ath/ath10k/wmi-ops.h | 11 + drivers/net/wireless/ath/ath10k/wmi-tlv.c | 1 + drivers/net/wirele

[PATCH v2 1/4] ath10k: rename Mesh related service names

-off-by: Peter Oh <p...@qca.qualcomm.com> --- drivers/net/wireless/ath/ath10k/mac.c | 4 ++-- drivers/net/wireless/ath/ath10k/wmi.h | 16 +--- 2 files changed, 11 insertions(+), 9 deletions(-) diff --git a/drivers/net/wireless/ath/ath10k/mac.c b/drivers/net/wireless/ath/ath10k

[PATCH v2 3/4] ath10k: use vif->type and vif->p2p for P2P_GO check

Interface type P2P_GO can be checked by either arvif->vdev_type and arvif->vdev_subtype or vif->type and vif->p2p. Use later one to avoid more cpu consumption that could happen when subtype abstraction layer change is introduced. Signed-off-by: Peter Oh <p...@qca.qualcomm.com>

[PATCH 1/4] ath10k: rename Mesh related service names

-off-by: Peter Oh <p...@qca.qualcomm.com> --- drivers/net/wireless/ath/ath10k/mac.c | 4 ++-- drivers/net/wireless/ath/ath10k/wmi.h | 16 +--- 2 files changed, 11 insertions(+), 9 deletions(-) diff --git a/drivers/net/wireless/ath/ath10k/mac.c b/drivers/net/wireless/ath/ath10k

[PATCH 0/4] ath10k: rename mesh and add abstraction layer

Split Mesh service to 11s Mesh and non-11s Mesh according to firmware service bit to help users distinguish 11s Mesh from non 11s Mesh. And add abstraction layer for vdev subtype to solve subtype mismatch and to give flexible compatibility among different firmware revisions. Peter Oh (4

[PATCH 4/4] ath10k: add abstraction layer for vdev subtype

. Hence use the abstraction API to get right subtype to use. Signed-off-by: Peter Oh <p...@qca.qualcomm.com> --- drivers/net/wireless/ath/ath10k/mac.c | 15 --- drivers/net/wireless/ath/ath10k/wmi-ops.h | 11 + drivers/net/wireless/ath/ath10k/wmi-tlv.c | 1 + drivers/net/wirele

[PATCH 3/4] ath10k: use vif->type and vif->p2p for P2P_GO check

Interface type P2P_GO can be checked by either arvif->vdev_type and arvif->vdev_subtype or vif->type and vif->p2p. Use later one to avoid more cpu consumption that could happen when subtype abstraction layer change is introduced. Signed-off-by: Peter Oh <p...@qca.qualcomm.com>

[PATCH 2/4] ath10k: update 10.4 WMI service map

Update 10.4 WMI service map to sync to the latest 10.4 firmware as of 1/20/2016. Signed-off-by: Peter Oh <p...@qca.qualcomm.com> --- drivers/net/wireless/ath/ath10k/wmi.h | 13 + 1 file changed, 13 insertions(+) diff --git a/drivers/net/wireless/ath/ath10k/wmi.h b/drive

Re: [PATCH 0/4] ath10k: rename mesh and add abstraction layer

On 01/27/2016 11:39 AM, Bob Copeland wrote: On Wed, Jan 27, 2016 at 10:55:53AM -0800, Peter Oh wrote: Split Mesh service to 11s Mesh and non-11s Mesh according to firmware service bit to help users distinguish 11s Mesh from non 11s Mesh. And add abstraction layer for vdev subtype to solve

Re: [PATCH v2] ath10k: set MAC timestamp in management Rx frame

On 02/24/2016 12:40 AM, Michal Kazior wrote: On 23 February 2016 at 20:44, Peter Oh <p...@qca.qualcomm.com> wrote: From: poh <p...@qca.qualcomm.com> Check and set Rx MAC timestamp when firmware indicates it. Firmware adds it in Rx beacon frame only at this moment. Driver and

[PATCH v3] ath10k: set MAC timestamp in management Rx frame

Check and set Rx MAC timestamp when firmware indicates it. Firmware adds it in Rx beacon frame only at this moment. Driver and mac80211 may utilize it to detect such clockdrift or beacon collision and use the result for beacon collision avoidance. Signed-off-by: Peter Oh <p...@qca.qualcomm.

[PATCH] ath10k: set MAC timestamp in management Rx frame

From: poh Check and set Rx MAC timestamp when firmware indicates it. Firmware adds it in Rx beacon frame only at this moment. Driver and mac80211 may utilize it to detect such clockdrift or beacon collision and use the result for beacon collision avoidance. Signed-off-by:

[PATCH v2] ath10k: set MAC timestamp in management Rx frame

From: poh Check and set Rx MAC timestamp when firmware indicates it. Firmware adds it in Rx beacon frame only at this moment. Driver and mac80211 may utilize it to detect such clockdrift or beacon collision and use the result for beacon collision avoidance. Signed-off-by:

Re: Which firmware has raw mode support

On 02/25/2016 07:58 AM, Xue Liu wrote: Hello, I have a WLE900VX (QCA9880) 11ac card and would like to do some mesh test. I have try some firmware from https://github.com/kvalo/ath10k-firmware/tree/master/QCA988X/10.2.4 but no luck. Could someone tell me that which firmware has raw mode

Re: [PATCH v3] ath10k: set MAC timestamp in management Rx frame

Hi, On 02/25/2016 08:34 AM, Valo, Kalle wrote: Peter Oh <p...@qca.qualcomm.com> writes: Check and set Rx MAC timestamp when firmware indicates it. Firmware adds it in Rx beacon frame only at this moment. Driver and mac80211 may utilize it to detect such clockdrift or beacon collision a

[PATCH v4] ath10k: set MAC timestamp in management Rx frame

Check and set Rx MAC timestamp when firmware indicates it. Firmware adds it in Rx beacon frame only at this moment. Driver and mac80211 may utilize it to detect such clockdrift or beacon collision and use the result for beacon collision avoidance. Signed-off-by: Peter Oh <p...@qca.qualcomm.

[PATCH v5] ath10k: set MAC timestamp in management Rx frame

Check and set Rx MAC timestamp when firmware indicates it. Firmware adds it in Rx beacon frame only at this moment. Driver and mac80211 may utilize it to detect such clockdrift or beacon collision and use the result for beacon collision avoidance. Signed-off-by: Peter Oh <p...@qca.qualcomm.

[PATCH] ath10k: parse Rx MAC timestamp in mgmt frame for FW 10.4

Check and parse Rx MAC timestamp when firmware sets its flag to status variable. 10.4 firmware adds it in Rx beacon frame only at this moment. Drivers and mac80211 may utilize it to detect such clockdrift or beacon collision and use the result for beacon collision avoidance. Signed-off-by: Peter

Re: [PATCH 13/13] ath10k: implement push-pull tx

On 01/21/2016 05:46 AM, Michal Kazior wrote: The current/old tx path design was that host, at its own leisure, pushed tx frames to the device. For HTT there was ~1000-1400 msdu queue depth. After reaching that limit the driver would request mac80211 to stop queues. There was little control

Re: [PATCH 13/13] ath10k: implement push-pull tx

On 01/26/2016 02:28 AM, Michal Kazior wrote: On 22 January 2016 at 08:47, Michal Kazior <michal.kaz...@tieto.com> wrote: On 21 January 2016 at 18:40, Peter Oh <p...@codeaurora.org> wrote: On 01/21/2016 05:46 AM, Michal Kazior wrote: [...] - /* TODO: apply c

Re: Mesh on ath10k drops all packets

On 01/22/2016 03:01 AM, Jeroen Roovers wrote: Maybe related? Jan 22 11:59:33 wim kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Jan 22 11:59:33 wim kernel: wlan0: Allocated STA 40:e2:30:cb:9a:11 Jan 22 11:59:33 wim kernel: wlan0: moving STA 40:e2:30:cb:9a:11 to state 2 Jan 22

Re: Mesh on ath10k drops all packets

On 01/22/2016 04:32 PM, Yeoh Chun-Yeow wrote: On Fri, Jan 22, 2016 at 11:45 PM, Jeroen Roovers wrote: On 22 January 2016 at 13:51, Bob Copeland wrote: On Fri, Jan 22, 2016 at 12:01:36PM +0100, Jeroen Roovers wrote: Maybe related? Could be.

Re: [PATCH v2] ath10k: parse Rx MAC timestamp in mgmt frame for FW 10.4

://github.com/0day-ci/linux/commits/Peter-Oh/ath10k-parse-Rx-MAC-timestamp-in-mgmt-frame-for-FW-10-4/20160323-064843 base: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git master config: x86_64-randconfig-x000-201612 (attached as .config) reproduce: # save

[PATCH v6] ath10k: set MAC timestamp in management Rx frame

Check and set Rx MAC timestamp when firmware indicates it. Firmware adds it in Rx beacon frame only at this moment. Driver and mac80211 may utilize it to detect such clockdrift or beacon collision and use the result for beacon collision avoidance. Signed-off-by: Peter Oh <p...@qca.qualcomm.

Re: [PATCH v5] ath10k: set MAC timestamp in management Rx frame

On 02/29/2016 10:33 AM, Michal Kazior wrote: On 26 February 2016 at 20:03, Peter Oh <p...@qca.qualcomm.com> wrote: Check and set Rx MAC timestamp when firmware indicates it. Firmware adds it in Rx beacon frame only at this moment. Driver and mac80211 may utilize it to detect such cloc

[PATCH 2/3] ath10k: update 10.4 WMI vdev parameters

Update 10.4 WMI vdev param to sync to current 10.4 firmware as of 2/23/2016. Signed-off-by: Peter Oh <p...@qca.qualcomm.com> --- drivers/net/wireless/ath/ath10k/wmi.h | 6 ++ 1 file changed, 6 insertions(+) diff --git a/drivers/net/wireless/ath/ath10k/wmi.h b/drivers/net/wirele

[PATCH 3/3] ath10k: enable set_tsf vdev command to WMI 10.4

10.4 firmware has addeded set_tsf vdev parameter, hence enable it. set_tsf function can be used to shift TBTT that will help avoid its clockdrift which happens when beacons are collided. Signed-off-by: Peter Oh <p...@qca.qualcomm.com> --- drivers/net/wireless/ath/ath10k/wmi.c | 2 +-

[PATCH 1/3] ath10k: add a support of set_tsf on vdev interface

10.2.4.70.24 firmware introduces new feature to set TSF via vdev parameter, hence implement relevant function. set_tsf function can be used to shift TBTT that will help avoid its clockdrift which happens when beacons are collided. Signed-off-by: Peter Oh <p...@qca.qualcomm.com> --- drive

[PATCH 0/3] ath10k: add a support of set_tsf on vdev interface

10.2.4 and 10.4 firmware has introduced new function to set TSF via vdev parameter. set_tsf function can be used to shift TBTT that will help avoid its clockdrift which happens when beacons are collided. Peter Oh (3): ath10k: add a support of set_tsf on vdev interface ath10k: update 10.4 WMI

Re: Does 99x0 support mesh mode?

On 07/08/2016 10:15 AM, Yeoh Chun-Yeow wrote: Make sure the firmware has the raw mode feature bit enabled to support mesh. In addition to that, you may check out wmi_services (cat /sys/kernel/debug/ieee80211/phyX/ath10k/wmi_services) if WMI_SERVICE_MESH_11S is set to enabled which means 11s

Re: DFS radar pattern detection in different regions

re-send in plain text mode. > I am just confused by the output of "iw reg get", which outputs lines > from the db.txt of wireless-regdb [1]. For example, the first lines of > the output for some countries read like the following: > country AE: DFS-FCC > country AF: DFS-ETSI > country BD:

Re: Issue with ATH10K driver while bringing up mesh interface

re-send in plain text mode. > >  > > Please try  "insmod ath10k_core.ko rawmode=1" > > I recommend you to use  FW version 10.2.4.70.12-2 or higher, so that you don't have to use raw mode. Main downside using raw mode is throughput throttled. You can get the ath10k firmware from 

Re: Issue with ATH10K driver while bringing up mesh interface

I was talking about QCA988X firmware and I don't think QCA99X0 has officially released firmware for mesh. Thanks, Peter From: Alexis Green <agr...@cococorp.com> Sent: Monday, August 22, 2016 10:33 AM To: Peter Oh Cc: Pedersen, Thomas; Sridhar Konabathini; michal.kaz...@tieto.com; Raj

Re: Is using 802.11s with DFS possible?

On 06/28/2017 06:54 PM, Zach Sherin wrote: Hi all, I've been running some experiments in LEDE thanks to your help many months ago, and I want to use DFS frequencies with my mesh network. Does ath10k currently support this or am I up a creek? My tests show that I can use DFS frequencies with

Re: [RFC v2 05/10] ath10k: htt: High latency TX support

On 06/12/2017 08:03 AM, Erik Stromdahl wrote: Add HTT TX function for HL interfaces. Intended for SDIO and USB. Signed-off-by: Erik Stromdahl --- diff --git a/drivers/net/wireless/ath/ath10k/mac.c b/drivers/net/wireless/ath/ath10k/mac.c index 48418f9..c5fd803 100644

Re: [RFC v2 06/10] ath10k: htt: High latency RX support

On 06/12/2017 08:03 AM, Erik Stromdahl wrote: Special HTT RX handling for high latency interfaces. Since no DMA physical addresses are used in the RX ring config message (this is not supported by the high latency devices), no RX ring is allocated. All RX skb's are allocated by the driver and

  1   2   >