* [PATCH 00/40] rt2x00 patches form OpenWrt.org
From: Daniel Golle @ 2017-01-13 21:18 UTC (permalink / raw)
To: linux-wireless
Cc: Johannes Berg, Stanislaw Gruszka, roman, michel.stempin,
c.mignanti, evaxige, Kalle Valo, Felix Fietkau, John Crispin,
Gabor Juhos
Some of these are fixes, most importantly Serge Vasilugin fixed setting
the HT20/HT40 filter which got us much closer to the expected
performance when using HT40 modes.
There is also a lot of new hardware support added:
Gabor Juhos wrote code for the Rt3883 WiSoC.
Daniel Golle implemented support for Rt3352 boards with external PA as
well as for boards using a 20MHz crystal instead of the usual 40MHz.
Serge Vasilugin contributed support for the Rt5350 WiSoC.
Michel Stempin, Felix Fietkau and John Crispin have been helping with
cleaning up things and putting away legal doubts.
Claudio Mignanti (1):
rt2x00: rt2x00pci: set PCI MWI only if supported
Daniel Golle (2):
rt2x00: support for for RT3352 with external PA
rt2x00: add support for RT3352 with 20MHz crystal
Felix Fietkau (1):
rt2x00: fix rf id for RT3352
Gabor Juhos (34):
rt2x00: rt2800lib: move rt2800_drv_data declaration into rt2800lib.h
rt2x00: rt2800lib: introduce RT2800_HAS_HIGH_SHARED_MEM flag
rt2x00: rt2800: serialize shared memory access
rt2x00: rt2800lib: fix beacon generation on RT3593
rt2x00: rt2800lib: add hw_beacon_count field to struct rt2800_drv_data
rt2x00: rt2800lib: init additional beacon offset registers
rt2x00: rt2800lib: fix max supported beacon count for RT3593
rt2x00: allow to build rt2800soc module for RT3883
rt2x00: rt2800lib: enable support for RT3883
rt2x00: rt2800lib: add rf_vals for RF3853
rt2x00: rt2800lib: enable VCO calibration for RF3853
rt2x00: rt2800lib: add channel configuration function for RF3853
rt2x00: rt2800lib: enable RF3853 support
rt2x00: rt2800lib: add MAC register initialization for RT3883
rt2x00: rt2800soc: fix rt2800soc_disable_radio for RT3883
rt2x00: rt2800lib: add BBP register initialization for RT3883
rt2x00: rt2800lib: add RFCSR initialization for RT3883
rt2x00: rt2800lib: use the extended EEPROM map for RT3883
rt2x00: rt2800lib: force rf type to RF3853 on RT3883
rt2x00: rt2800lib: add channel configuration code for RT3883
rt2x00: rt2800lib: fix txpower_to_dev function for RT3883
rt2x00: rt2800lib: use correct txpower calculation function for RT3883
rt2x00: rt2800lib: hardcode txmixer gain values to zero for RT3883
rt2x00: rt2800lib: use correct [RT]XWI size for RT3883
rt2x00: rt2800lib: use correct beacon base for RT3883
rt2x00: rt2800lib: use correct beacon count for RT3883
rt2x00: rt2800lib: fix antenna configuration for RT3883
rt2x00: rt2800lib: fix LNA gain configuration for RT3883
rt2x00: rt2800lib: fix VGC setup for RT3883
rt2x00: rt2800lib: fix EEPROM LNA validation for RT3883
rt2x00: rt2800lib: fix txpower compensation for RT3883
rt2x00: rt2800lib: enable RT2800_HAS_HIGH_SHARED_MEM for RT3883
rt2x00: rt2800lib: use high memory for beacons on RT3883
rt2x00: rt2800mmio: add a workaround for spurious TX_FIFO_STATUS
interrupts
Michel Stempin (1):
rt2x00: add support for RT5350 WiSoC
Serge Vasilugin (1):
rt2x00: correctly set HT20/HT40 filter
drivers/net/wireless/ralink/rt2x00/Kconfig | 2 +-
drivers/net/wireless/ralink/rt2x00/rt2800.h | 77 +-
drivers/net/wireless/ralink/rt2x00/rt2800lib.c | 1013 ++++++++++++++++++++++-
drivers/net/wireless/ralink/rt2x00/rt2800lib.h | 65 ++
drivers/net/wireless/ralink/rt2x00/rt2800mmio.c | 98 ++-
drivers/net/wireless/ralink/rt2x00/rt2800mmio.h | 4 +
drivers/net/wireless/ralink/rt2x00/rt2800pci.c | 14 +
drivers/net/wireless/ralink/rt2x00/rt2800soc.c | 12 +-
drivers/net/wireless/ralink/rt2x00/rt2800usb.c | 31 +
drivers/net/wireless/ralink/rt2x00/rt2x00.h | 10 +
drivers/net/wireless/ralink/rt2x00/rt2x00pci.c | 2 +
11 files changed, 1254 insertions(+), 74 deletions(-)
--
2.11.0
^ permalink raw reply
* ANNOUNCE: Netdev 2.1 in Montreal
From: Jamal Hadi Salim @ 2017-01-13 19:58 UTC (permalink / raw)
To: netdev
Cc: netfilter-devel, netfilter, info, linux-wireless, tech-committee,
David Miller, Stephen Jaworski, Rob Echlin, lwn
Folks,
We are pleased to announce Netdev 2.1 (year 2, conference 1)
in the beautiful city of Montreal, Canada on the 6th to 8th of April.
The website is now online: http://www.netdevconf.org/2.1/
Netdev 2.1 will be held back to back with netconf2017.1
(http://vger.kernel.org/netconf2017.html)
Netdev 2.1 is a community-driven conference geared towards Linux
netheads. Linux kernel networking and user space utilization of the
interfaces to the Linux kernel networking subsystem are the central
theme.
If you are using Linux as a boot system for proprietary networking,
then this conference _may not be for you_.
Registration costs
------------------
Very Cheap.
$CAN 300 if you register before Feb 27. $360 after.
$CAN 150 if you are a student. $180 after Feb 27
Why you should register
-----------------------
If you yearn for the old community tech driven conferences where
you mingle with fellow geeks (only these would be Linux networking
geeks) then this would be it. There will be no marketing flashing
light openings or loud bad music. Just a pure feed of Linux
networking. Gurus and magicians of all sorts will be there mingling,
juggling and giving talks.
While there will be heavy Linux kernel influence we expect a lot
of user space presence as well.
Exact Location:
-----------------
Tentative: LE WESTIN MONTRÉAL
Sponsorship
------------
If you can help us organize this event by sponsoring, please drop us a
line to: sponsor@netdevconf.org and we'll send you our sponsorship policy.
Important dates
----------------
January 18, 2017 Call for proposals open
January 23, 2017 Registration opens
February 20, 2017 Call for proposals close
February 27, 2017 Early Registration close
March 13, 2017 Conference schedule announced
March 27, 2017 Paper submission
March 31, 2017 Online Registration close
April 3, 2017 Slides submission
April 6-8, 2017 Conference days
May 1, 2017 Slides release
June 1, 2017 Paper release
cheers,
jamal
^ permalink raw reply
* Re: [RFC] [PULL REQUEST] rt2x00 patches from OpenWrt.org
From: Daniel Golle @ 2017-01-13 16:17 UTC (permalink / raw)
To: Johannes Berg
Cc: Kalle Valo, linux-wireless, lede-dev, openwrt-devel, john, nbd,
roman, evaxige, c.mignanti, michel.stempin, vasilugin,
Stanislaw Gruszka, Helmut Schaa
In-Reply-To: <1484323199.8670.5.camel@sipsolutions.net>
On Fri, Jan 13, 2017 at 04:59:59PM +0100, Johannes Berg wrote:
>
> > The advantage of pull requests is that author information can be
> > preserved more easily. Running git format-patch results in most
> > patches
> > having wrong SMTP sender information due to the assumption that the
> > patch author is the same person also submitting the patch.
> > So in practise, this would either require changing the From: (and
> > thus
> > Author) to myself or having most mails eaten by anti-spam measures
> > due
> > to non-matching SPF which prohibits my SMTP to send mail on behalf of
> > the original authors of the patches.
> >
>
> This is completely untrue. If the first line of the *body* of the email
> is "From: ..." then this is preserved as the author information by git
> am, and doing so is also the default in git format-patch/send-email
> when the author doesn't match the email configuration.
Thanks for the clarification, I'll then submit the patches via
git format-patch.
Cheers
Daniel
^ permalink raw reply
* Re: [RFC] [PULL REQUEST] rt2x00 patches from OpenWrt.org
From: Johannes Berg @ 2017-01-13 15:59 UTC (permalink / raw)
To: Daniel Golle, Kalle Valo
Cc: linux-wireless, lede-dev, openwrt-devel, john, nbd, roman,
evaxige, c.mignanti, michel.stempin, vasilugin, Stanislaw Gruszka,
Helmut Schaa
In-Reply-To: <20170113154629.GG2332@makrotopia.org>
> The advantage of pull requests is that author information can be
> preserved more easily. Running git format-patch results in most
> patches
> having wrong SMTP sender information due to the assumption that the
> patch author is the same person also submitting the patch.
> So in practise, this would either require changing the From: (and
> thus
> Author) to myself or having most mails eaten by anti-spam measures
> due
> to non-matching SPF which prohibits my SMTP to send mail on behalf of
> the original authors of the patches.
>
This is completely untrue. If the first line of the *body* of the email
is "From: ..." then this is preserved as the author information by git
am, and doing so is also the default in git format-patch/send-email
when the author doesn't match the email configuration.
johannes
^ permalink raw reply
* Re: [PATCH] rtlwifi: rtl8192ee: New firmware from Realtek
From: Larry Finger @ 2017-01-13 15:57 UTC (permalink / raw)
To: Kyle McMartin; +Cc: linux-wireless, Troy Tan, netdev, linux-firmware
In-Reply-To: <20170113150306.GE13400@bombadil.infradead.org>
On 01/13/2017 09:03 AM, Kyle McMartin wrote:
> On Sat, Dec 17, 2016 at 12:50:54PM -0600, Larry Finger wrote:
>> -Info: Taken from Realtek version rtl_92ce_92se_92de_8723ae_88ee_8723be_92ee_linux_mac80211_0017.1224.2013
>> +Info: Initial version taken from Realtek version
>> + rtl_92ce_92se_92de_8723ae_88ee_8723be_92ee_linux_mac80211_0017.1224.2013
>> + Updated Jan. 14, 2015 with file added by Realtek to
>> + http://github.com/lwfinger/rtlwifi_new.git.
>> File: rtlwifi/rtl8192eefw.bin
>>
>
> Uh, did something weird happen here? This patch was applied in 2015. ;-)
>
> cheers, Kyle
Realtek fixed some bugs in the firmware. This is a new version.
Larry
^ permalink raw reply
* Re: [RFC] [PULL REQUEST] rt2x00 patches from OpenWrt.org
From: Daniel Golle @ 2017-01-13 15:46 UTC (permalink / raw)
To: Kalle Valo
Cc: linux-wireless, lede-dev, openwrt-devel, john, nbd, roman,
evaxige, c.mignanti, michel.stempin, vasilugin, Stanislaw Gruszka,
Helmut Schaa
In-Reply-To: <87tw93i6e7.fsf@purkki.adurom.net>
Hi Kalle,
On Fri, Jan 13, 2017 at 12:46:56PM +0200, Kalle Valo wrote:
> Daniel Golle <daniel@makrotopia.org> writes:
> > ...
> > Please review and comment, so we can get those patches merged!
>
> No pull requests, please. Instead send these as patches, easier to
> review and actually also easier for me to merge.
The advantage of pull requests is that author information can be
preserved more easily. Running git format-patch results in most patches
having wrong SMTP sender information due to the assumption that the
patch author is the same person also submitting the patch.
So in practise, this would either require changing the From: (and thus
Author) to myself or having most mails eaten by anti-spam measures due
to non-matching SPF which prohibits my SMTP to send mail on behalf of
the original authors of the patches.
How do you suggest to handle this situation?
Cheers
Daniel
^ permalink raw reply
* [PATCH] mwifiex: fix uninitialized variable access in pcie_remove
From: Arnd Bergmann @ 2017-01-13 15:35 UTC (permalink / raw)
To: Amitkumar Karwar, Kalle Valo
Cc: Arnd Bergmann, Nishant Sarmukadam, Brian Norris, Xinming Hu,
Cathy Luo, Shengzhen Li, linux-wireless, netdev, linux-kernel
Checking the firmware status from PCIe register only works
if the register is available, otherwise we end up with
random behavior:
drivers/net/wireless/marvell/mwifiex/pcie.c: In function 'mwifiex_pcie_remove':
drivers/net/wireless/marvell/mwifiex/pcie.c:585:5: error: 'fw_status' may be used uninitialized in this function [-Werror=maybe-uninitialized]
This makes sure we treat the absence of the register as a failure.
Fixes: 045f0c1b5e26 ("mwifiex: get rid of global user_rmmod flag")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
drivers/net/wireless/marvell/mwifiex/pcie.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/wireless/marvell/mwifiex/pcie.c b/drivers/net/wireless/marvell/mwifiex/pcie.c
index 031141663fc0..eebc68caecdd 100644
--- a/drivers/net/wireless/marvell/mwifiex/pcie.c
+++ b/drivers/net/wireless/marvell/mwifiex/pcie.c
@@ -581,6 +581,8 @@ static void mwifiex_pcie_remove(struct pci_dev *pdev)
reg = card->pcie.reg;
if (reg)
ret = mwifiex_read_reg(adapter, reg->fw_status, &fw_status);
+ else
+ fw_status = -1;
if (fw_status == FIRMWARE_READY_PCIE && !adapter->mfg_mode) {
mwifiex_deauthenticate_all(adapter);
--
2.9.0
^ permalink raw reply related
* Re: [PATCH] linux-firmware: mwlwifi: update 88W8864 firmware.
From: Kyle McMartin @ 2017-01-13 15:04 UTC (permalink / raw)
To: David Lin
Cc: Ben Hutchings, linux-wireless@vger.kernel.org, Chor Teck Law,
James Lin, Pete Hsieh, linux-firmware
In-Reply-To: <8dd5581553b448f3911604f9c5d0f3c8@SC-EXCH02.marvell.com>
On Wed, Dec 21, 2016 at 06:53:19AM +0000, David Lin wrote:
> Release Version: 7.2.9.26.
>
> Signed-off-by: David Lin <dlin@marvell.com>
> ---
> mwlwifi/88W8864.bin | Bin 116356 -> 118776 bytes
> 1 file changed, 0 insertions(+), 0 deletions(-)
>
Please include an update for WHENCE.
regards, Kyle
^ permalink raw reply
* Re: [PATCH] rtlwifi: rtl8192ee: New firmware from Realtek
From: Kyle McMartin @ 2017-01-13 15:03 UTC (permalink / raw)
To: Larry Finger; +Cc: linux-wireless, Troy Tan, netdev, linux-firmware
In-Reply-To: <20161217185054.15017-1-Larry.Finger@lwfinger.net>
On Sat, Dec 17, 2016 at 12:50:54PM -0600, Larry Finger wrote:
> -Info: Taken from Realtek version rtl_92ce_92se_92de_8723ae_88ee_8723be_92ee_linux_mac80211_0017.1224.2013
> +Info: Initial version taken from Realtek version
> + rtl_92ce_92se_92de_8723ae_88ee_8723be_92ee_linux_mac80211_0017.1224.2013
> + Updated Jan. 14, 2015 with file added by Realtek to
> + http://github.com/lwfinger/rtlwifi_new.git.
> File: rtlwifi/rtl8192eefw.bin
>
Uh, did something weird happen here? This patch was applied in 2015. ;-)
cheers, Kyle
^ permalink raw reply
* [PATCH] rt2800: remove warning on bcn_num != rt2x00dev->intf_beaconing
From: Stanislaw Gruszka @ 2017-01-13 14:55 UTC (permalink / raw)
To: linux-wireless; +Cc: Helmut Schaa, Daniel Golle
Since rt2800pci update beacon settings asynchronously from
tbtt tasklet, without beacon_skb_mutex protection, number of
currently active beacons entries can be different than
number pointed by rt2x00dev->intf_beaconing. Remove warning
about that inconsistency.
Reported-by: evaxige@qq.com
Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
---
drivers/net/wireless/ralink/rt2x00/rt2800lib.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/net/wireless/ralink/rt2x00/rt2800lib.c b/drivers/net/wireless/ralink/rt2x00/rt2800lib.c
index 4fb79e0..1abe38f 100644
--- a/drivers/net/wireless/ralink/rt2x00/rt2800lib.c
+++ b/drivers/net/wireless/ralink/rt2x00/rt2800lib.c
@@ -967,8 +967,6 @@ static void rt2800_update_beacons_setup(struct rt2x00_dev *rt2x00dev)
bcn_num++;
}
- WARN_ON_ONCE(bcn_num != rt2x00dev->intf_beaconing);
-
rt2800_register_write(rt2x00dev, BCN_OFFSET0, (u32) reg);
rt2800_register_write(rt2x00dev, BCN_OFFSET1, (u32) (reg >> 32));
--
1.8.3.1
^ permalink raw reply related
* Re: [PATCH 1/2] brcm: add firmware for the BCM4356 SDIO device
From: Kyle McMartin @ 2017-01-13 14:57 UTC (permalink / raw)
To: Arend van Spriel; +Cc: linux-wireless, linux-firmware
In-Reply-To: <1482092196-10227-1-git-send-email-arend.vanspriel@broadcom.com>
On Sun, Dec 18, 2016 at 08:16:35PM +0000, Arend van Spriel wrote:
> This patch adds firmware for the BCM4356 2x2 11ac SDIO device.
>
> Reviewed-by: Hante Meuleman <hante.meuleman@broadcom.com>
> Reviewed-by: Pieter-Paul Giesberts <pieter-paul.giesberts@broadcom.com>
> Reviewed-by: Franky Lin <franky.lin@broadcom.com>
> Signed-off-by: Arend van Spriel <arend.vanspriel@broadcom.com>
> Change-Id: I73131f77986c9fc0faf58d316640846897725a14
> Reviewed-on: http://hnd-swgit.sj.broadcom.com:8080/8117
Applied both, thanks Arend.
--Kyle
^ permalink raw reply
* Google Summer of Code 2017 - Project ideas page for the Linux Foundation online
From: Till Kamppeter @ 2017-01-13 14:18 UTC (permalink / raw)
To: Alexey Khoroshilov, Luis R. Rodriguez, Greg KH,
lsb-discuss@lists.linux-foundation.org, linux-wireless,
Open Printing, dl9pf
Hi,
I have set up a page for project ideas for the Linux Foundation's
participation in the Google Summer of Code 2017:
https://wiki.linuxfoundation.org/gsoc/google-summer-code-2017
Please add your ideas to the sub-page of your work group. If you have
problems mail me with your project idea.
From this year on the ideas list is in the Linux Foundation Wiki. AFAIK
it is enough to have a Linux Foundation web site account to be able to
edit and there is no requirement of a special group membership.
Please also take into account that the deadline for our application as
mentoring organization is Feb 9 and after that Google will evaluate the
applications. So have your ideas (at least most of them, ideas can be
posted up to the student application deadline) in by then to raise our
chances to get accepted.
Till
^ permalink raw reply
* Re: [PATCH 1/6] iwlwifi: mvm: don't restart HW if suspend fails with unified image
From: Coelho, Luciano @ 2017-01-13 14:21 UTC (permalink / raw)
To: kvalo@codeaurora.org; +Cc: linux-wireless@vger.kernel.org
In-Reply-To: <87inpjhwu8.fsf@purkki.adurom.net>
T24gRnJpLCAyMDE3LTAxLTEzIGF0IDE2OjEzICswMjAwLCBLYWxsZSBWYWxvIHdyb3RlOg0KPiBM
dWNhIENvZWxobyA8bHVjYUBjb2VsaG8uZmk+IHdyaXRlczoNCj4gDQo+ID4gRnJvbTogTHVjYSBD
b2VsaG8gPGx1Y2lhbm8uY29lbGhvQGludGVsLmNvbT4NCj4gPiANCj4gPiBGb3IgdW5pZmllZCBp
bWFnZXMsIHdlIHNob3VsZG4ndCByZXN0YXJ0IHRoZSBIVyBpZiBzdXNwZW5kIGZhaWxzLiAgVGhl
DQo+ID4gb25seSByZWFzb24gZm9yIHJlc3RhcnRpbmcgdGhlIEhXIHdpdGggbm9uLXVuaWZpZWQg
aW1hZ2VzIGlzIHRvIGdvDQo+ID4gYmFjayB0byB0aGUgRDAgaW1hZ2UuDQo+ID4gDQo+ID4gRml4
ZXM6IGNvbW1pdCAyM2FlNjEyODJiODggKCJpd2x3aWZpOiBtdm06IERvIG5vdCBzd2l0Y2ggdG8g
RDMgaW1hZ2Ugb24gc3VzcGVuZCIpDQo+IA0KPiBzL2NvbW1pdCAvLyA6KQ0KDQpBcmdoLCBkaWQg
SSBkbyBpdCBhZ2Fpbj8gSSB3YXMgc3BlY2lmaWNhbGx5IHRyeWluZyB0byByZW1lbWJlciB0aGlz
LCBidXQNCkkgZ3Vlc3MgaXQgd2FzIG5vdCBlbm91Z2guLi4NCg0KLS0NCkx1Y2Eu
^ permalink raw reply
* Re: [RFC] [PULL REQUEST] rt2x00 patches from OpenWrt.org
From: Stanislaw Gruszka @ 2017-01-13 14:15 UTC (permalink / raw)
To: Daniel Golle
Cc: linux-wireless, lede-dev, openwrt-devel, john, nbd, roman,
evaxige, c.mignanti, michel.stempin, vasilugin, Helmut Schaa
In-Reply-To: <20170113035020.GA9063@makrotopia.org>
Hi
On Fri, Jan 13, 2017 at 04:50:32AM +0100, Daniel Golle wrote:
> Please review and comment, so we can get those patches merged!
As already pointed by Kalle posting patches to mailing list is better
way for review. Posing patches is easy with git-format-patch and
git-send-email. Ideally patch series should not be long, let say no more
than 30 patches - I suggest to split this into two series: second one
for RT3853 support and first one for other patches.
> evaxige (1):
> rt2x00: fix WARN_ON_ONCE() caused by inbalanced set/clear of beacon enable bit
I think I would prefer to remove:
WARN_ON_ONCE(bcn_num != rt2x00dev->intf_beaconing);
line instead of this patch. Other patches looks ok after quick glance.
I think you can post them as normal PATCH in the topic (not as RFC).
Thanks
Stanislaw
^ permalink raw reply
* Re: [PATCH 1/6] iwlwifi: mvm: don't restart HW if suspend fails with unified image
From: Kalle Valo @ 2017-01-13 14:13 UTC (permalink / raw)
To: Luca Coelho; +Cc: linux-wireless, Luca Coelho
In-Reply-To: <20170113123919.30384-2-luca@coelho.fi>
Luca Coelho <luca@coelho.fi> writes:
> From: Luca Coelho <luciano.coelho@intel.com>
>
> For unified images, we shouldn't restart the HW if suspend fails. The
> only reason for restarting the HW with non-unified images is to go
> back to the D0 image.
>
> Fixes: commit 23ae61282b88 ("iwlwifi: mvm: Do not switch to D3 image on suspend")
s/commit // :)
--
Kalle Valo
^ permalink raw reply
* Re: [3/5] ath10k: Remove unused wmi_p2p_noa_descriptor 'noa' in wmi-tlv
From: Kalle Valo @ 2017-01-13 14:01 UTC (permalink / raw)
To: Kirtika Ruchandani
Cc: Arnd Bergmann, netdev, linux-wireless, Raja Mani, Michal Kazior
In-Reply-To: <99d0ff42e57d5f62560e72d926b4d69d5d7c418b.1479974100.git.kirtika@chromium.org>
Kirtika Ruchandani <kirtika.ruchandani@gmail.com> wrote:
> Commit ca996ec56608 (ath10k: implement wmi-tlv backend)
> introduced ath10k_wmi_tlv_op_gen_vdev_start() where
> 'struct wmi_p2p_noa_descriptor *noa' is defined and set but not used.
> Compiling with W=1 gives the following warning, fix it.
> drivers/net/wireless/ath/ath10k/wmi-tlv.c: In function ‘ath10k_wmi_tlv_op_gen_vdev_start’:
> drivers/net/wireless/ath/ath10k/wmi-tlv.c:1647:33: warning: variable ‘noa’ set but not used [-Wunused-but-set-variable]
>
> Fixes: ca996ec56608 ("ath10k: implement wmi-tlv backend")
> Cc: Michal Kazior <michal.kazior@tieto.com>
> Cc: Kalle Valo <kvalo@qca.qualcomm.com>
> Signed-off-by: Kirtika Ruchandani <kirtika@chromium.org>
No response to Michal's comment by the author
Patch set to Changes Requested.
--
https://patchwork.kernel.org/patch/9444937/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
^ permalink raw reply
* Re: [PATCH v2] mac80211: prevent skb/txq mismatch
From: Johannes Berg @ 2017-01-13 13:57 UTC (permalink / raw)
To: Michal Kazior; +Cc: linux-wireless, greearb, mohammed
In-Reply-To: <1484310771-28359-1-git-send-email-michal.kazior@tieto.com>
On Fri, 2017-01-13 at 13:32 +0100, Michal Kazior wrote:
> Station structure is considered as not uploaded
> (to driver) until drv_sta_state() finishes. This
> call is however done after the structure is
> attached to mac80211 internal lists and hashes.
> This means mac80211 can lookup (and use) station
> structure before it is uploaded to a driver.
>
[...]
Applied, thanks.
johannes
^ permalink raw reply
* pull-request: mac80211 2017-01-13
From: Johannes Berg @ 2017-01-13 13:55 UTC (permalink / raw)
To: David Miller; +Cc: netdev, linux-wireless
Hi Dave,
Here's another update for the current cycle. Some of those
patches have been sitting in our tree and I haven't been
pulling them out quickly enough - will try to do better...
Please pull and let me know if there's any problem.
Thanks,
johannes
The following changes since commit 03430fa10b99e95e3a15eb7c00978fb1652f3b24:
Merge branch 'bcm_sf2-fixes' (2017-01-08 22:01:22 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git tags/mac80211-for-davem-2017-01-13
for you to fetch changes up to dbef53621116474bb883f76f0ba6b7640bc42332:
mac80211: prevent skb/txq mismatch (2017-01-13 14:47:21 +0100)
----------------------------------------------------------------
We have a number of fixes, in part because I was late
in actually sending them out - will try to do better in
the future:
* handle VHT opmode properly when hostapd is controlling
full station state
* two fixes for minimum channel width in mac80211
* don't leave SMPS set to junk in HT capabilities
* fix headroom when forwarding mesh packets, recently
broken by another fix that failed to take into account
frame encryption
* fix the TID in null-data packets indicating EOSP (end
of service period) in U-APSD
* prevent attempting to use (and then failing which
results in crashes) TXQs on stations that aren't added
to the driver yet
----------------------------------------------------------------
Beni Lev (1):
cfg80211: consider VHT opmode on station update
Cedric Izoard (1):
mac80211: Fix headroom allocation when forwarding mesh pkt
Emmanuel Grumbach (1):
mac80211: fix the TID on NDPs sent as EOSP carrier
Felix Fietkau (1):
mac80211: initialize SMPS field in HT capabilities
Johannes Berg (3):
mac80211: implement multicast forwarding on fast-RX path
mac80211: calculate min channel width correctly
mac80211: recalculate min channel width on VHT opmode changes
Michal Kazior (1):
mac80211: prevent skb/txq mismatch
include/uapi/linux/nl80211.h | 4 +++-
net/mac80211/chan.c | 3 ---
net/mac80211/iface.c | 21 +++++++++++++++++++++
net/mac80211/main.c | 13 +++++++++----
net/mac80211/rate.c | 2 ++
net/mac80211/rx.c | 38 +++++++++++++++++++++-----------------
net/mac80211/sta_info.c | 4 ++--
net/mac80211/tx.c | 17 +++++++----------
net/mac80211/vht.c | 4 +++-
net/wireless/nl80211.c | 15 +++++++++++++++
10 files changed, 83 insertions(+), 38 deletions(-)
^ permalink raw reply
* Re: linux-next: build warning after merge of the wireless-drivers-next tree
From: Kalle Valo @ 2017-01-13 13:47 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Kalle Valo, Wireless, linux-next, linux-kernel, Xinming Hu,
Amitkumar Karwar
In-Reply-To: <20170113111250.2023a160@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> After merging the wireless-drivers-next tree, today's linux-next build
> (x86_64 allmodconfig) produced this warning:
>
> drivers/net/wireless/marvell/mwifiex/pcie.c: In function 'mwifiex_pcie_remove':
> drivers/net/wireless/marvell/mwifiex/pcie.c:303:5: warning: 'fw_status' may be used uninitialized in this function [-Wmaybe-uninitialized]
> if (fw_status == FIRMWARE_READY_PCIE && !adapter->mfg_mode) {
> ^
>
> Introduced by commit
>
> 045f0c1b5e26 ("mwifiex: get rid of global user_rmmod flag")
>
> This is not a false positive since "reg" could be NULL just above
> (otherwise it would be tested for).
Thanks, I noticed this myself yesterday (after I had applied the patch)
and I have asked Marvell to send a fix.
--
Kalle Valo
^ permalink raw reply
* Re: ath10k: Fix Tx legacy rate reporting
From: Kalle Valo @ 2017-01-13 13:35 UTC (permalink / raw)
To: Mohammed Shafi Shajakhan
Cc: ath10k, mohammed, linux-wireless, Mohammed Shafi Shajakhan
In-Reply-To: <1484063603-13652-1-git-send-email-mohammed@qca.qualcomm.com>
Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com> wrote:
> From: Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com>
>
> Tx legacy rate is reported 10 fold, as below
>
> iw dev wlan#N station dump | grep "tx bitrate"
> tx bitrate: 240.0 MBit/s
>
> This is because by mistake we muliply by the hardware reported
> rate twice by 10, fix this.
>
> Fixes: cec17c382140 ("ath10k: add per peer htt tx stats support for 10.4")
> Signed-off-by: Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com>
Patch applied to ath-next branch of ath.git, thanks.
cd59102779ac ath10k: fix tx legacy rate reporting
--
https://patchwork.kernel.org/patch/9508075/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
^ permalink raw reply
* Re: ath10k: Fix wifi connectivity and warning in Rx with channel 169
From: Kalle Valo @ 2017-01-13 13:34 UTC (permalink / raw)
To: Mohammed Shafi Shajakhan
Cc: ath10k, mohammed, linux-wireless, Mohammed Shafi Shajakhan
In-Reply-To: <1484062318-13476-1-git-send-email-mohammed@qca.qualcomm.com>
Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com> wrote:
> From: Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com>
>
> In countries where basic operation of channel 169 is allowed,
> this fixes the below WARN_ON_ONCE in Rx and fixes the station
> connectivity failure in channel 169 as the packet is dropped
> in the driver as the current check limits to channel 165. As of
> now all the packets beyond channel 165 is dropped, fix this
> by extending the range to channel 169.
>
> Call trace:
>
> drivers/net/wireless/ath/ath10k/wmi.c:1505
> ath10k_wmi_event_mgmt_rx+0x278/0x440 [ath10k_core]()
> Call Trace:
> [<c158f812>] ? printk+0x2d/0x2f
> [<c105a182>] warn_slowpath_common+0x72/0xa0
> [<f8b67b58>] ? ath10k_wmi_event_mgmt_rx+0x278/0x440
>
> [<f8b67b58>] ? ath10k_wmi_event_mgmt_rx+0x278/0x440
>
> [<c105a1d2>] warn_slowpath_null+0x22/0x30
> [<f8b67b58>] ath10k_wmi_event_mgmt_rx+0x278/0x440
>
> [<f8b0e72b>] ? ath10k_pci_sleep+0x8b/0xb0 [ath10k_pci]
> [<f8b6ac63>] ath10k_wmi_10_2_op_rx+0xf3/0x3b0
>
> [<f8b6495e>] ath10k_wmi_process_rx+0x1e/0x60
>
> [<f8b5f077>] ath10k_htc_rx_completion_handler+0x347/0x4d0 [ath10k_core]
> [<f8b11dc3>] ? ath10k_ce_completed_recv_next+0x53/0x70 [ath10k_pci]
> [<f8b0f921>] ath10k_pci_ce_recv_data+0x171/0x1d0 [ath10k_pci]
> [<f8b0ec69>] ? ath10k_pci_write32+0x39/0x80 [ath10k_pci]
> [<f8b120bc>] ath10k_ce_per_engine_service+0x5c/0xa0 [ath10k_pci]
> [<f8b1215f>] ath10k_ce_per_engine_service_any+0x5f/0x70 [ath10k_pci]
> [<c1060dc0>] ? local_bh_enable_ip+0x90/0x90
> [<f8b1048b>] ath10k_pci_tasklet+0x1b/0x50 [ath10k_pci]
>
> Fixes: 34c30b0a5e97 ("ath10k: enable advertising support for channel 169, 5Ghz")
> Signed-off-by: Mohammed Shafi Shajakhan <mohammed@qti.qualcomm.com>
Patch applied to ath-next branch of ath.git, thanks.
c486dc571a37 ath10k: fix wifi connectivity and warning in rx with channel 169
--
https://patchwork.kernel.org/patch/9508031/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
^ permalink raw reply
* Re: ath9k: move RELAY and DEBUG_FS to ATH9K[_HTC]_DEBUGFS
From: Kalle Valo @ 2017-01-13 13:29 UTC (permalink / raw)
To: Christian Lamparter
Cc: QCA ath9k Development, linux-wireless, ath9k-devel, Kalle Valo
In-Reply-To: <20170109174852.20114-1-chunkeey@googlemail.com>
Christian Lamparter <chunkeey@googlemail.com> wrote:
> Currently, the common ath9k_common module needs to have a
> dependency on RELAY and DEBUG_FS in order to built. This
> is usually not a problem. But for RAM and FLASH starved
> AR71XX devices, every little bit counts.
>
> This patch adds a new symbol CONFIG_ATH9K_COMMON_DEBUG
> which makes it possible to drop the RELAY and DEBUG_FS
> dependency there and move it to ATH_(HTC)_DEBUGFS.
>
> Note: The shared FFT/spectral code (which is the only user
> of the relayfs in ath9k*) needs DEBUG_FS to export the relayfs
> interface to dump the data to userspace. So it makes no sense
> to have the functions compiled in, if DEBUG_FS is not there.
>
> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
Patch applied to ath-next branch of ath.git, thanks.
1077ec472df4 ath9k: move RELAY and DEBUG_FS to ATH9K[_HTC]_DEBUGFS
--
https://patchwork.kernel.org/patch/9505653/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
^ permalink raw reply
* Re: [1/2] ath10k: add accounting for the extended peer statistics
From: Kalle Valo @ 2017-01-13 13:28 UTC (permalink / raw)
To: Christian Lamparter; +Cc: linux-wireless, ath10k
In-Reply-To: <992a4e2676037a06f482cdbe2d3d39e287530be5.1480974623.git.chunkeey@googlemail.com>
Christian Lamparter <chunkeey@googlemail.com> wrote:
> The 10.4 firmware adds extended peer information to the
> firmware's statistics payload. This additional info is
> stored as a separate data field and the elements are
> stored in their own "peers_extd" list.
>
> These elements can pile up in the same way as the peer
> information elements. This is because the
> ath10k_wmi_10_4_op_pull_fw_stats() function tries to
> pull the same amount (num_peer_stats) for every statistic
> data unit.
>
> Fixes: 4a49ae94a448faa ("ath10k: fix 10.4 extended peer stats update")
> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
Patch applied to ath-next branch of ath.git, thanks.
c1e3330f22bc ath10k: add accounting for the extended peer statistics
--
https://patchwork.kernel.org/patch/9461631/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
^ permalink raw reply
* Re: [v2,1/2] ath10k: refactor ath10k_peer_assoc_h_phymode()
From: Kalle Valo @ 2017-01-13 13:27 UTC (permalink / raw)
To: Kalle Valo; +Cc: ath10k, linux-wireless
In-Reply-To: <20161014101859.5300.47040.stgit@potku.adurom.net>
Kalle Valo <kvalo@qca.qualcomm.com> wrote:
> When adding VHT160 support to ath10k_peer_assoc_h_phymode() the VHT mode
> selection code becomes too complex. Simplify it by refactoring the vht part to
> a separate function.
>
> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
2 patches applied to ath-next branch of ath.git, thanks.
06efdbe70f9c ath10k: refactor ath10k_peer_assoc_h_phymode()
bc1efd739b61 ath10k: add VHT160 support
--
https://patchwork.kernel.org/patch/9376371/
Documentation about submitting wireless patches and checking status
from patchwork:
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
^ permalink raw reply
* Re: [PATCH] mac80211: fix documentation warnings
From: Johannes Berg @ 2017-01-13 13:14 UTC (permalink / raw)
To: Markus Heiser; +Cc: linux-wireless, corbet, linux-doc
In-Reply-To: <4973EEB8-5F54-451E-B939-CDA94332CEF7@darmarit.de>
On Fri, 2017-01-13 at 13:43 +0100, Markus Heiser wrote:
> does it make live easier when we use in-line member comments:
>
> https://www.kernel.org/doc/html/latest/doc-guide/kernel-doc.html#in-
> line-member-documentation-comments
>
> and place the entire list in a literalblock?
Ah yes, I forgot about that. I should convert everything to that, but
that's probably better done separately.
johannes
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox