- 20 Mar, 2013 16 commits
-
-
Johannes Berg authored
The RF-kill wakeup trigger flag is set in the wrong command, which means it won't work. Also fix the comment in the TCP wakeup trigger code -- the firmware was changed to look at all the different trigger flags. Reviewed-by:
Emmanuel Grumbach <emmanuel.grumbach@intel.com> Signed-off-by:
Johannes Berg <johannes.berg@intel.com>
-
Emmanuel Grumbach authored
We should disable MIMO only if bt_traffic_load goes up to 3. Signed-off-by:
-
Emmanuel Grumbach authored
This is the right source of information for the valid Tx antennas, not the NVM. Signed-off-by:
-
Emmanuel Grumbach authored
This data should taken from TLVs and not from the NVM. This is true for the value written in CSR_HW_IF_CONFIG_REG too. Also, no need to set the CSR_HW_IF_CONFIG_REG_BIT_MAC_SI bit for 7000 devices which are the only devices currently supported. Signed-off-by:
-
Johannes Berg authored
In firmware "listener" (monitor) mode, we still need to open up the filters with the filter flags to receive all frames. Reviewed-by:
Ilan Peer <ilan.peer@intel.com> Reviewed-by:
-
Emmanuel Grumbach authored
Signed-off-by:
-
Emmanuel Grumbach authored
This has valuable data about RFkill state seen from the fw side. Signed-off-by:
-
Stanislaw Gruszka authored
5ghz_disable has no effect any longer, that was changed during refactoring of EEPROM reading/parsing. Remove it, wpa_supplicant allow now to specify frequencies, on which device will operate. Signed-off-by:
Stanislaw Gruszka <sgruszka@redhat.com> Reviewed-by:
-
Ilan Peer authored
1. Quota for the monitor interface should be added only if there is a channel context assigned to the interface. 2. In the unassign channel context flow, need to remove the quota for the monitor interface binding, before unbinding. Signed-off-by:
-
Andrei Epure authored
Signed-off-by:
Andrei Epure <epure.andrei@gmail.com> Reviewed-by:
-
Ilan Peer authored
Signed-off-by:
-
Emmanuel Grumbach authored
This feature is not implemented yet in firmware. Signed-off-by:
-
Emmanuel Grumbach authored
The masks were wrong. They should be 0xffffffff when SCO, HID or SNIFF profiles are used. They should be 0xffff0000 in any other case (default) to get a bit more throughput when the BT profile allows for it. Fix a debug print on the way. Signed-off-by:
-
Ilan Peer authored
Mostly for debugging purposes Signed-off-by:
-
Johannes Berg authored
In AP mode, don't attempt to program GTKs into the device, they're used for TX only so not needed and programming them causes error messages. Also, in this case and if key programming fails, avoid trying to remove the key that isn't present later. Reviewed-by:
-
Emmanuel Grumbach authored
The code removed in this patch was used for bring up on older NICs. No MVM capable fw will ever be released for older NICs, so remove that code. Signed-off-by:
-
- 06 Mar, 2013 24 commits
-
-
Emmanuel Grumbach authored
The SCD byte count layout is decided by the configuration done in fw, it is then logical to export it as a TLV flag and not per HW SKU. Signed-off-by:
-
Amnon Paz authored
Fix a bug in writing to indirect (periphery) registers; although writes seem successful the data is not written to the desired address). Also fix address mask for HBUS_TARG_PRPH_RADDR and HBUS_TARG_PRPH_WADDR registers. Signed-off-by:
Amnon Paz <amnonX.paz@intel.com> Reviewed-by:
-
Emmanuel Grumbach authored
This allows to test fw restart flow. The hook in transport layer doesn't really make the fw assert. Moving this hook to the op_mode allows to use the fw API to actually send a host command that will make the fw assert. Change the restart_fw module parameter to be a boolean on the way. Signed-off-by:
-
Emmanuel Grumbach authored
The firmware tells the driver to what MACs the received frame belongs (based on the time slot in which it was received). Note that there can be several MACs if they share the same binding. Signed-off-by:
-
Emmanuel Grumbach authored
This will allow to track how BT core updates the driver. This is required to debug the BT Coexistence mechanism. Signed-off-by:
-
Emmanuel Grumbach authored
When BT traffic load gets higher, we want to avoid using the shared antenna. In order to do so, we need to tell the AP that we don't support MIMO any more, or at least not all the time: in short, use the SMPS to achieve this. Signed-off-by:
-
Emmanuel Grumbach authored
The BT-Coex notification is sent by the fw when there are updates wrt. BT activity. Driver action might be taken based on the info in this notification. For now, update the Ack/Cts_kill_msk if HID / SCO / A2DP profiles are active. Signed-off-by:
-
Emmanuel Grumbach authored
Send the PRIO table before the calibrations. This table tells the fw what priority to give to what (WiFi / BT) according to events. Send a hardcoded BT_COEX command to the fw to enable basic BT coexistence. Signed-off-by:
-
Emmanuel Grumbach authored
This is the API to tell the fw to handle the BT Coexistence. Signed-off-by:
-
Emmanuel Grumbach authored
Then the transport can print it nicely in its debug prints. Signed-off-by:
-
Johannes Berg authored
If all the pieces of iwlwifi are built into the kernel then there's no need for it to export its symbols to other modules, so prevent that. Reviewed-by:
-
Johannes Berg authored
Now that we have two drivers (DVM and MVM) stop selecting the DVM one (but make it default) and allow enabling only the MVM driver if so desired. Add a warning for the case of having neither DVM nor MVM enabled -- that's useless. Reviewed-by:
-
Dor Shaish authored
Signed-off-by:
Dor Shaish <dor.shaish@intel.com> Reviewed-by:
-
Johannes Berg authored
When modifying a MAC, we update its beacon system time which is taken as a base to calculate TBTT. The firmware doesn't use the new timestamp because the time is never used after the MAC and broadcast station were added, but it is safer to not rely on this and avoids the overhead of reading the register every time the MAC is updated. Reviewed-by:
-
Emmanuel Grumbach authored
Newer devices can work on different buses. This means that their configuration can be shared between different buses. Hence the configuration structures should exported to all the buses and not only to PCIE. Change this. Note that this requires all the fields to be the same amongst the buses. If differences will appear, we can always define a part that is bus dependent. Today, this is not needed. Signed-off-by:
-
Emmanuel Grumbach authored
All the data coming from the fw must have a length that is multiple of 4. This doesn't change anything to the way we handle the notification. Signed-off-by:
-
Eytan Lifshitz authored
Update the NVM parsing functions to add VHT capabilities; they are only added for 5 GHz, of course. This assumes that all devices with NVM reading (rather than EEPROM) that support 5 GHz have VHT, which is true right now. Signed-off-by:
Eytan Lifshitz <eytan.lifshitz@intel.com> Reviewed-by:
-
Johannes Berg authored
When a station is added, we need to tell the firmware what the SMPS settings and number of streams are. After having the initial data, the firmware will track future changes by itself. Reviewed-by:
-
Johannes Berg authored
With remote wake, the firmware creates a TCP connection and sends some configurable data on it, until a special TCP data packet from the server is received that triggers a wakeup. The configuration is a bit tricky because it is based on packet pattern matching but this is hidden in the driver and the exposed API in cfg80211 is just based on the required TCP connection parameters. Reviewed-by:
-
Wei Yongjun authored
This removes an open coded simple_open() function and replaces file operations references to the function with simple_open() instead. Signed-off-by:
Wei Yongjun <yongjun_wei@trendmicro.com.cn> Reviewed-by:
-
Johannes Berg authored
Instead of using (char *)__get_dynamic_array use __get_str. The latter is actually a macro that expands to the former in the code, but trace-cmd in userspace can parse __get_str only. Reviewed-by:
-
Johannes Berg authored
All hardware after 4965 supports this. It's likely that it wasn't set because for 4965 it was irrelevant (HT is only supported on 5 GHz there) and then never updated. Reviewed-by:
-
Emmanuel Grumbach authored
mac80211 tells us when we need to dump the frames from the AGG queue instead of releasing them as single MPDUs. Being able to differentiate between the different cases (IEEE80211_AMPDU_TX_STOP_*) allows us to handle races better. When the station is removed, mac80211 asks to flush and removes the station right away. This allows to avoid a case where we still have frames in AGG queues, but the station has been remove already. Note that we can have frames on the shared queues, but this is not a problem: the station in the fw will be kept until all the frames on the shared queues have been drained. AGG queues are a special case since they are dynamically allocated. Signed-off-by:
-
Ilan Peer authored
Use the number of addresses (max 5) from the NVM instead of limiting to 2 artificially. Signed-off-by:
-
