1. 21 7月, 2015 9 次提交
  2. 15 6月, 2015 1 次提交
  3. 08 6月, 2015 4 次提交
  4. 03 6月, 2015 2 次提交
    • A
      mwifiex: device dump support via devcoredump framework · 57670ee8
      Amitkumar Karwar 提交于
      Currently device dump generated in the driver is retrieved
      using ethtool set/get dump commands. We will get rid of
      ethtool approach and use devcoredump framework.
      
      Device dump can be trigger by
      cat /debugfs/mwifiex/mlanX/device_dump
      and when the dump operation is completed, data can be read by
      cat /sys/class/devcoredump/devcdX/data
      
      We have prepared following script to split device dump data
      into multiple files.
      
       [root]# cat mwifiex_split_dump_data.sh
       #!/bin/bash
       # usage: ./mwifiex_split_dump_data.sh dump_data
      
       fw_dump_data=$1
      
       mem_type="driverinfo ITCM DTCM SQRAM APU CIU ICU MAC"
      
       for name in ${mem_type[@]}
       do
           sed -n "/Start dump $name/,/End dump/p" $fw_dump_data  > tmp.$name.log
           if [ ! -s tmp.$name.log ]
           then
               rm -rf tmp.$name.log
           else
               #Remove the describle info "Start dump" and "End dump"
               sed '1d' tmp.$name.log | sed '$d' > /data/$name.log
               if [ -s /data/$name.log ]
               then
                   echo "generate /data/$name.log"
               else
                   sed '1d' tmp.$name.log | sed '$d' > /var/$name.log
                   echo "generate /var/$name.log"
               fi
               rm -rf tmp.$name.log
           fi
       done
      Signed-off-by: NAmitkumar Karwar <akarwar@marvell.com>
      Signed-off-by: NCathy Luo <cluo@marvell.com>
      Signed-off-by: NKalle Valo <kvalo@codeaurora.org>
      57670ee8
    • A
      mwifiex: use generic name 'device dump' · fc697159
      Amitkumar Karwar 提交于
      Currently we are dumping driver information also inside
      firmware dump API. We will call it as device dump and
      dump driver and firmware data separately.
      Signed-off-by: NAmitkumar Karwar <akarwar@marvell.com>
      Signed-off-by: NCathy Luo <cluo@marvell.com>
      Signed-off-by: NKalle Valo <kvalo@codeaurora.org>
      fc697159
  5. 26 5月, 2015 3 次提交
  6. 30 3月, 2015 2 次提交
    • T
      cfg80211: pass name_assign_type to rdev_add_virtual_intf() · 6bab2e19
      Tom Gundersen 提交于
      This will expose in /sys whether the ifname of a device is set by
      userspace or generated by the kernel. The latter kind (wlanX, etc)
      is not deterministic, so userspace needs to rename these devices
      to names that are guaranteed to stay the same between reboots. The
      former, however should never be renamed, so userspace needs to be
      able to reliably tell the difference.
      
      Similar functionality was introduced for the rtnetlink core in
      commit 5517750f ("net: rtnetlink - make create_link take name_assign_type")
      Signed-off-by: NTom Gundersen <teg@jklm.no>
      Cc: Kalle Valo <kvalo@qca.qualcomm.com>
      Cc: Brett Rudley <brudley@broadcom.com>
      Cc: Arend van Spriel <arend@broadcom.com>
      Cc: Franky (Zhenhui) Lin <frankyl@broadcom.com>
      Cc: Hante Meuleman <meuleman@broadcom.com>
      Cc: Johannes Berg <johannes@sipsolutions.net>
      [reformat changelog to fit 72 cols]
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      6bab2e19
    • M
      mwifiex: Fix issue in the SDIO reset path of mwifiex. · 2f5872b6
      Maithili Hinge 提交于
      SDIO reset was not happening properly on mwifiex as cancel_work_sync
      in mwifiex_sdio_remove used to kill the calling work function itself.
      Due to this, the interface was not getting removed and card was not
      getting added again. Reset work function has been made independent
      of adapter variable and cancel_work_sync has been moved to cleanup
      function.
      Signed-off-by: NMaithili Hinge <maithili@marvell.com>
      Signed-off-by: NAmitkumar Karwar <akarwar@marvell.com>
      Signed-off-by: NKalle Valo <kvalo@codeaurora.org>
      2f5872b6
  7. 17 3月, 2015 7 次提交
  8. 27 2月, 2015 2 次提交
  9. 29 1月, 2015 10 次提交