1. 27 10月, 2014 1 次提交
  2. 09 9月, 2014 1 次提交
  3. 31 8月, 2014 1 次提交
  4. 31 7月, 2014 1 次提交
  5. 30 7月, 2014 1 次提交
  6. 26 7月, 2014 1 次提交
    • P
      ARM: omap: clean redundant PISMO_xx macros used in OMAP3 · 222a3113
      pekon gupta 提交于
      PISMO_xx macros were used to define 'Platform Independent Storage MOdule'
      related GPMC configurations. This patch
      - Replaces these OMAP3 specific macros with generic CONFIG_xx macros as provided
        by current u-boot infrastructure.
      - Removes unused redundant macros, which are no longer required after
        merging of common platform code in following commit
            commit a0a37183
            ARM: omap: merge GPMC initialization code for all platform
      
      +-----------------+-----------------------------------------------------------+
      | Macro           | Reason for removal                                        |
      +-----------------+-----------------------------------------------------------+
      | PISMO1_NOR_BASE | duplicate of CONFIG_SYS_FLASH_BASE                        |
      +-----------------+-----------------------------------------------------------+
      | PISMO1_NAND_BASE| duplicate of CONFIG_SYS_NAND_BASE                         |
      +-----------------+-----------------------------------------------------------+
      | PISMO1_ONEN_BASE| duplicate of CONFIG_SYS_ONENAND_BASE                      |
      +-----------------+-----------------------------------------------------------+
      | PISMO1_NAND_SIZE| GPMC accesses NAND device via I/O mapped registers so     |
      |                 | configuring GPMC chip-select for smallest allowable       |
      |                 | segment (GPMC_SIZE_16M) is enough.                        |
      +-----------------+-----------------------------------------------------------+
      | PISMO1_ONEN_SIZE| OneNAND uses a fixed GPMC chip-select address-space of    |
      |                 | 128MB (GPMC_SIZE_128M)                                    |
      +-----------------+-----------------------------------------------------------+
      +-----------------+-----------------------------------------------------------+
      | PISMO1_NOR      |  Unused Macros                                            |
      | PISMO1_NAND     |                                                           |
      | PISMO2_CS0      |                                                           |
      | PISMO2_CS1      |                                                           |
      | PISMO1_ONENAND  |                                                           |
      | PISMO2_NAND_CS0 |                                                           |
      | PISMO2_NAND_CS1 |                                                           |
      | PISMO1_NOR_BASE |                                                           |
      | PISMO1_NAND_BASE|                                                           |
      | PISMO2_CS0_BASE |                                                           |
      +-----------------+-----------------------------------------------------------+
      Signed-off-by: NPekon Gupta <pekon@ti.com>
      222a3113
  7. 07 6月, 2014 1 次提交
  8. 02 6月, 2014 1 次提交
    • S
      usb: hub: remove CONFIG_USB_HUB_MIN_POWER_ON_DELAY · 77b83e6d
      Stephen Warren 提交于
      Now that we wait the correct specification-mandated time at the end of
      usb_hub_power_on(), I suspect that CONFIG_USB_HUB_MIN_POWER_ON_DELAY has
      no purpose.
      
      For cm_t35.h, we already wait longer than the original MIN_POWER_ON_DELAY,
      so this change is safe.
      
      For gw_ventana.h, we will wait as long as the original MIN_POWER_ON_DELAY
      iff pgood_delay was at least 200ms. I'm not sure if this is the case or
      not, hence I've CC'd relevant people to test this change.
      
      Cc: Igor Grinberg <grinberg@compulab.co.il>
      Cc: Tim Harvey <tharvey@gateworks.com>
      Signed-off-by: NStephen Warren <swarren@nvidia.com>
      77b83e6d
  9. 13 3月, 2014 1 次提交
    • S
      arm: omap: cm_t35: Fix: Re-add GPMC_NAND_ECC_LP_x8_LAYOUT · 7bb6e29b
      Stefan Roese 提交于
      Patch a7e36fc9 (mtd: nand: omap: remove unused #defines from common
      omap_gpmc.h) removed some MTD related defines. Including
      GPMC_NAND_ECC_LP_x8_LAYOUT. But this define is also needed for the
      memory controller configuration (only the x8 defines are needed,
      the x16 defines are the default). Without it the NAND subsystem is
      not configured correctly and booting into U-Boot does not work.
      Signed-off-by: NStefan Roese <sr@denx.de>
      Cc: Pekon Gupta <pekon@ti.com>
      Cc: Nikita Kiryanov <nikita@compulab.co.il>
      Cc: Igor Grinberg <grinberg@compulab.co.il>
      Cc: Tom Rini <trini@ti.com>
      Acked-by: NIgor Grinberg <grinberg@compulab.co.il>
      7bb6e29b
  10. 05 3月, 2014 1 次提交
    • P
      mtd: nand: omap: remove unused #defines from common omap_gpmc.h · a7e36fc9
      pekon gupta 提交于
      OMAP NAND driver can detect Page-size and OOB-size of NAND device from ONFI
      params or nand_id[] table. And based on that it defines ECC layout.
      This patch
      1) removes following board configs used for defining NAND ECC layout
      	- GPMC_NAND_ECC_LP_x16_LAYOUT (for large page x16 NAND)
      	- GPMC_NAND_ECC_LP_x8_LAYOUT  (for large page x8 NAND)
      	- GPMC_NAND_ECC_SP_x16_LAYOUT (for small page x16 NAND)
      	- GPMC_NAND_ECC_SP_x8_LAYOUT  (for small page x8 NAND)
      
      2) removes unused #defines in common omap_gpmc.h depending on above configs
      
      Build tested using: ./MAKEALL -s am33xx -s omap3 -s omap4 -s omap5
      Signed-off-by: NPekon Gupta <pekon@ti.com>
      a7e36fc9
  11. 22 2月, 2014 1 次提交
    • S
      arm: omap: cm_t35: Remove CONFIG_SYS_BOOTMAPSZ to fix FDT Linux booting · bc97f489
      Stefan Roese 提交于
      With CONFIG_SYS_BOOTMAPSZ defined, recent Linux kernel booting
      results in this error:
      
         Booting using the fdt blob at 0x81f00000
         Loading Kernel Image ... OK
      ERROR: Failed to allocate 0x1189d bytes below 0x80004000.
      device tree - allocation error
      FDT creation failed! hanging...### ERROR ### Please RESET the board ###
      
      Removing this define solves this issue.
      Signed-off-by: NStefan Roese <sr@denx.de>
      Cc: Nikita Kiryanov <nikita@compulab.co.il>
      Cc: Igor Grinberg <grinberg@compulab.co.il>
      Cc: Tom Rini <trini@ti.com>
      bc97f489
  12. 08 1月, 2014 1 次提交
  13. 13 12月, 2013 2 次提交
  14. 13 11月, 2013 1 次提交
    • H
      i2c, omap24xx: convert driver to new mutlibus/mutliadapter framework · 6789e84e
      Heiko Schocher 提交于
      - add omap24xx driver to new multibus/multiadpater support
      - adapted all config files, which uses this driver
      
      Tested on the am335x based siemens boards rut, dxr2 and pxm2
      posted here:
      http://patchwork.ozlabs.org/patch/263211/Signed-off-by: NHeiko Schocher <hs@denx.de>
      Tested-by: NTom Rini <trini@ti.com>
      Cc: Lars Poeschel <poeschel@lemonage.de>
      Cc: Steve Sakoman <sakoman@gmail.com>
      Cc: Thomas Weber <weber@corscience.de>
      Cc: Tom Rix <Tom.Rix@windriver.com>
      Cc: Grazvydas Ignotas <notasas@gmail.com>
      Cc: Enric Balletbo i Serra <eballetbo@iseebcn.com>
      Cc: Luca Ceresoli <luca.ceresoli@comelit.it>
      Cc: Igor Grinberg <grinberg@compulab.co.il>
      Cc: Ilya Yanok <yanok@emcraft.com>
      Cc: Stefano Babic <sbabic@denx.de>
      Cc: Nishanth Menon <nm@ti.com>
      Cc: Pali Rohár <pali.rohar@gmail.com>
      Cc: Peter Barada <peter.barada@logicpd.com>
      Cc: Nagendra T S  <nagendra@mistralsolutions.com>
      Cc: Michael Jones <michael.jones@matrix-vision.de>
      Cc: Raphael Assenat <raph@8d.com>
      Acked-by: NIgor Grinberg <grinberg@compulab.co.il>
      Acked-by: NStefano Babic <sbabic@denx.de>
      6789e84e
  15. 12 11月, 2013 2 次提交
  16. 05 11月, 2013 1 次提交
  17. 02 11月, 2013 2 次提交
  18. 15 8月, 2013 1 次提交
  19. 24 7月, 2013 1 次提交
  20. 02 7月, 2013 1 次提交
  21. 10 5月, 2013 1 次提交
  22. 22 3月, 2013 1 次提交
  23. 11 3月, 2013 1 次提交
  24. 09 3月, 2013 1 次提交
  25. 29 1月, 2013 1 次提交
  26. 21 12月, 2012 1 次提交
  27. 11 12月, 2012 2 次提交
  28. 23 10月, 2012 2 次提交
  29. 01 9月, 2012 2 次提交
  30. 07 7月, 2012 2 次提交
  31. 21 6月, 2012 1 次提交
  32. 15 5月, 2012 1 次提交
  33. 16 1月, 2012 1 次提交