1. 21 10月, 2015 1 次提交
  2. 08 10月, 2015 1 次提交
  3. 04 10月, 2015 1 次提交
    • L
      Bluetooth: btintel: Add iBT register access over HCI support · d06f107b
      Loic Poulain 提交于
      Add regmap ibt to support Intel Bluetooth silicon register access
      over HCI. Intel BT/FM combo chip allows to read/write some registers
      (e.g. FM registers) via its HCI interface.
      
      Read/Write operations are performed via a HCI transaction composed of
      a HCI command (host->controller) followed by a HCI command complete
      event (controller->host). Read/Write Command opcodes can be specified
      to the regmap init function.
      We define data formats which are intel/vendor specific.
      
      Register Read/Write HCI command payload (Host):
      Field: | REG ADDR | MODE | DATA_LEN | DATA... |
      size:  |   32b    |  8b  |    8b    |  8b*    |
      
      Register Read HCI command complete event payload (Controller):
      Field: | CMD STATUS | REG ADDR | DATA... |
      size:  |     8b     |   32b    |  8b*    |
      
      Register Write HCI command complete event payload (Controller):
      Field: | CMD_STATUS |
      size:  |     8b     |
      
      Since this payload is HCI encapsulated, Little Endian byte order is
      used.
      
      Write/Read Example:
      
      If we write 0x0000002a at address 0x00008c04, with opcode_write 0xfc5d,
      The resulting transaction is (btmon trace):
      
      < HCI Command (0x3f|0x005d) plen 10 [hci0]
              04 8c 00 00 02 04 2a 00 00 00
      > HCI Event (0x0e) plen 4
            Unknown (0x3f|0x005d) ncmd 1
              00
      
      Then, if we read the same register with opcode_read 0xfc5e:
      
      < HCI Command (0x3f|0x005e) plen 6 [hci0]
              04 8c 00 00 02 04
      > HCI Event (0x0e) plen 12 [hci0]
            Unknown (0x3f|0x005e) ncmd 1
              00 04 8c 00 00 2a 00 00 00
      Signed-off-by: NLoic Poulain <loic.poulain@intel.com>
      Signed-off-by: NMarcel Holtmann <marcel@holtmann.org>
      d06f107b
  4. 22 9月, 2015 1 次提交
  5. 11 8月, 2015 2 次提交
  6. 23 7月, 2015 1 次提交
  7. 14 5月, 2015 1 次提交
  8. 08 4月, 2015 12 次提交
  9. 04 12月, 2014 1 次提交
    • X
      Bluetooth: btmrvl add firmware dump support · dc759613
      Xinming Hu 提交于
      This patch adds firmware dump support for marvell
      bluetooth chipset. Currently only SD8897 is supported.
      This is implemented based on dev_coredump, a new mechnism
      introduced in kernel 3.18rc3
      
      Firmware dump can be trigger by
      echo 1 > /sys/kernel/debug/bluetooth/hci*/config/fw_dump
      and when the dump operation is completed, data can be read by
      cat /sys/class/devcoredump/devcd*/data
      
      We have prepared following script to divide fw memory
      dump data into multiple files based on memory type.
      
       [root]# cat btmrvl_split_dump_data.sh
       #!/bin/bash
       # usage: ./btmrvl_split_dump_data.sh dump_data
      
       fw_dump_data=$1
      
       mem_type="ITCM DTCM SQRAM APU CIU ICU MAC EXT7 EXT8 EXT9 EXT10 EXT11 EXT12 EXT13 EXTLAST"
      
       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: NXinming Hu <huxm@marvell.com>
      Signed-off-by: NCathy Luo <cluo@marvell.com>
      Signed-off-by: NAvinash Patil <patila@marvell.com>
      Reviewed-by: NJohannes Berg <johannes@sipsolutions.net>
      Reviewed-by: NMarcel Holtmann <marcel@holtmann.org>
      Signed-off-by: NAmitkumar Karwar <akarwar@marvell.com>
      Signed-off-by: NMarcel Holtmann <marcel@holtmann.org>
      dc759613
  10. 30 9月, 2014 1 次提交
  11. 03 7月, 2014 1 次提交
  12. 10 3月, 2014 1 次提交
  13. 12 6月, 2013 1 次提交
  14. 19 1月, 2013 1 次提交
    • J
      tty: Added a CONFIG_TTY option to allow removal of TTY · 4f73bc4d
      Joe Millenbach 提交于
      The option allows you to remove TTY and compile without errors. This
      saves space on systems that won't support TTY interfaces anyway.
      bloat-o-meter output is below.
      
      The bulk of this patch consists of Kconfig changes adding "depends on
      TTY" to various serial devices and similar drivers that require the TTY
      layer.  Ideally, these dependencies would occur on a common intermediate
      symbol such as SERIO, but most drivers "select SERIO" rather than
      "depends on SERIO", and "select" does not respect dependencies.
      
      bloat-o-meter output comparing our previous minimal to new minimal by
      removing TTY.  The list is filtered to not show removed entries with awk
      '$3 != "-"' as the list was very long.
      
      add/remove: 0/226 grow/shrink: 2/14 up/down: 6/-35356 (-35350)
      function                                     old     new   delta
      chr_dev_init                                 166     170      +4
      allow_signal                                  80      82      +2
      static.__warned                              143     142      -1
      disallow_signal                               63      62      -1
      __set_special_pids                            95      94      -1
      unregister_console                           126     121      -5
      start_kernel                                 546     541      -5
      register_console                             593     588      -5
      copy_from_user                                45      40      -5
      sys_setsid                                   128     120      -8
      sys_vhangup                                   32      19     -13
      do_exit                                     1543    1526     -17
      bitmap_zero                                   60      40     -20
      arch_local_irq_save                          137     117     -20
      release_task                                 674     652     -22
      static.spin_unlock_irqrestore                308     260     -48
      Signed-off-by: NJoe Millenbach <jmillenbach@gmail.com>
      Reviewed-by: NJamey Sharp <jamey@minilop.net>
      Reviewed-by: NJosh Triplett <josh@joshtriplett.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      4f73bc4d
  15. 18 7月, 2012 1 次提交
  16. 21 11月, 2011 1 次提交
  17. 13 4月, 2011 1 次提交
  18. 24 2月, 2011 1 次提交
    • P
      Bluetooth: btwilink driver · 363907af
      Pavan Savoy 提交于
      This is the bluetooth protocol driver for the TI WiLink7 chipsets.
      Texas Instrument's WiLink chipsets combine wireless technologies
      like BT, FM, GPS and WLAN onto a single chip.
      
      This Bluetooth driver works on top of the TI_ST shared transport
      line discipline driver which also allows other drivers like
      FM V4L2 and GPS character driver to make use of the same UART interface.
      
      Kconfig and Makefile modifications to enable the Bluetooth
      driver for Texas Instrument's WiLink 7 chipset.
      Signed-off-by: NPavan Savoy <pavan_savoy@ti.com>
      Acked-by: NGustavo F. Padovan <padovan@profusion.mobi>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      363907af
  19. 22 7月, 2010 1 次提交
  20. 30 1月, 2010 1 次提交
  21. 23 8月, 2009 4 次提交
  22. 30 11月, 2008 1 次提交
  23. 18 8月, 2008 1 次提交
    • M
      [Bluetooth] Add SCO support to btusb driver · 9bfa35fe
      Marcel Holtmann 提交于
      The new generic driver for Bluetooth USB devices was missing proper
      SCO support. The driver now claims the second interface for these USB
      devices to allow the flow of SCO packets. It also handles switching
      of the alternate setting and re-submission of isochronous URBs.
      
      The btusb driver is now a full replacement for hci_usb and thus the
      experimental tag has been removed and this driver is promoted as
      preferred one.
      Signed-off-by: NMarcel Holtmann <marcel@holtmann.org>
      9bfa35fe
  24. 15 7月, 2008 1 次提交
  25. 11 6月, 2008 1 次提交