1. 10 1月, 2015 1 次提交
  2. 27 11月, 2014 1 次提交
  3. 25 11月, 2014 1 次提交
  4. 04 11月, 2014 2 次提交
  5. 20 10月, 2014 1 次提交
  6. 29 9月, 2014 1 次提交
  7. 24 9月, 2014 4 次提交
  8. 30 8月, 2014 1 次提交
    • A
      usbtest: Add interrupt EP testcases · 457a0955
      Amit Virdi 提交于
      Two simple test cases for interrupt endpoints are added to the usbtest.c file.
      These are simple non-queued interrupt IN and interrupt OUT transfers. Currently,
      only gadget zero is capable of executing the interrupt EP test cases. However,
      extending the same to other gadgets is extremely simple and can be done
      on-demand.
      
      The two new tests added are
        - Test 25: To verify Interrupt OUT transfer
        - Test 26: To verify Interrupt IN transfer
      
      Since the default value of wMaxPacketSize is set as 1024, so interrupt
      IN transfers must be specified with the size parameter = multiple of
      1024. Otherwise the default value (512) in the usbtest application fails
      the transfer. See [RUN 4] for sample logs
      
      The application logs (usbtest) and corresponding kernel logs are as
      following:
      
      [Run 1]
      ./testusb -a -c 10 -s 2048 -t 26 -v 511
      usbtest 7-1:3.0: TEST 26: read 2048 bytes 10 times
      
      [Run 2]
      ./testusb -a -c 10 -s 1024 -t 25 -v 511
      usbtest 7-1:3.0: TEST 25: write 1024 bytes 10 times
      
      [Run 3]
      ./testusb -a -c 10 -s 1098 -t 25 -v 511
      usbtest 7-1:3.0: TEST 25: write 1098 bytes 10 times
      
      [Run 4 - Failure case scenario]
      ./testusb -a  -t 26
      unknown speed   /dev/bus/usb/007/004    0
      /dev/bus/usb/007/004 test 26 --> 75 (Value too large for defined data type)
      
      usbtest 7-1:3.0: TEST 26: read 512 bytes 1000 times
      usb 7-1: test26 failed, iterations left 999, status -75 (not 0)
      Signed-off-by: NAmit Virdi <amit.virdi@st.com>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      457a0955
  9. 27 8月, 2014 1 次提交
  10. 23 7月, 2014 1 次提交
  11. 18 7月, 2014 1 次提交
    • P
      USB: Add LVS Test device driver · ce21bfe6
      Pratyush Anand 提交于
      OTG3 and EH Compliance Plan 1.0 talks about Super Speed OTG Verification
      system (SS-OVS) which consists of an excersizer and analyzer.
      
      USB Compliance Suite from Lecroy or Ellisys can act as such SS-OVS for
      Link Layer Validation (LVS).
      
      Some modifications are needed for an embedded Linux USB host to pass all
      these tests.  Most of these tests require just Link to be in U0. They do
      not work with default Linux USB stack since, default stack does port
      reset and then starts sending setup packet, which is not expected by
      Link Layer Validation (LVS) device of Lecroy Compliance Suit.  Then,
      There are many Link Layer Tests which need host to generate specific
      traffic.
      
      This patch supports specific traffic generation cases. As of now all the
      host Lecroy Link Layer-USBIF tests (except TD7.26) passes
      with this patch for single run using  Lecroy USB Compliance Suite
      Version 1.98 Build 239 and Lecroy USB Protocol Analyzer version 4.80
      Build 1603. Therefore patch seems to be a good candidate for inclusion.
      Further modification can be done on top of it.
      
      lvstest driver will not bind to any device by default. It can bind
      manually to a super speed USB host controller root hub. Therefore, regular
      hub driver must be unbound before this driver is bound. For example, if
      2-0:1.0 is the xhci root hub, then execute following to unbind hub driver.
      
       echo 2-0:1.0 > /sys/bus/usb/drivers/hub/unbind
      
      Then write Linux Foundation's vendor ID which is used by root hubs and
      SS root hub's device ID into new_id file. Writing IDs into new_id file
      will also bind the lvs driver with any available SS root hub interfaces.
      
       echo "1D6B 3" > /sys/bus/usb/drivers/lvs/new_id
      
      Now connect LVS device with root hub port.
      
      Test case specific traffic can be generated as follows whenever needed:
      
      1. To issue "Get Device descriptor" command for TD.7.06:
       echo  > /sys/bus/usb/devices/2-0\:1.0/get_dev_desc
      
      2. To set U1 timeout to 127 for TD.7.18
       echo 127 > /sys/bus/usb/devices/2-0\:1.0/u1_timeout
      
      3. To set U2 timeout to 0 for TD.7.18
       echo 0 > /sys/bus/usb/devices/2-0\:1.0/u2_timeout
      
      4. To issue "Hot Reset" for TD.7.29
       echo  > /sys/bus/usb/devices/2-0\:1.0/hot_reset
      
      5. To issue "U3 Entry" for TD.7.35
       echo  > /sys/bus/usb/devices/2-0\:1.0/u3_entry
      
      6. To issue "U3 Exit" for TD.7.36
       echo  > /sys/bus/usb/devices/2-0\:1.0/u3_exit
      Signed-off-by: NPratyush Anand <pratyush.anand@st.com>
      Acked-by: NAlan Stern <stern@rowland.harvard.edu>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      ce21bfe6
  12. 12 7月, 2014 1 次提交
  13. 10 7月, 2014 1 次提交
  14. 18 6月, 2014 1 次提交
  15. 28 5月, 2014 7 次提交
  16. 25 4月, 2014 5 次提交
  17. 04 3月, 2014 1 次提交
  18. 12 2月, 2014 2 次提交
  19. 09 1月, 2014 1 次提交
  20. 04 1月, 2014 3 次提交
  21. 20 12月, 2013 1 次提交
  22. 19 12月, 2013 2 次提交