1. 29 Feb, 2016 5 commits
    • Peter Chen's avatar
      doc: usb: ci-hdrc-usb2: add property non-zero-ttctrl-ttha · 4670ba6c
      Peter Chen authored
      If this property is not set, the max packet size is 1023 bytes, and if
      the total of packet size for pervious transactions are more than 256 bytes,
      it can't accept any transactions within this frame. The use case is single
      transaction, but higher frame rate.
      
      If this property is set, the max packet size is 188 bytes, it can handle
      more transactions than above case, it can accept transactions until it
      considers the left room size within frame is less than 188 bytes, software
      needs to make sure it does not send more than 90%
      maximum_periodic_data_per_frame. The use case is multiple transactions, but
      less frame rate.
      Signed-off-by: default avatarPeter Chen <peter.chen@nxp.com>
      4670ba6c
    • Peter Chen's avatar
      usb: chipidea: add system interface for ttctrl.ttha · aa738187
      Peter Chen authored
      In chipidea IP RTL, there is a very limited design for siTD, the detail
      like below:
      There is no Max Packet Size at siTD, so it uses one constant for both
      Max Packet Size for packet and the packet size for the last transaction
      when considering schedule.
      If the ttctrl.ttha does not match against Hub Address field in siTD,
      this constant is 188 bytes, else this constant is 1023 bytes.
      
      If the ttctrl.ttha is non-zero value, RTL will use 188 as this constant,
      so it will lose the data if the packet size is larger than 188 bytes, eg,
      if we playback a wav which format is 48khz, 16 bits, 2 channels, the
      packet size will be 192bytes, but the controller will only send 188 bytes
      for this packet, the noise will be heared using USB audio card.
      The use case is single transaction, but higher frame rate.
      
      If the ttctr.ttha is zero value, we can send 1023 bytes within one
      transaction, but the controller will not accept the coming tranaction
      if it considers the schedule time is less than 1023 bytes. So the
      limitation is we can't schedule as many as transactions within frame.
      If the total bytes is already 256 bytes for previous transactions within
      frame, it can't accept another transaction. The use case is multiple
      transactions, but less frame rate.
      Signed-off-by: default avatarPeter Chen <peter.chen@nxp.com>
      aa738187
    • Li Jun's avatar
      usb: chipidea: udc: remove unused value assignment · 34d5732d
      Li Jun authored
      retval is assigned to be -EOVERFLOW but is overwritten later before
      it's used, remove this unused value assignment.
      Signed-off-by: default avatarLi Jun <jun.li@nxp.com>
      Signed-off-by: default avatarPeter Chen <peter.chen@nxp.com>
      34d5732d
    • Stefan Wahren's avatar
      dt-bindings: ci-hdrc-usb2: add missing compatibles · 6a6319f4
      Stefan Wahren authored
      This patch adds the missing compatible strings from ci_hdrc_imx.
      Signed-off-by: default avatarStefan Wahren <stefan.wahren@i2se.com>
      Signed-off-by: default avatarPeter Chen <peter.chen@nxp.com>
      6a6319f4
    • Stefan Wahren's avatar
      usb: chipidea: add CI_HDRC_TURN_VBUS_EARLY_ON for imx23 · 81345722
      Stefan Wahren authored
      Until now the imx23 uses the imx27 platform flag. But the
      imx23 needs the flag CI_HDRC_TURN_VBUS_EARLY_ON, too. So
      fix this by adding a separate platform flag.
      Suggested-by: default avatarPeter Chen <peter.chen@nxp.com>
      Signed-off-by: default avatarStefan Wahren <stefan.wahren@i2se.com>
      Signed-off-by: default avatarPeter Chen <peter.chen@nxp.com>
      81345722
  2. 21 Feb, 2016 9 commits
  3. 20 Feb, 2016 1 commit
  4. 15 Feb, 2016 25 commits