On 10/4/19 5:15 AM, Johannes Berg wrote:
On Thu, 2019-10-03 at 08:13 +, Aaron Komisar wrote:
The real reason of scan failure is because mac80211 checks if it's DFS
channel, but it doesn't check if CAC is done or not.
The problem is that scan request is blocked in ETSI reg domains. In non
On 10/2/19 6:59 AM, Aaron Komisar wrote:
In non-ETSI reg domains scan is blocked when operating channel is a DFS ch.
For ETSI domains, however, once DFS channel is marked as available afer
the CAC, this channel will remain available even after leaving this channel.
Therefore a new CAC will not
On 9/19/19 10:54 AM, Peter Oh wrote:
On 9/19/19 10:46 AM, Ben Greear wrote:
On 9/19/19 10:44 AM, Peter Oh wrote:
On 9/19/19 5:22 AM, Toke Høiland-Jørgensen wrote:
From: Toke Høiland-Jørgensen
This patch ports that idea over to mac80211. The basic idea is simple
enough: Whenever we
On 9/19/19 10:46 AM, Ben Greear wrote:
On 9/19/19 10:44 AM, Peter Oh wrote:
On 9/19/19 5:22 AM, Toke Høiland-Jørgensen wrote:
From: Toke Høiland-Jørgensen
This patch ports that idea over to mac80211. The basic idea is simple
enough: Whenever we dequeue a packet from the TXQs and send it to
On 9/19/19 5:22 AM, Toke Høiland-Jørgensen wrote:
From: Toke Høiland-Jørgensen
This patch ports that idea over to mac80211. The basic idea is simple
enough: Whenever we dequeue a packet from the TXQs and send it to the
driver, we estimate its airtime usage, based on the last recorded TX rate
of
On Wed, Sep 11, 2019 at 12:59 AM Aaron Komisar
wrote:
>
> In non-ETSI reg domains scan is blocked when operating channel is a DFS ch.
> For ETSI domains, however, once DFS channel is marked as available afer
> the CAC, this channel will remain available even after leaving this channel.
> Therefore
From: Peter Oh
Update power limit as documented in:
http://www.law.go.kr/%ED%96%89%EC%A0%95%EA%B7%9C%EC%B9%99/
%EC%8B%A0%EA%B3%A0%ED%95%98%EC%A7%80%EC%95%84%EB%8B%88%ED
%95%98%EA%B3%A0%EA%B0%9C%EC%84%A4%ED%95%A0%EC%88%98%EC%9E
%88%EB%8A%94%EB%AC%B4%EC%84%A0%EA%B5%AD%EC%9A%A9%EB%AC%B4
%EC%84%A0
On 05/15/2019 09:21 AM, Seth Forshee wrote:
> You dropped Peter and the linux-wireless list from your reply, adding
> them back.
>
> On Thu, May 16, 2019 at 12:10:16AM +0900, suchan wrote:
>> 2019-05-15 10:03PM at Seth Forshee wrote:
>>> Is there any mention of transmit power control in the docum
From: Peter Oh
Update power limit as documented in:
http://www.law.go.kr/%ED%96%89%EC%A0%95%EA%B7%9C%EC%B9%99/
%EC%8B%A0%EA%B3%A0%ED%95%98%EC%A7%80%EC%95%84%EB%8B%88%ED
%95%98%EA%B3%A0%EA%B0%9C%EC%84%A4%ED%95%A0%EC%88%98%EC%9E
%88%EB%8A%94%EB%AC%B4%EC%84%A0%EA%B5%AD%EC%9A%A9%EB%AC%B4
%EC%84%A0
On 04/25/2019 01:37 PM, b.k.il.h.u+tig...@gmail.com wrote:
> Note that a link to the 2016-124 document is specified as reference in
> the above code (conversion also attached), not to 2016-125. Should we
> update the link? Although some of the numbers seem to match, the
> documents differ in stru
On 04/08/2019 05:41 AM, Seth Forshee wrote:
> On Wed, Mar 27, 2019 at 06:34:29PM +0000, Peter Oh wrote:
>> From: Peter Oh
>>
>> Update power limit as documented in:
>> https://www.rra.go.kr/FileDownSvl?file_type=LAWKR&file_parentseq=54&file_seq=27
&g
From: Peter Oh
Update power limit as documented in:
https://www.rra.go.kr/FileDownSvl?file_type=LAWKR&file_parentseq=54&file_seq=27
which revised on November 30, 2016.
Signed-off-by: Peter Oh
---
db.txt | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/
On 03/19/2019 12:59 PM, Tomislav Požega wrote:
> On some systems there are heavy crashes if the kernel config
> option CONFIG_PCIEASPM_PERFORMANCE is not set. Patch provided by
> Sujith for ath9k fixes
ath10k?
Peter
On 12/10/2018 08:56 PM, Pradeep Kumar Chitrapu wrote:
> From: Pradeep kumar Chitrapu
>
> Invalid rate code is sent to firmware when multicast rate value of 0 is
> sent to driver indicating disabled case, causing broken mesh path.
> so fix that.
>
> Tested on QCA9984 with firmware 10.4-3.6.1-0082
On 10/14/2018 10:07 PM, Tamizh chelvam wrote:
> Many number of false radar detection occurred in a noisy
> environment in QCA4019, QCA9888 devices. By reducing
> PRI_TOLERANCE to 6 and flushing out pulse queue by dpd_reset
> if timestamp between current and previous pulse is lesser than
> 100ms h
On 09/28/2018 12:10 PM, Peter Oh wrote:
>
> On 09/24/2018 12:10 AM, Anilkumar Kolli wrote:
>> diff --git a/drivers/net/wireless/ath/ath10k/htt_rx.c
>> b/drivers/net/wireless/ath/ath10k/htt_rx.c
>> index f2405258a6d3..355c39a0486c 100644
>> --- a/drivers/net/wireles
On 09/24/2018 12:10 AM, Anilkumar Kolli wrote:
> diff --git a/drivers/net/wireless/ath/ath10k/htt_rx.c
> b/drivers/net/wireless/ath/ath10k/htt_rx.c
> index f2405258a6d3..355c39a0486c 100644
> --- a/drivers/net/wireless/ath/ath10k/htt_rx.c
> +++ b/drivers/net/wireless/ath/ath10k/htt_rx.c
> @@ -27
On 08/31/2018 01:31 AM, Luca Coelho wrote:
)
From: Andrei Otcheretianski
Otherwise the offchannel frame might be queued due to
IEEE80211_QUEUE_STOP_REASON_PS and later dropped (in
ieee80211_tx_frags()). Anyway, it doesn't make much sense to wake up
the device during ROC.
Signed-off-by: An
From: Peter Oh
NL80211_ATTR_OFFCHANNEL_TX_OK does not mean given channel is always
off channel, but it means the channel given could be off channel.
Hence it should not block the given channel to be used if given
channel does not require off channel mgmt tx although regulatory
domain is non-ETSI
On 07/03/2018 05:47 AM, Johannes Berg wrote:
From: Johannes Berg
Since (QoS) NDP frames shouldn't be put into aggregation nor are
assigned real sequence numbers, etc. it's better to treat them as
non-data packets and not put them on the normal TXQs, for example
when building A-MPDUs they nee
+ /* Even in case of radar detection failure we follow the same
+* behaviour as if radar is detected i.e to switch to a different
+* channel.
+*/
+ if (status_arg.status == WMI_HW_RADAR_DETECTED ||
+ status_arg.status == WMI_RADAR_DETECTION_FAIL)
+
Sure, every software change can cause regressions. But the thing is that
this isn't an optional, ath10k has to have this to be able to continue
using DFS channels.
Kalle, you said you don't know which exact FCC requirement this is for
in another email thread.
Then how come you're sure this is
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.
Th
On 05/07/2018 01:06 PM, Johannes Berg wrote:
On Mon, 2018-05-07 at 13:04 -0700, Peter Oh wrote:
On 05/07/2018 12:44 PM, Johannes Berg wrote:
On Fri, 2018-04-27 at 12:26 -0700, peter...@bowerswilkins.com wrote:
From: Peter Oh
There is no meaning to call ieee80211_mesh_process_chnswitch
On 05/07/2018 12:44 PM, Johannes Berg wrote:
On Fri, 2018-04-27 at 12:26 -0700, peter...@bowerswilkins.com wrote:
From: Peter Oh
There is no meaning to call ieee80211_mesh_process_chnswitch
without CSA IE provided, since the function will always return error.
I'm not convinced, an ext
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 WMI_SERVICE_HOST_DFS_CHECK_SUPPORT flag.
This new features enables the ath10k ho
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 WMI_SERVICE_HOST_DFS_CHECK_SUPPORT flag.
This new features enables the ath10k host to send information to the
firmware on the specifications of detected
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 implementation.
For example, collected radar info could be used by th
From: Peter Oh
There is no meaning to call ieee80211_mesh_process_chnswitch
without CSA IE provided, since the function will always return error.
Signed-off-by: Peter Oh
---
net/mac80211/mesh.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/mac80211/mesh.c b/net
where is the 9th patch gone?
On 04/20/2018 03:49 AM, Luca Coelho wrote:
From: Ilan Peer
There are specific cases, such as SAE authentication exchange, that
might require long duration to complete. For such cases, add support
for indicating to the driver the required duration of the prepare_tx
On 04/13/2018 06:48 AM, Kalle Valo wrote:
Sven Eckelmann writes:
But of course, I cannot say much about how the rate control from QCA works and
in which form these information are already available.
If you want to know the average PHY rate then wouldn't it be better to report
the rates to o
Hi Anilkumar,
On 03/27/2018 11:37 PM, Sven Eckelmann wrote:
On Mittwoch, 28. März 2018 11:41:51 CEST ako...@codeaurora.org wrote:
[...]
The rate average and throughput are relative. no?
Can you share the output number from your new function?
It may help us to understand a little bit more how
+ if (sdata->vif.type == NL80211_IFTYPE_AP)
+ wmm_ac = &rrule->wmm_rule->ap[ac];
+ else
+ wmm_ac = &rrule->wmm_rule->client[ac];
+ qparam->cw_min = max_t(u16, qparam->cw_min, wmm_ac->cw_min);
+ qparam->cw_max = max_t(u16, qparam->cw_max, wmm_ac
Add QMI client driver for Q6 integrated WLAN connectivity subsystem.
Can you give an example which chipset series is Q6 integrated WLAN ?
Thanks,
Peter
From: Sathishkumar Muruganandam
This patch adds support for WMI_FWTEST_CMD.
This command is used for setting the wifi parameters.
It's too lack of information in commit message.
You should add such what values are acceptable for which purpose by each
param_id and param_value to make this chan
This reverts commit 55884c045d31a29cf69db8332d1064a1b61dd159.
When Ath10k is in AP mode and an unassociated STA sends a VHT action frame
(Operating Mode Notification for the NSS change) periodically to AP this causes
ath10k to call ath10k_station_assoc() which sends WMI_PEER_ASSOC_CMDID during
next-20180126]
[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/peter-oh-bowerswilkins-com/mac80211-mesh-fix-wrong-mesh-TTL-offset-calculation/20180128-042444
base: https://git.kernel.org/pub/scm
From: Peter Oh
mesh TTL offset in Mesh Channel Switch Parameters element depends on
not only Secondary Channel Offset element, but also affected by
HT Control field and Wide Bandwidth Channel Switch element.
So use element structure to manipulate mesh channel swich param IE
after removing its
Ignore the patch below for now. Just noticed mesh_chansw_params_ie is
constance.
will come up with new approach.
Thanks,
Peter
On 01/24/2018 05:16 PM, peter...@bowerswilkins.com wrote:
From: Peter Oh
mesh TTL offset in Mesh Channel Switch Parameters element depends on
not only Secondary
From: Peter Oh
mesh TTL offset in Mesh Channel Switch Parameters element depends on
not only Secondary Channel Offset element, but also affected by
HT Control field and Wide Bandwidth Channel Switch element.
Use element structure to correct the miscalculation.
Signed-off-by: Peter Oh
---
net
From: Peter Oh
mesh TTL offset in Mesh Channel Switch Parameters element depends on
not only Secondary Channel Offset element, but also affected by
HT Control field and Wide Bandwidth Channel Switch element.
Hence take those values place in.
Signed-off-by: Peter Oh
---
net/mac80211/mesh.c
From: Peter Oh
mesh TTL offset in Mesh Channel Switch Parameters element depends on
not only Secondary Channel Offset element, but also affected by
HT Control field and Wide Bandwidth Channel Switch element.
Hence take those values place in.
Signed-off-by: Peter Oh
---
net/mac80211/mesh.c
Hi Rajkumar,
I'm wondering if this patch is related to kernel crash due to ath10k napi.
Do you think this patch helps the crash below?
This crash happened ath10k v4.14 (10/04/2017, commit id c09dbd7) +
3.14.43 kernel backports.
[ 6866.655419] [ cut here ]
[ 6866.6590
On 11/06/2017 01:02 AM, Sven Eckelmann wrote:
On Montag, 6. November 2017 09:28:42 CET Sebastian Gottschall wrote:
Am 06.11.2017 um 09:23 schrieb Sven Eckelmann:
On Sonntag, 5. November 2017 10:22:22 CET Sebastian Gottschall wrote:
the assumption made in this patch is obviously wrong (at lea
On 10/15/2017 11:00 PM, yint...@qti.qualcomm.com wrote:
From: Yingying Tang
This patchset is for Rome PCIE chip, it will not affect other hardware
Please add your patchset history here until V6.
That's what cover letter is supposed to have.
Yingying Tang (5):
mac80211: Enable TDLS peer b
On 06/28/2017 01:16 PM, Arend van Spriel wrote:
On 28-06-17 00:07, peter...@bowerswilkins.com wrote:
From: Peter Oh
Update Public Action field values as updated in IEEE Std 802.11-2016,
so that modules/drivers can refer it.
Hi Peter,
I am pretty sure there are a lot of other definitions
From: Peter Oh
Update Public Action field values as updated in IEEE Std 802.11-2016,
so that modules/drivers can refer it.
Signed-off-by: Peter Oh
---
include/linux/ieee80211.h | 35 ++-
1 file changed, 34 insertions(+), 1 deletion(-)
diff --git a/include
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 pa
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
--- a/drivers/net/wireless
where is 2/3 ?
On 06/20/2016 06:00 AM, Maxim Altshul wrote:
> Hi All,
> This patch series focuses on metric calculation that
> occurs during the path selection phase of a mesh network.
>
> During the path selection phase, the mesh hwmp module
> performs metric calculations, that take as parameters
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
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
---
drivers/net/wireless/ath/ath10k
Update 10.4 WMI vdev param to sync to current 10.4 firmware
as of 2/23/2016.
Signed-off-by: Peter Oh
---
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/wireless/ath/ath10k/wmi.h
index 8225d90
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
---
drivers/net/wireless/ath/ath10k/wmi.c | 2 +-
1 file changed, 1 insertion(+), 1
://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 the
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
On 02/29/2016 10:33 AM, Michal Kazior wrote:
On 26 February 2016 at 20:03, Peter Oh 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 clockdrift
or beacon collision and
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
---
v2:
- fix kbuild
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
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
---
v2:
- fix kbuild
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
---
v2:
- fix
Thank you!
On 02/25/2016 11:32 AM, Sven Eckelmann wrote:
On Thursday 25 February 2016 10:53:23 Peter Oh wrote:
I see new warnings:
drivers/net/wireless/ath/ath10k/wmi.c:2199:16: warning: restricted
__le32
degrades to integer
drivers/net/wireless/ath/ath10k/wmi.c:2201:41: warning: restricted
Hi,
On 02/25/2016 08:34 AM, Valo, Kalle wrote:
Peter Oh 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 and use the result for beacon
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
---
v2:
- fix
On 02/24/2016 12:40 AM, Michal Kazior wrote:
On 23 February 2016 at 20:44, Peter Oh wrote:
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
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: poh
---
v2:
-
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: poh
---
drivers/net/w
On 02/03/2016 12:18 PM, Neelansh Mittal wrote:
Currently, for a mesh node ,the mac80211
sync implementation sets the tbtt
adjustment bit , when it is adjusting it's
tsf as part of Neighbour offset
Synchronization(Function:mesh_sync_offset_
adjust_tbtt())
According to ieee80211s specification,
th
Update 10.4 WMI service map to sync to the latest 10.4 firmware
as of 1/20/2016.
Signed-off-by: Peter Oh
---
drivers/net/wireless/ath/ath10k/wmi.h | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/net/wireless/ath/ath10k/wmi.h
b/drivers/net/wireless/ath/ath10k/wmi.h
.
Hence use the abstraction API to get right subtype to use.
Signed-off-by: Peter Oh
---
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/wireless/ath/ath10k/wmi.c | 70
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
---
drivers/net/wireless/ath/
-off-by: Peter Oh
---
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/mac.c
index ef0438d..1406b0f
code changes.
Peter Oh (4):
ath10k: rename Mesh related service names
ath10k: update 10.4 WMI service map
ath10k: use vif->type and vif->p2p for P2P_GO check
ath10k: add abstraction layer for vdev subtype
drivers/net/wireless/ath/ath10k/mac.c | 25 +--
drivers/net/wirele
On 01/27/2016 06:04 PM, Yeoh Chun-Yeow wrote:
On Thu, Jan 28, 2016 at 5:53 AM, Peter Oh wrote:
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
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
On 01/27/2016 11:11 AM, Ben Greear wrote:
On 01/27/2016 10:55 AM, Peter Oh wrote:
Abstraction layer for vdev subtype is added to solve
subtype mismatch and to give flexible compatibility
among different firmware revisions.
For instance, 10.2 and 10.4 firmware has different
definition of their
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
-off-by: Peter Oh
---
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/mac.c
index 6146a29..6bf5c91
Update 10.4 WMI service map to sync to the latest 10.4 firmware
as of 1/20/2016.
Signed-off-by: Peter Oh
---
drivers/net/wireless/ath/ath10k/wmi.h | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/net/wireless/ath/ath10k/wmi.h
b/drivers/net/wireless/ath/ath10k/wmi.h
.
Hence use the abstraction API to get right subtype to use.
Signed-off-by: Peter Oh
---
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/wireless/ath/ath10k/wmi.c | 70
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
---
drivers/net/wireless/ath/
On 01/26/2016 02:28 AM, Michal Kazior wrote:
On 22 January 2016 at 08:47, Michal Kazior wrote:
On 21 January 2016 at 18:40, Peter Oh wrote:
On 01/21/2016 05:46 AM, Michal Kazior wrote:
[...]
- /* TODO: apply configuration */
+ rcu_read_unlock();
+
+ spin_lock_bh(&am
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
over
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
---
drivers/net/wireless/ath/ath10k/mac.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath
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
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
On 12/16/2015 11:29 PM, Michal Kazior wrote:
On 17 December 2015 at 00:50, Peter Oh wrote:
On 12/16/2015 01:54 PM, Felix Fietkau wrote:
On 2015-12-16 22:19, Peter Oh wrote:
[...]
If mentioned to use the function to mesh frame only without touching
mac80211, then how do you suggest it to
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
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
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
suitabl
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 che
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
---
dr
y one
supporting secured Mesh at this moment.
Signed-off-by: Peter Oh
---
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..b4bdeb0 100644
--- a/driver
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) withou
I believe the robot report is false.
Am I right?
Thanks,
Peter
On 11/24/2015 01:19 PM, kbuild test robot wrote:
Hi Peter,
[auto build test WARNING on net-next/master]
[also build test WARNING on v4.4-rc2 next-20151124]
url:
https://github.com/0day-ci/linux/commits/Peter-Oh/ath10k-introduce
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
---
drivers/net/wireless/ath/ath10k/wmi.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/wireless/ath/ath10k/wmi.h
b
received via the interface, once Mesh
subtype is used.
The firmware and this patch together make native Wi-Fi mode comply to
IEEE802.11s Mesh frame in open mode, but the firmware doesn't yet
support secured Mesh mode.
Signed-off-by: Peter Oh
---
drivers/net/wireless/ath/ath10k/mac.c | 4 ++
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
---
drivers/net/wireless/ath/ath10k/wmi.h | 15 +++
1 file changed, 15 insertions(+)
diff --git a/drivers/net
QCA988X firmware has started supporting Mesh frame in native Wi-Fi mode
by adding its subtype since 10.2.4.70.12-2.
Hence update its WMI service map and vdev subtypes to be used for Mesh in
native Wi-Fi mode.
Peter Oh (3):
ath10k: update WMI 10.x service map
ath10k: introduce new subtypes for
The error message order of board data fetch is board info,
directory, and then file name, hence place print arguments
in the order.
Fixes: 0a51b343abfe ("ath10k: add board 2 API support")
Signed-off-by: Peter Oh
---
drivers/net/wireless/ath/ath10k/core.c | 2 +-
1 file changed, 1
1 - 100 of 176 matches
Mail list logo
