1. 02 3月, 2015 2 次提交
    • E
      iwlwifi: mvm: add the cause of the firmware dump in the dump · b6eaa45a
      Emmanuel Grumbach 提交于
      Now that the firmware dump can be triggered by events in
      the code and not only the user or an firmware ASSERT, we
      need a way to know why the firmware dump was triggered.
      Add a section in the dump file for that.
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      b6eaa45a
    • E
      iwlwifi: mvm: add framework for triggers for fw dump · d2709ad7
      Emmanuel Grumbach 提交于
      Most of the time, the issues we want to debug with the
      firmware dump mechanism are transient. It is then very
      hard to stop the recording on time and get meaningful
      data.
      In order to solve this, I add here an infrastucture
      of triggers. The user will supply a list of triggers
      that will start / stop the recording. We have two types
      of triggers: start and stop. Start triggers can start a
      specific configuration. The stop triggers will be able to
      kick the collection of the data with the currently running
      configuration. These triggers are given to the driver by
      the .ucode file - just like the configuration.
      
      In the next patches, I'll add triggers in the code.
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      d2709ad7
  2. 22 1月, 2015 4 次提交
  3. 29 12月, 2014 2 次提交
  4. 01 12月, 2014 1 次提交
  5. 24 11月, 2014 2 次提交
  6. 29 10月, 2014 2 次提交
  7. 16 9月, 2014 1 次提交
  8. 14 9月, 2014 2 次提交
  9. 04 9月, 2014 5 次提交
  10. 23 7月, 2014 2 次提交
  11. 21 7月, 2014 1 次提交
  12. 08 7月, 2014 3 次提交
  13. 25 6月, 2014 1 次提交
  14. 16 5月, 2014 1 次提交
  15. 13 5月, 2014 1 次提交
  16. 07 5月, 2014 1 次提交
  17. 14 4月, 2014 3 次提交
  18. 13 4月, 2014 1 次提交
  19. 19 3月, 2014 3 次提交
    • E
      iwlwifi: mvm: add missing include · 192c80a2
      Emmanuel Grumbach 提交于
      This fixes the build for powerpc:
      
      After merging the final tree, today's linux-next build (powerpc allyesconfig)
      failed like this:
      
      drivers/net/wireless/iwlwifi/mvm/debugfs.c: In function 'iwl_dbgfs_fw_error_dump_release':
      drivers/net/wireless/iwlwifi/mvm/debugfs.c:161:2: error: implicit declaration of function 'vfree' [-Werror=implicit-function-declaration]
        vfree(file->private_data);
        ^
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      192c80a2
    • E
      iwlwifi: mvm: BT Coex - add debugfs hook to set BT Tx priority · cdb00563
      Emmanuel Grumbach 提交于
      In order to debug the firmware, we need to be able to set
      the BT priority of WiFi packets. This priority is set based
      on the type of the packet (control frames, EAPOL etc...).
      For debugging purposes, allow to override this priority by
      a debugfs controlled value.
      Enable this feature that needs this priority to be able to
      test it.
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      cdb00563
    • E
      iwlwifi: mvm: send udev event upon firmware error to dump logs · 1bd3cbc1
      Emmanuel Grumbach 提交于
      When the firmware asserts, the driver will dump the firmware
      state to an internal buffer. This buffer is kept aside until
      it is dumped through debugfs. Once an external application
      fetched the data, the buffer is freed and a new buffer can
      be allocated in case another assert occurs.
      
      A udev event is sent to trigger an external application.
      
      A simple rule like:
      DRIVER=="iwlwifi", ACTION=="change", RUN+="/sbin/dump_sram.sh"
      
      can fetch the data from debugfs.
      
      Here is my dump_sram.sh:
      
      phyname=$(basename ${DEVPATH})
      date=$(date +%F_%H_%M)
      filename=/var/log/iwl-sram-${phyname}-${date}.bin
      cat /sys/kernel/debug/ieee80211/${phyname}/iwlwifi/iwlmvm/fw_error_dump > ${filename}
      
      The current SRAM size is 80KB so, currently:
      $ ls -lh iwl-sram-phy0-2014-03-16_13_14.bin
      -rw-r--r-- 1 emmanuel emmanuel 81K Mar 16 13:15 iwl-sram-phy0-2014-03-16_13_14.bin
      
      and after compression:
      $ ls -lh iwl-sram-phy0-2014-03-16_13_14.bin.xz
      -rw-r--r-- 1 emmanuel emmanuel 13K Mar 16 13:15 iwl-sram-phy0-2014-03-16_13_14.bin.xz
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      1bd3cbc1
  20. 12 3月, 2014 1 次提交
    • E
      iwlwifi: mvm: BT Coex add support for Co-running block · b9fae2d5
      Emmanuel Grumbach 提交于
      7265 features a new calibration which is called antenna
      coupling. The purpose of this calibration (which isn't
      really a calibration), is to measure the isolation between
      the antennas and that can give us useful information for
      the Coex modules.
      
      With this information, we can tune the LookUpTables (LUTs)
      that define the BT / WiFi contention policy.
      
      The LUTs currently contain dummy values - but they will be
      updated soon.
      
      While at it, change the current code to stop duplicate the
      host command while sending. This was needed back then, when
      the command was short enough to be allocated on the stack.
      Since then, the command grew a lot and is now allocated on
      the heap - hence we can use the NOCOPY option instead.
      Signed-off-by: NEmmanuel Grumbach <emmanuel.grumbach@intel.com>
      b9fae2d5
  21. 09 3月, 2014 1 次提交