1. 21 5月, 2015 1 次提交
    • R
      ARM: dts: Fix WLAN interrupt line for AM335x EVM-SK · f25bf74c
      Romain Izard 提交于
      While Sitara AM335x SoCs are very close to OMAP SoCs, the 32-line GPIO
      controllers are numbered from 0 on AM335x and from 1 on OMAP. But when
      the configuration for the TI WLAN controllers was converted from
      platform data to device tree, this detail was overlooked, as 10 boards
      were using OMAP with the WL12xx and WL18xx controllers, and only one
      was based on AM335x.
      
      This invalid configuration prevents the WL1271 module on the AM335x
      EVM-SK from notifying interrupts to the SoC, and breaks the wlan driver.
      
      The DTS must be corrected to use the correct GPIO controller.
      Signed-off-by: NRomain Izard <romain.izard.pro@gmail.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      f25bf74c
  2. 25 3月, 2015 1 次提交
  3. 07 7月, 2014 1 次提交
  4. 02 7月, 2014 1 次提交
  5. 15 5月, 2014 1 次提交
  6. 07 5月, 2014 2 次提交
  7. 19 4月, 2014 1 次提交
  8. 13 3月, 2014 1 次提交
  9. 06 3月, 2014 1 次提交
  10. 05 3月, 2014 1 次提交
  11. 01 3月, 2014 2 次提交
  12. 14 2月, 2014 2 次提交
  13. 11 11月, 2013 1 次提交
  14. 21 10月, 2013 2 次提交
  15. 12 10月, 2013 6 次提交
  16. 03 9月, 2013 1 次提交
  17. 28 8月, 2013 1 次提交
    • S
      usb: usb: dsps: update code according to the binding document · c031a7d4
      Sebastian Andrzej Siewior 提交于
      This relfects the code and dts requires changes due to recent .dts
      binding updates:
      - use mg prefix for the Metor Graphics specific attributes
      - use power in mA not in mA/2 as specifed in the USB2.0 specification
      - remove the child node for USB. This is driver specific on won't be
        reflected in the device tree
      - use the "mentor" prefix instead of "mg".
      - use "dr_mode" istead of "mg,port-mode" for the port mode. The former
        is used by a few other drivers.
      
      Cc: Rob Herring <rob.herring@calxeda.com>
      Cc: Pawel Moll <pawel.moll@arm.com>
      Cc: Mark Rutland <mark.rutland@arm.com>
      Cc: Stephen Warren <swarren@wwwdotorg.org>
      Cc: Ian Campbell <ian.campbell@citrix.com>
      Cc: devicetree@vger.kernel.org
      Signed-off-by: NSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      c031a7d4
  18. 09 8月, 2013 1 次提交
    • S
      usb: musb: dsps: use proper child nodes · 97238b35
      Sebastian Andrzej Siewior 提交于
      This moves the two instances from the big node into two child nodes. The
      glue layer ontop does almost nothing.
      
      There is one devices containing the control module for USB (2) phy,
      (2) usb and later the dma engine. The usb device is the "glue device"
      which contains the musb device as a child. This is what we do ever since.
      
      The new file musb_am335x is just here to prob the new bus and populate
      child devices.
      
      There are a lot of changes to the dsps file as a result of the changes:
      
      - musb_core_offset
        This is gone. The device tree provides memory ressources information
        for the device there is no need to "fix" things
      
      - instances
        This is gone as well. If we have two instances then we have have two
        child enabled nodes in the device tree. For instance the SoC in beagle
        bone has two USB instances but only one has been wired up so there is
        no need to load and init the second instance since it won't be used.
      
      - dsps_glue is now per glue device
        In the past there was one of this structs but with an array of two and
        each instance accessed its variable depending on the platform device
        id.
      
      - no unneeded copy of structs
        I do not know why struct dsps_musb_wrapper is copied but it is not
        necessary. The same goes for musb_hdrc_platform_data which allocated
        on demand and then again by platform_device_add_data(). One copy is
        enough.
      Signed-off-by: NSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      97238b35
  19. 19 6月, 2013 10 次提交
  20. 05 6月, 2013 2 次提交
  21. 09 4月, 2013 1 次提交