This patch series allows to use the firmware debugging features
of iwlwifi on 3.16. These features are already in 3.17.
I know that this patch series is not compliant with Greg's
rules for stable patches. It is unlikely that these patches
will be applied on vanilla 3.16 - I know that.
I send them
commit c2d202017da18ebd6567862bd9a50392970f048f upstream
This allows to use the firmware monitor. This capability
uses a lot of contiguous memory (up to 64MB), so make its
usage module parameter dependent.
The driver will try to allocate as much contiguous memory
as possible downgrading its
commit 655e6d6db21b0c0d411aef9d816816fb68b0496c upstream.
Its content can move to the caller.
While at it, move iwl_mvm_fw_error_rxf_dump to caller.
Signed-off-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
---
drivers/net/wireless/iwlwifi/mvm/mac80211.c | 100
commit 5bfe6f53283de44855ee45a102210abbfac995f9 upstream.
The memory was not zeroed - fix that. Also update the
iwl_fw_error_dump_info structure.
Signed-off-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
---
drivers/net/wireless/iwlwifi/mvm/mac80211.c | 2 +-
1 file changed, 1 insertion(+),
commit d4849277f92a0bfa08a988545ea527fc8e0c9571 upstream.
The chunks of data do not need to be multipliers of 4 nor
4-bytes aligned.
Signed-off-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
---
drivers/net/wireless/iwlwifi/iwl-fw-error-dump.h | 4 ++--
1 file changed, 2 insertions(+), 2
commit 1fa1605648d15d42f350807279b6c6e8d33b6382 upstream.
This is not related to mvm. Rename to iwl_fw_error_next_data.
Signed-off-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
---
drivers/net/wireless/iwlwifi/iwl-fw-error-dump.h | 4 ++--
drivers/net/wireless/iwlwifi/mvm/ops.c |
commit 06ddbf5adac1fd2a031eade8a92239abfa6db93a upstream.
This can be useful later for parsing since the parsing may
differ based on the device's family / bus.
Also add the human readable version of the firmware.
Signed-off-by: Emmanuel Grumbach emmanuel.grumb...@intel.com
---
On Tue, Oct 28, 2014 at 08:11:19AM +0200, Emmanuel Grumbach wrote:
This patch series allows to use the firmware debugging features
of iwlwifi on 3.16. These features are already in 3.17.
I know that this patch series is not compliant with Greg's
rules for stable patches. It is unlikely that
On Mon, 2014-10-27 at 16:14 -0700, Marcel Holtmann wrote:
Hi Luca,
Hi Marcel,
That's not particularly hard to figure out, for example by looking at
sysfs.
Is this really so time-constrained/important/... that you can't do that?
It does not seem very practical to dig this
2014-10-27 21:04 GMT+03:00 John W. Linville linvi...@tuxdriver.com:
On Wed, Oct 22, 2014 at 03:03:49AM +0400, Sergey Ryazanov wrote:
This reverts commit 093ec3c5337434f40d77c1af06c139da3e5ba6dc.
AHB bus code has been removed, since we did not have support Atheros
AR231x SoC, required for
On 08.10.2014 11:53, Stanislaw Gruszka wrote:
On Tue, Oct 07, 2014 at 05:12:47PM +0200, poma wrote:
BTW, pán Gruszka, when will these devices be supported as a part of the
upstream Linux kernel?
I'm not an oracle :-)
Larry declared to work on some mt76xx chip support, I'm cc him.
I
On Monday, October 27, 2014 01:26:37 PM John W. Linville wrote:
On Tuesday, October 14, 2014 02:28:58 PM Xose Vazquez Perez wrote:
(57240 - 65880 @ 2160), (40), NO-OUTDOOR should(must) be replaced by:
(57000 - 66000 @ 2160), (40)
Would someone like to post a patch to that effect?
Hello, Joe,
On 24 October 2014 02:43, Joe Perches j...@perches.com wrote:
struct ipw_rt_hdr {
struct ieee80211_radiotap_header rt_hdr;
u64 rt_tsf; /* TSF */ /* XXX */
u8 rt_flags;/* radiotap packet flags *
u8 rt_rate; /* rate in 500kb/s */
Hi,
This is a partial re-spin which includes the
not-yet-applied patches that fix/change warm
reset.
v3:
* change CE ring cleanup (new patch #1)
Michal Kazior (4):
ath10k: change ce ring cleanup logic
ath10k: make warm reset a bit safer and faster
ath10k: split reset logic from power up
Currently hif_power_up performs effectively a
reset and hif_stop resets the chip as well so
there's no point in resetting here.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
Notes:
v2:
* this patch replaces `replace power up/down with reset callback` [Kalle]
One of the problems with warm reset I've found is
that it must be guaranteed that copy engine
registers are not being accessed while being
reset. Otherwise in worst case scenario the host
may lock up.
Instead of using sleeps and hoping the device is
operational in some arbitrary timeframes use
Until now it was possible to simulate soft and
hard fw crashes but it wasn't possible to trigger
an immediately hw restart itself (without the fw
crash).
This can be useful when stress testing hw
restarting stability, e.g. during heavy tx/rx
traffic.
Signed-off-by: Michal Kazior
While testing other things I've found that CE
items aren't cleared properly. This could lead to
null dereferences in BMI.
To prevent that make sure CE revoking clears the
nbytes value (which is used as a buffer completion
indication) and memset the entire CE ring data
shared between host and
In some cases hw recovery was taking an absurdly
long time due to ath10k waiting for things that
would never really complete.
Instead of waiting for inevitable timeouts poke
all completions and wakequeues and check if it's
still worth waiting.
Reading/writing ar-state requires conf_mutex.
Since
Patch #1 fixes a bug I've found while testing
patches #2 and #3. It's safe to cherry-pick it in
case patches #2 and/or #3 aren't accepted or need
a re-spin.
I've mainly used patch #2 to test reset and
recovery. It's pretty handy for (stress-)testing.
Patch #3 should improve recovery speed in
The driver uses devm_gpiod_get_index(..., index) so that the index refers
directly to the GpioIo resource under the ACPI device. The problem with
this is that if the ordering changes we get wrong GPIOs.
With ACPI 5.1 _DSD we can now use names instead to reference GPIOs
analogous to Device Tree.
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/db.txt b/db.txt
index 43afa5c..be24c73 100644
--- a/db.txt
+++ b/db.txt
@@ -70,6 +70,13 @@ country AR: DFS-FCC
(5490 - 5730
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/db.txt b/db.txt
index be24c73..7a0b0dc 100644
--- a/db.txt
+++ b/db.txt
@@ -156,6 +156,13 @@ country BL: DFS-ETSI
(5250 -
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/db.txt b/db.txt
index 7a0b0dc..11c8716 100644
--- a/db.txt
+++ b/db.txt
@@ -181,6 +181,13 @@ country BR: DFS-FCC
(5490 -
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 6 ++
1 file changed, 6 insertions(+)
diff --git a/db.txt b/db.txt
index 40ef0e8..024b424 100644
--- a/db.txt
+++ b/db.txt
@@ -382,6 +382,12 @@ country ES: DFS-ETSI
# 60 gHz
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/db.txt b/db.txt
index 11c8716..40ef0e8 100644
--- a/db.txt
+++ b/db.txt
@@ -268,6 +268,13 @@ country CR: DFS-FCC
(5490 -
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 6 ++
1 file changed, 6 insertions(+)
diff --git a/db.txt b/db.txt
index 024b424..07e56d0 100644
--- a/db.txt
+++ b/db.txt
@@ -418,6 +418,12 @@ country GE: DFS-ETSI
# 60 gHz
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 6 ++
1 file changed, 6 insertions(+)
diff --git a/db.txt b/db.txt
index 07e56d0..4ecfcf3 100644
--- a/db.txt
+++ b/db.txt
@@ -446,6 +446,12 @@ country GH: DFS-FCC
(5490 -
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/db.txt b/db.txt
index 4ecfcf3..6d8abd1 100644
--- a/db.txt
+++ b/db.txt
@@ -625,6 +625,13 @@ country KW: DFS-ETSI
(5170 -
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/db.txt b/db.txt
index 6d8abd1..04614fe 100644
--- a/db.txt
+++ b/db.txt
@@ -750,6 +750,13 @@ country MK: DFS-ETSI
# 60 gHz
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/db.txt b/db.txt
index 04614fe..bbc7f8c 100644
--- a/db.txt
+++ b/db.txt
@@ -757,6 +757,13 @@ country MN: DFS-FCC
(5490 -
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 6 ++
1 file changed, 6 insertions(+)
diff --git a/db.txt b/db.txt
index bbc7f8c..0a507d6 100644
--- a/db.txt
+++ b/db.txt
@@ -764,6 +764,12 @@ country MP: DFS-FCC
(5490 -
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 6 ++
1 file changed, 6 insertions(+)
diff --git a/db.txt b/db.txt
index 5869b96..7319579 100644
--- a/db.txt
+++ b/db.txt
@@ -793,6 +793,12 @@ country MU: DFS-FCC
(5490 -
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/db.txt b/db.txt
index 7319579..1c9e307 100644
--- a/db.txt
+++ b/db.txt
@@ -812,6 +812,13 @@ country MX: DFS-FCC
(5490 -
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 6 ++
1 file changed, 6 insertions(+)
diff --git a/db.txt b/db.txt
index 1c9e307..640d2a7 100644
--- a/db.txt
+++ b/db.txt
@@ -874,6 +874,12 @@ country PE: DFS-FCC
(5490 -
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/db.txt b/db.txt
index 640d2a7..7e14d24 100644
--- a/db.txt
+++ b/db.txt
@@ -934,6 +934,13 @@ country PW: DFS-FCC
(5490 -
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 6 ++
1 file changed, 6 insertions(+)
diff --git a/db.txt b/db.txt
index e2981a2..8d56c92 100644
--- a/db.txt
+++ b/db.txt
@@ -1029,6 +1029,12 @@ country SN: DFS-FCC
(5490 -
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 6 ++
1 file changed, 6 insertions(+)
diff --git a/db.txt b/db.txt
index 292dbac..2a54da8 100644
--- a/db.txt
+++ b/db.txt
@@ -1195,6 +1195,12 @@ country WF: DFS-ETSI
country YE:
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/db.txt b/db.txt
index 95a750f..292dbac 100644
--- a/db.txt
+++ b/db.txt
@@ -1163,6 +1163,13 @@ country VE: DFS-FCC
(5250 -
Source is QCA's regulatory team's efforts.
Signed-off-by: Jouni Malinen jo...@qca.qualcomm.com
---
db.txt | 7 +++
1 file changed, 7 insertions(+)
diff --git a/db.txt b/db.txt
index 8d56c92..95a750f 100644
--- a/db.txt
+++ b/db.txt
@@ -1114,6 +1114,13 @@ country UA: DFS-ETSI
# 60
From: Luciano Coelho luciano.coe...@intel.com
Due to the time it takes to process the beacon that started the CSA
process, we may be late for the switch if we try to reach exactly
beacon 0. To avoid that, use count - 1 when calculating the switch time.
Reported-by: Jouni Malinen j...@w1.fi
From: Luciano Coelho luciano.coe...@intel.com
If we are switching from an HT40+ to an HT40- channel (or vice-versa),
we need the secondary channel offset IE to specify what is the
post-CSA offset to be used. This applies both to beacons and to probe
responses.
In ieee80211_parse_ch_switch_ie()
On 20 October 2014 14:58, Michal Kazior michal.kaz...@tieto.com wrote:
Latest firmware revision introduced a new WMI ABI
called wmi-tlv. It is not a tlv strictly speaking
but something that resembles it because it is
ordered and may have duplicate id entries.
This will be used by new
The first patch was already posted earlier:
Message-ID: 1413043315-22332-1-git-send-email-ar...@broadcom.com
This series include changes in driver code to investigate potential
code savings. As example used the ath9k driver as it has a fair
amount of debugfs files. In this series it changes 7
This patch adds a helper function that simplifies adding a
so-called single_open sequence file for device drivers. The
calling device driver needs to provide a read function and
a device pointer. The field struct seq_file::private will
reference the device pointer upon call to the read function
so
Use the helper to get rid of the file operations per debugfs file. The
struct ath9k_softc pointer is set as device driver data to be obtained
in the seq_file read operation.
Signed-off-by: Arend van Spriel ar...@broadcom.com
---
drivers/net/wireless/ath/ath9k/ahb.c | 1 +
Hi Amitkumar,
On Thu, Oct 23, 2014 at 2:40 PM, Amitkumar Karwar akar...@marvell.com wrote:
Hi Marek,
I tried to capture logs but when enable DYNAMIC_DEBUG I cannot
reproduce issue (running test 30 minutes without allocation
failure).
Thanks for the testing. Yes. Sometimes timing issues
(fixed Johannes' email address)
Both these bugs go far back, so IMHO they should go to 3.8 and stable.
1/2 goes back to 3.13
2/2 goes back to 2.6.30 (though the affected code changed somewhat
since then)
--
Luca.
On Tue, 2014-10-28 at 13:33 +0200, Luca Coelho wrote:
This series has a couple of wowl patches that were too late to make
the 3.18 merge window. Apart from those there are a number of rename
and rework patches that get rid of the terms dhd and wl.
The series is intended for 3.19 and applies to the master branch
of the wireless-next repository.
From: Hante Meuleman meule...@broadcom.com
This patch adds wowl support for SDIO bus devices. This feature
requires FW which has support for wowl built in.
Reviewed-by: Arend Van Spriel ar...@broadcom.com
Reviewed-by: Franky (Zhenhui) Lin fran...@broadcom.com
Reviewed-by: Pieter-Paul Giesberts
Showing the firmware error allows to quickly give a clue what
went wrong and directly look in the firmware code that gave us
back the error.
Reviewed-by: Franky (Zhenhui) Lin fran...@broadcom.com
Reviewed-by: Hante Meuleman meule...@broadcom.com
Reviewed-by: Daniel (Deognyoun) Kim
Passing the firmware error codes up the driver may be mapped to
linux error numbers which may impact proper fault analysis. So
better pass up a generic failure code, ie. -EBADE and only show
firmware error code in FIL debug message.
Reviewed-by: Franky (Zhenhui) Lin fran...@broadcom.com
From: Hante Meuleman meule...@broadcom.com
Reviewed-by: Arend Van Spriel ar...@broadcom.com
Reviewed-by: Pieter-Paul Giesberts piete...@broadcom.com
Signed-off-by: Hante Meuleman meule...@broadcom.com
Signed-off-by: Arend van Spriel ar...@broadcom.com
---
From: Hante Meuleman meule...@broadcom.com
Reviewed-by: Arend Van Spriel ar...@broadcom.com
Reviewed-by: Pieter-Paul Giesberts piete...@broadcom.com
Signed-off-by: Hante Meuleman meule...@broadcom.com
Signed-off-by: Arend van Spriel ar...@broadcom.com
---
On Mon, Oct 27, 2014 at 07:19:32PM +0100, Oleksij Rempel wrote:
Am 27.10.2014 um 16:20 schrieb John W. Linville:
On Mon, Oct 27, 2014 at 11:02:00AM +0800, Etna wrote:
I am not a developer, but I stumbled upon this just a couple of days ago in
the OpenWRT forums:
From: Hante Meuleman meule...@broadcom.com
Rename sdio_host.h to sdio.h and dhd_sdio.c to sdio.c.
Reviewed-by: Arend Van Spriel ar...@broadcom.com
Reviewed-by: Pieter-Paul Giesberts piete...@broadcom.com
Signed-off-by: Hante Meuleman meule...@broadcom.com
Signed-off-by: Arend van Spriel
Am 28.10.2014 um 15:06 schrieb Arend van Spriel:
On 28-10-14 14:46, John W. Linville wrote:
On Mon, Oct 27, 2014 at 07:19:32PM +0100, Oleksij Rempel wrote:
Am 27.10.2014 um 16:20 schrieb John W. Linville:
On Mon, Oct 27, 2014 at 11:02:00AM +0800, Etna wrote:
I am not a developer, but I
When interface is down, recovery flow should not be attempted.
Next ndo_open() will trigger target reset, that is FW recovery.
Doing recovery while interface is down cause internal up, leaving
internal driver state in conflict with network stack. Then, when network
stack will call ndo_open(),
Disconnect flow may be invoked either from upper layer request,
or from event reported by the firmware.
In case of firmware event, driver need to release resources for the station but
not send another disconnect WMI command.
In case of upper layer request, WMI_DISCONNECT_STA_CMDID command need
minor fixes, except for the last patch that adds support
for the maximum MTU up to 7920, as by the 802.11ad spec
Vladimir Kondratiev (5):
wil6210: do not attempt FW recovery if interface is down
wil6210: reset flow updates
wil6210: prevent double disconnect command issuing
wil6210:
In case of FW error, make it clear (in dmesg) what branch is taken
in the error recovery code.
Signed-off-by: Vladimir Kondratiev qca_vkond...@qca.qualcomm.com
---
drivers/net/wireless/ath/wil6210/main.c | 3 +++
1 file changed, 3 insertions(+)
diff --git
It is possible to configure driver using mtu_max module parameter
by setting it to value in range of 68..7920 inclusive.
This is sub-optimal performance-wise in case packet is larger than 1 page.
mtu_max default value is 2228.
Signed-off-by: Vladimir Kondratiev qca_vkond...@qca.qualcomm.com
---
As communicated with the firmware hardware teams
Signed-off-by: Vladimir Kondratiev qca_vkond...@qca.qualcomm.com
---
drivers/net/wireless/ath/wil6210/main.c| 23 ++-
drivers/net/wireless/ath/wil6210/wil6210.h | 6 ++
2 files changed, 24 insertions(+), 5
On Tue, 2014-10-28 at 14:56 +0100, Arend van Spriel wrote:
This series has a couple of wowl patches that were too late to make
the 3.18 merge window. Apart from those there are a number of rename
and rework patches that get rid of the terms dhd and wl.
The series is intended for 3.19 and
0x1b75 0xa200 AirLive WN-200USB wireless 11b/g/n dongle
References: https://bugs.debian.org/766802
Reported-by: Martin Mokrejs mmokr...@fold.natur.cuni.cz
Cc: sta...@vger.kernel.org
Signed-off-by: Cyril Brulebois k...@debian.org
---
drivers/net/wireless/rt2x00/rt2800usb.c |1 +
1 file
For packet log, the transmitted frame 802.11 header alone is sufficient.
Recording entire packet is also consuming lot of disk space. To
optimize, add tracepoints for sending tx-ed 802.11 headers alone.
Cc: Michal Kazior michal.kaz...@tieto.com
Signed-off-by: Rajkumar Manoharan
On Tue, 2014-10-28 at 22:18 +0530, Rajkumar Manoharan wrote:
For packet log, the transmitted frame 802.11 header alone is sufficient.
Recording entire packet is also consuming lot of disk space. To
optimize, add tracepoints for sending tx-ed 802.11 headers alone.
FWIW, in iwlwifi I made the
From: John W. Linville linvi...@tuxdriver.com
Date: Tue, 28 Oct 2014 15:05:19 -0400
Please pull this batch of fixes intended for the 3.18 stream!
...
git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless.git
tags/master-2014-10-27
Pulled, thanks John.
--
To unsubscribe from this
On Sun 2014-10-26 12:05:54, Pavel Machek wrote:
On Sun 2014-10-26 11:33:15, Stanislaw Gruszka wrote:
On Sat, Oct 25, 2014 at 01:42:46PM +0200, Pavel Machek wrote:
Since 3.17 we have only 2 minor iwlegacy changes on current linus tree.
If this is a regression it's probably caused by
- Use config symbol defined in the driver instead of arch specific one for
conditional compilation.
- Rename the ATHEROS_AR231X config symbol to ATH25.
- Fix include (ar231x_platform.h - ath25_platform.h).
- Some of AR231x SoCs (e.g. AR2315) have PCI bus support, so remove !PCI
dependency,
-btcoexist.btc_ops-btc_init_hal_vars(rtlpriv);
}
Hi, Larry everyone.
This patch didn't solve and next-20141028 is still crashing on my laptop
with rtl8192se device:
http://opsfelder.com/~murilo/lkml/next-20141028_crashing.jpg
--
Murilo
--
To unsubscribe from this list: send the line
On Tue, Oct 28, 2014 at 05:59:39PM +0100, Johannes Berg wrote:
On Tue, 2014-10-28 at 22:18 +0530, Rajkumar Manoharan wrote:
For packet log, the transmitted frame 802.11 header alone is sufficient.
Recording entire packet is also consuming lot of disk space. To
optimize, add tracepoints for
72 matches
Mail list logo