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 <maxim.alts...@ti.com>
---
Removed ret and NULL test.
drivers/net/wireless/ti/wlcore/main.c | 11
-off-by: Maxim Altshul <maxim.alts...@ti.com>
---
Changed the function to return u32, I agree that this
is much clearer.
As for the rate, two things:
1. I had to divide the returned value by 100, since
drv_get_expected_throughput returns values in units of Kbps.
On the contrary, the fu
-off-by: Maxim Altshul <maxim.alts...@ti.com>
---
net/mac80211/mesh_hwmp.c | 23 +++
1 file changed, 15 insertions(+), 8 deletions(-)
diff --git a/net/mac80211/mesh_hwmp.c b/net/mac80211/mesh_hwmp.c
index c6be0b4..e3ce40d 100644
--- a/net/mac80211/mesh_hwmp.c
+++ b/net/ma
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 <maxim.alts...@ti.com>
---
drivers/net/wireless/ti/wlcore/main.c | 15 +++
1 file chang
FW will provide a TX rate per link for each FW status,
and wlcore will be able to store the information for
the use of the mesh hwmp module.
This is used mainly in mesh.
Rates are reported when a mesh interface is up.
Signed-off-by: Maxim Altshul <maxim.alts...@ti.com>
---
drivers/net/wi
to the mesh hwmp module by using an existing op called
get_expected_throughput.
In case that a vendor does not implement the op, all previous
functionality still applies.
2. Implements the opcode and the mechanism that reports the rates
in TI driver.
Maxim Altshul (3):
wlcore/wl18xx: Add functionality
