1. 31 8月, 2012 1 次提交
    • K
      ARM: shmobile: mackerel: fixup usb module order · e26a6038
      Kuninori Morimoto 提交于
      renesas_usbhs driver can play role as both Host and Gadget.
      In case of Gadget, it requires not only renesas_usbhs
      but also usb gadget module (like g_ether).
      So, renesas_usbhs driver calls usb_add_gadget_udc() on probe time.
      
      Because of this behavior,
      Host port plays also Gadget role if kernel has both Host/Gadget support.
      
      In mackerel case, from 0ada2da5
      (ARM: mach-shmobile: mackerel: use renesas_usbhs instead of r8a66597_hcd)
      usb0 plays Gadget role, and usb1 plays Host role,
      and current mackerel board probes as usb1 -> usb0.
      Thus, 1st installed usb gadget module (like g_ether) will be
      assigned to usb1 (= usb Host port), and 2nd module to usb0 (= usb Gadget port).
      It is very confusable for user.
      This patch fixup usb modes probing order as usb0 -> usb1.
      Signed-off-by: NKuninori Morimoto <kuninori.morimoto.gx@renesas.com>
      Signed-off-by: NSimon Horman <horms@verge.net.au>
      e26a6038
  2. 07 7月, 2012 1 次提交
  3. 01 7月, 2012 1 次提交
  4. 30 6月, 2012 1 次提交
  5. 20 6月, 2012 1 次提交
  6. 13 5月, 2012 3 次提交
  7. 08 5月, 2012 1 次提交
  8. 13 4月, 2012 2 次提交
  9. 27 3月, 2012 1 次提交
  10. 13 3月, 2012 14 次提交
  11. 07 3月, 2012 1 次提交
  12. 03 2月, 2012 1 次提交
  13. 26 1月, 2012 1 次提交
  14. 19 1月, 2012 2 次提交
  15. 18 1月, 2012 1 次提交
  16. 03 1月, 2012 1 次提交
  17. 20 12月, 2011 1 次提交
  18. 24 11月, 2011 1 次提交
  19. 04 11月, 2011 3 次提交
  20. 27 10月, 2011 1 次提交
  21. 22 10月, 2011 1 次提交
    • M
      ARM: mach-shmobile: sh7372 A4R support (v4) · 382414b9
      Magnus Damm 提交于
      This change adds support for the sh7372 A4R power domain.
      
      The sh7372 A4R hardware power domain contains the
      SH CPU Core and a set of I/O devices including
      multimedia accelerators and I2C controllers.
      
      One special case about A4R is the INTCS interrupt
      controller that needs to be saved and restored to
      keep working as expected. Also the LCDC hardware
      blocks are in a different hardware power domain
      but have their IRQs routed only through INTCS. So
      as long as LCDCs are active we cannot power down
      INTCS because that would risk losing interrupts.
      Signed-off-by: NMagnus Damm <damm@opensource.se>
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      382414b9