This shouldn't really happen but take into account
the original service bitmap length when mapping
service ids.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
Notes:
v2:
* remove space between brackets as per checkpatch warning
drivers/net/wireless/ath/ath10k/wmi.c | 6 +-
Since the 10.x fw branch support was introduced it
became apparent ath10k will need to be able to
deal with different fw ABIs eventually.
The patch creates an abstraction for dealing with
command and event structures across different ABIs
and mostly gets rid of the
ATH10K_FW_FEATURE_WMI_10X flag
Latest main firmware branch 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 prepares ath10k to support new hw.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
Notes:
The service bitmap can be used to determine
firmware capabilities.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
drivers/net/wireless/ath/ath10k/core.h | 2 +-
drivers/net/wireless/ath/ath10k/debug.c | 11 +++
drivers/net/wireless/ath/ath10k/debug.h | 9 -
Some functions can be shared across different WMI
ABIs. Make them public so different WMI backends
can use them from different source files in the
future.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
drivers/net/wireless/ath/ath10k/wmi.c | 136 ++
An attribute NL80211_ATTR_SOCKET_OWNER can be set by the scan initiator.
If present, the attribute will cause the scan to be stopped if the client
dies.
Signed-off-by: Jukka Rissanen jukka.rissa...@linux.intel.com
---
include/net/cfg80211.h | 1 +
include/uapi/linux/nl80211.h | 3 +++
Hi,
v8:
- reworked the RCU code and placed it in patch 2
v7:
- convert the cfg80211_sched_scan_request to __rcu pointer in order
to avoid races when accessing it
- reverting the patch v6, the port id is back in request struct
v6:
- moved owner netlink port id from cfg80211_sched_scan_request
This wasn't used since forever and there are no
plans on using it.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
drivers/net/wireless/ath/ath10k/hif.h | 3 +--
drivers/net/wireless/ath/ath10k/htc.c | 3 +--
drivers/net/wireless/ath/ath10k/pci.c | 2 +-
3 files changed, 3
Because of possible races when accessing sched_scan_req pointer in
rdev, the sched_scan_req is converted to RCU pointer.
Signed-off-by: Jukka Rissanen jukka.rissa...@linux.intel.com
---
include/net/cfg80211.h | 1 +
net/wireless/core.c| 10 +++---
net/wireless/core.h| 2 +-
In theory it was possible to starve the system if
a tx/rx handler could implicitly trigger more
tx/rx pci events.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
drivers/net/wireless/ath/ath10k/pci.c | 21 +++--
1 file changed, 15 insertions(+), 6 deletions(-)
diff
Pass the eid argument via skbuff control buffer.
This will make it possible to work with queues of
HTC event buffers.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
---
drivers/net/wireless/ath/ath10k/core.h | 1 +
drivers/net/wireless/ath/ath10k/hif.h | 3 +--
Hi John,
Here's one more bluetooth-next pull request for 3.19:
- Minor cleanups for ieee802154 mac802154
- Fix for the kernel warning with !TASK_RUNNING reported by Kirill A.
Shutemov
- Support for another ath3k device
- Fix for tracking link key based security level
- Device tree
On Wed, Nov 12, 2014 at 04:26:45PM +0200, Tomasz Bursztyka wrote:
Let the other listeners being notified when a new or del interface
command has been issued, thus reducing later necessary request to be in
sync with current context.
This seems to trigger a NULL pointer dereference in
Hi,
here's ath10k device tree support which Toshi and me have been working
on. Please review.
Device tree maintainers: please review the bindings document
carefully, this is the first time I have written one.
v3:
* add a debug message to ath10k
* write bindings file
* use ar-dev.of_node
Document how calibration data can be provided to ath10k via Device Tree.
Signed-off-by: Kalle Valo kv...@qca.qualcomm.com
---
.../bindings/net/wireless/qcom,ath10k.txt | 30
1 file changed, 30 insertions(+)
create mode 100644
From: Toshi Kikuchi tos...@chromium.org
This patch adds support for reading calibration data from Device Tree.
It looks for the calibration data in Device Tree if it can't find it
in a file. If there's no node in Device Tree, ath10k will try to find the
calibration data from OTP.
The node for
Kalle Valo kv...@qca.qualcomm.com writes:
here's ath10k device tree support which Toshi and me have been working
on. Please review.
Device tree maintainers: please review the bindings document
carefully, this is the first time I have written one.
Argh, I again used the old devicetree
Document how calibration data can be provided to ath10k via Device Tree.
Signed-off-by: Kalle Valo kv...@qca.qualcomm.com
---
.../bindings/net/wireless/qcom,ath10k.txt | 30
1 file changed, 30 insertions(+)
create mode 100644
Hi,
here's providing ath10k calibration data via device tree support which
Toshi and me have been working on. Please review.
Device tree maintainers: please review the bindings document
carefully, this is the first time I have written one.
v4:
* use correct devicetree mailing list address
v3:
On Thursday 27 November 2014 14:08:56 Kalle Valo wrote:
diff --git a/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
b/Documentation/devicetree/bindings/net/wireless/qcom,ath10k.txt
new file mode 100644
index ..edefc26c6204
--- /dev/null
+++
When we want to calculate the minimal bandwidth needed for
a channel context, we need to take into account vifs that
have reserved the channel context.
I hit an issue with iwlwifi and channel switch as a client.
We would allocate a virgin channel context and reserve it.
At that stage, the min_def
Michal Kazior michal.kaz...@tieto.com writes:
This wasn't used since forever and there are no
plans on using it.
Signed-off-by: Michal Kazior michal.kaz...@tieto.com
I modified the title to get it more unique:
ath10k: remove unused callback argument from struct ath10k_hif_cb::rx_completion
Michal Kazior michal.kaz...@tieto.com writes:
First 2 patches are simple fixes. Patch 3 isn't
strictly related to wmi-tlv but I decided to
include it anyway. Other patches gradually
implement wmi-tlv.
There's a bunch of false-positive checkpatch
warnings regarding `CHECK: No space is
When the channel switch has been made, a vif is now using
the channel context which was reserved. When that happens,
we need to update the channel context since its parameters
may change.
I hit a case in which I switched to a 40Mhz channel but the
reserved channel context was still on 20Mhz. The
Hello,
wifi driver wl1251 needs NVS calibration data for working. These
data are loaded by driver via request_firmware from userspace
file: ti-connectivity/wl1251-nvs.bin. In linux-fimrware git tree
there is generic wl1251-nvs.bin file which is used by default.
Driver wl1251 is used on Nokia
On Thursday 27 November 2014 15:21:44 Ming Lei wrote:
On Thu, Nov 27, 2014 at 10:06 PM, Pali Rohár
pali.ro...@gmail.com wrote:
Hello,
wifi driver wl1251 needs NVS calibration data for working.
These data are loaded by driver via request_firmware from
userspace file:
On Thu, 2014-11-27 at 14:39 +0100, Lorenzo Bianconi wrote:
Configure per packet Transmit Power Control (TPC) in lower drivers checking
if user_power_level has been set to IEEE80211_UNSET_POWER_LEVEL
Err, what? Why? how? what does this do?
johannes
--
To unsubscribe from this list: send the
On Thu, 2014-11-27 at 14:39 +0100, Lorenzo Bianconi wrote:
Configure per packet Transmit Power Control (TPC) in lower drivers checking
if user_power_level has been set to IEEE80211_UNSET_POWER_LEVEL
Err, what? Why? how? what does this do?
johannes
I would like to enable TPC in ath9k using
On Thu, Nov 27, 2014 at 10:43 PM, Pali Rohár pali.ro...@gmail.com wrote:
On Thursday 27 November 2014 15:21:44 Ming Lei wrote:
On Thu, Nov 27, 2014 at 10:06 PM, Pali Rohár
pali.ro...@gmail.com wrote:
Hello,
wifi driver wl1251 needs NVS calibration data for working.
These data are loaded
On Thu, Nov 27, 2014 at 03:43:23PM +0100, Pali Rohár wrote:
Which userspace helper programs for (automatic) firmware loading
are used? Can be udev configured to use own program for loading
firmware instead that udev integrated which looking for firmware
only in /lib/firmware files?
The
On Thu, Nov 27, 2014 at 03:43:23PM +0100, Pali Rohár wrote:
On Thursday 27 November 2014 15:21:44 Ming Lei wrote:
On Thu, Nov 27, 2014 at 10:06 PM, Pali Rohár
pali.ro...@gmail.com wrote:
Hello,
wifi driver wl1251 needs NVS calibration data for working.
These data are loaded by
On Thursday 27 November 2014 16:16:55 Greg Kroah-Hartman wrote:
On Thu, Nov 27, 2014 at 03:43:23PM +0100, Pali Rohár wrote:
On Thursday 27 November 2014 15:21:44 Ming Lei wrote:
On Thu, Nov 27, 2014 at 10:06 PM, Pali Rohár
pali.ro...@gmail.com wrote:
Hello,
wifi driver
On Thursday 27 November 2014 16:14:48 Greg Kroah-Hartman wrote:
On Thu, Nov 27, 2014 at 03:43:23PM +0100, Pali Rohár wrote:
Which userspace helper programs for (automatic) firmware
loading are used? Can be udev configured to use own program
for loading firmware instead that udev integrated
On Thu, Nov 27, 2014 at 04:22:58PM +0100, Pali Rohár wrote:
On Thursday 27 November 2014 16:16:55 Greg Kroah-Hartman wrote:
On Thu, Nov 27, 2014 at 03:43:23PM +0100, Pali Rohár wrote:
On Thursday 27 November 2014 15:21:44 Ming Lei wrote:
On Thu, Nov 27, 2014 at 10:06 PM, Pali Rohár
From: Johannes Berg johannes.b...@intel.com
One of the cases for an invalid channel definition is that
the channel pointer is NULL, in which case the warning is
a bit late since we'll dereference the pointer. Bail out
of the function upon warning about this.
Signed-off-by: Johannes Berg
On Mon, 2014-11-24 at 18:12 +0100, Felix Fietkau wrote:
Fixes a crash in nl80211_send_chandef, introduced in
commit c12bc4885f4b3bab0ed779c69d5d7e3223fa5003
mac80211: return the vif's chandef in ieee80211_cfg_get_channel()
I've fixed up the commit log myself and applied it, but I doubt we'll
From: Luciano Coelho luciano.coe...@intel.com
Signed-off-by: Luciano Coelho luciano.coe...@intel.com
---
nl80211.h | 119 +++---
1 file changed, 115 insertions(+), 4 deletions(-)
diff --git a/nl80211.h b/nl80211.h
index f7daae5..d775245
From: Luciano Coelho luciano.coe...@intel.com
Adds a netdetect option to the wowlan triggers that allows the user to
request network detection to be started when the device goes to
suspend mode.
Signed-off-by: Luciano Coelho luciano.coe...@intel.com
---
event.c | 30 ++-
info.c |
On 11/27/14 22:06, Luca Coelho wrote:
From: Luciano Coelholuciano.coe...@intel.com
Adds a netdetect option to the wowlan triggers that allows the user to
request network detection to be started when the device goes to
suspend mode.
So it can start heating up my backpack when I get home. Nice
Hi,
I have an X1 Carbon laptop with an intel 7260 chip.
The automatic firmware loading doesn't work (kernel 3.17.2). I get this
in dmesg:
[1.615155] iwlwifi :03:00.0: Direct firmware load for
iwlwifi-7260-10.ucode failed with error -2
The firmware then gets loaded by the userspace
On 28.11.2014 01:40, Hanno Böck wrote:
Hi,
I have an X1 Carbon laptop with an intel 7260 chip.
The automatic firmware loading doesn't work (kernel 3.17.2). I get this
in dmesg:
[1.615155] iwlwifi :03:00.0: Direct firmware load for
iwlwifi-7260-10.ucode failed with error -2
The
Radar detection happens before starting AP; so netdev carrier may be dormant
at this time. Remove this check from cfg80211_start_radar_detection.
Signed-off-by: Avinash Patil pat...@marvell.com
---
net/wireless/nl80211.c | 3 ---
1 file changed, 3 deletions(-)
diff --git
On Thu, 2014-11-27 at 22:29 +0100, Arend van Spriel wrote:
On 11/27/14 22:06, Luca Coelho wrote:
From: Luciano Coelholuciano.coe...@intel.com
Adds a netdetect option to the wowlan triggers that allows the user to
request network detection to be started when the device goes to
suspend
On 27 November 2014 at 13:30, Emmanuel Grumbach
emmanuel.grumb...@intel.com wrote:
When we want to calculate the minimal bandwidth needed for
a channel context, we need to take into account vifs that
have reserved the channel context.
I hit an issue with iwlwifi and channel switch as a client.
Michal Kazior michal.kaz...@tieto.com writes:
Hmm.. I have a couple of ideas:
[...]
2. Have a dedicatd pci-specific structure:
struct ath10k_pci_supported_chip {
u16 dev_id;
u32 chip_id;
};
struct ath10k_pci_supported_chip ath10k_pci_supported_chips[] = {
{
On Thu, Nov 27, 2014 at 5:35 PM, Luis R. Rodriguez mcg...@suse.com wrote:
On Thu, Nov 27, 2014 at 09:12:11AM +0200, Arik Nemtsov wrote:
On Wed, Nov 26, 2014 at 11:43 PM, Luis R. Rodriguez mcg...@suse.com wrote:
On Wed, Nov 26, 2014 at 4:35 PM, Luis R. Rodriguez mcg...@suse.com wrote:
We're
46 matches
Mail list logo
