1. 03 3月, 2010 2 次提交
  2. 12 12月, 2009 1 次提交
  3. 10 10月, 2009 1 次提交
  4. 13 7月, 2009 1 次提交
  5. 16 6月, 2009 4 次提交
    • A
      musb: add high bandwidth ISO support · a483d706
      Ajay Kumar Gupta 提交于
      Tested on OMAP3 host side with Creative (Live! Cam Optia) USB camera
      which uses high bandwidth isochronous IN endpoints.  FIFO mode 4 is
      updated to provide the needed 4K endpoint buffer without breaking
      the g_nokia composite gadget configuration.  (This is the only
      gadget driver known to use enough endpoints to notice the change.)
      Signed-off-by: NAjay Kumar Gupta <ajay.gupta@ti.com>
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      a483d706
    • D
      musb: otg timer cleanup · f7f9d63e
      David Brownell 提交于
      Minor cleanup of OTG timer handling:
          * unify decls for OTG time constants, in the core header
          * set up and use that timer in a more normal way
          * move to the driver struct, so it's usable outside core
      
      And tighten use and setup of T(a_wait_bcon) so that if it's used,
      it's always valid.  (If that timer expires, the A-device will
      stop powering VBUS.  For non-OTG systems, that will be a surprise.)
      No behavioral changes, other than more consistency when applying
      that core HNP timeout.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      f7f9d63e
    • D
      musb: proper hookup to transceiver drivers · 84e250ff
      David Brownell 提交于
      Let the otg_transceiver in MUSB be managed by an external driver;
      don't assume it's integrated.  OMAP3 chips need it to be external,
      and there may be ways to interact with the transceiver which add
      functionality to the system.
      
      Platform init code is responsible for setting up the transeciver,
      probably using the NOP transceiver for integrated transceivers.
      External ones will use whatever the board init code provided,
      such as twl4030 or something more hands-off.
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      84e250ff
    • S
      musb_gadget: fix unhandled endpoint 0 IRQs · a5073b52
      Sergei Shtylyov 提交于
      The gadget EP0 code routinely ignores an interrupt at end of
      the data phase because of musb_g_ep0_giveback() resetting the
      state machine to "idle, waiting for SETUP" phase prematurely.
      
      The driver also prematurely leaves the status phase on
      receiving the SetupEnd interrupt.
      
      As there were still unhandled endpoint 0 interrupts happening
      from time to time after fixing these issues, there turned to
      be yet another culprit: two distinct gadget states collapsed
      into one.
      
      The (missing) state that comes after STATUS IN/OUT states was
      typically indiscernible from them since the corresponding
      interrupts tend to happen within too little period of time
      (due to only a zero-length status packet in between) and so
      they got coalesced; yet this state is not the same as the next
      one which is associated with the reception of a SETUP packet.
      
      Adding this extra state seems to have fixed the rest of the
      unhandled interrupts that generic_interrupt() and
      davinci_interrupt() hid by faking their result and only
      emitting a debug message -- so, stop doing that.
      Signed-off-by: NSergei Shtylyov <sshtylyov@ru.mvista.com>
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      a5073b52
  6. 25 3月, 2009 2 次提交
  7. 08 1月, 2009 3 次提交
  8. 22 8月, 2008 1 次提交
  9. 14 8月, 2008 2 次提交