1. 07 7月, 2014 1 次提交
  2. 15 5月, 2014 1 次提交
  3. 14 5月, 2014 1 次提交
  4. 07 5月, 2014 1 次提交
  5. 19 4月, 2014 2 次提交
  6. 06 3月, 2014 1 次提交
  7. 03 3月, 2014 2 次提交
    • P
      ARM: dts: AM33xx: updated default ECC scheme in nand-ecc-opt · c06c5270
      Pekon Gupta 提交于
      This patch updated MTD/NAND DT node binding to replace deprecated bindings
      as per following commit.
          commit ac65caf5
          ARM: OMAP2+: cleaned-up DT support of various ECC schemes
          Also Refer: Documentation/devicetree/bindings/mtd/gpmc-nand.txt
      Reviewed-by: NFelipe Balbi <balbi@ti.com>
      Signed-off-by: NPekon Gupta <pekon@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      c06c5270
    • P
      ARM: dts: am335x-evm: NAND: update MTD partition table · 91994fac
      Pekon Gupta 提交于
      This patch has following updates, specific to MTD/NAND DT
       - update MTD NAND partition table to keep compatibility between
         different boards and mainline u-boot.
       - prefix 'NAND.' in names of NAND device MTD partitions to differentiate them
         from other MTD device partitions (like NOR and QSPI)
                     Partition_Name            Partition_Size
          /dev/mtd0  NAND.SPL                  1 block-size*
          /dev/mtd1  NAND.SPL.backup1          1 block-size*
          /dev/mtd2  NAND.SPL.backup2          1 block-size*
          /dev/mtd3  NAND.SPL.backup3          1 block-size*
          /dev/mtd5  NAND.u-boot-spl-os        2 block-size* [for falcon boot]
          /dev/mtd4  NAND.u-boot               1 MB
          /dev/mtd6  NAND.u-boot-env           1 block-size*
          /dev/mtd7  NAND.u-boot-env.backup1   1 block-size*
          /dev/mtd8  NAND.kernel               till 0xA00000
          /dev/mtd9  NAND.file-system          till end of device
      
      * am335x-evm uses NAND device with block-size=128KiB
      Signed-off-by: NPekon Gupta <pekon@ti.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      91994fac
  8. 11 11月, 2013 1 次提交
  9. 21 10月, 2013 1 次提交
  10. 12 10月, 2013 7 次提交
  11. 28 8月, 2013 2 次提交
    • S
      usb: musb: am335x-evm: Do not remove the session bit HOST-only mode · 781f1798
      Sebastian Andrzej Siewior 提交于
      This is what I observe:
      On the first connect, the musb starts with DEVCTL.Session set. On
      disconnect, musb_core calls try_idle. That functions removes the Session
      bit signalizing that the session is over (something that only in OTG is
      required). A new device, that is plugged, is no longer recognized.
      I've setup a timer and checked the DEVCTL register and I haven't seen a
      change in VBus and I saw the B-Device bit set. After setting the IDDIG
      into A mode and forcing the device to behave like a A device, I didn't
      see a change.
      Neither VBUS goes to 0b11 nor does a session start request comes.
      In the TI-v3.2 kernel they skip to call musb_platform_try_idle() in the
      OTG_STATE_A_WAIT_BCON state while not in OTG mode.
      Since the second port hast a standard A plug the patch changes the port
      to run in host mode only and skips the timer which would remove
      DEVCTL.Session so we can reconnect to another device later.
      Signed-off-by: NSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      781f1798
    • 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
  12. 09 8月, 2013 2 次提交
    • S
      usb: musb dma: add cppi41 dma driver · 9b3452d1
      Sebastian Andrzej Siewior 提交于
      This driver is currently used by musb' cppi41 couter part. I may merge
      both dma engine user of musb at some point but not just yet.
      
      The driver seems to work in RX/TX mode in host mode, tested on mass
      storage. I increaed the size of the TX / RX transfers and waited for the
      core code to cancel a transfers and it seems to recover.
      
      v2..3:
      - use mall transfers on RX side and check data toggle.
      - use rndis mode on tx side so we haveon interrupt for 4096 transfers.
      - remove custom "transferred" hack and use dmaengine_tx_status() to
        compute the total amount of data that has been transferred.
      - cancel transfers and reclaim descriptors
      
      v1..v2:
      - RX path added
      - dma mode 0 & 1 is working
      - device tree nodes re-created.
      
      Cc: Vinod Koul <vinod.koul@intel.com>
      Cc: Dan Williams <djbw@fb.com>
      Signed-off-by: NSebastian Andrzej Siewior <bigeasy@linutronix.de>
      Signed-off-by: NFelipe Balbi <balbi@ti.com>
      9b3452d1
    • 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
  13. 19 6月, 2013 10 次提交
  14. 13 6月, 2013 2 次提交
  15. 05 6月, 2013 1 次提交
  16. 09 4月, 2013 1 次提交
  17. 15 11月, 2012 1 次提交
  18. 06 11月, 2012 3 次提交