1. 20 Apr, 2016 2 commits
    • Sam Protsenko's avatar
      usb: gadget: Move CONFIG_USB_GADGET_DUALSPEED to Kconfig · 3457bbaf
      Sam Protsenko authored
      Move CONFIG_USB_GADGET_DUALSPEED option to Kconfig and
      make all UDC controllers select USB_GADGET_DUALSPEED:
        - add next options to Kconfig selecting USB_GADGET_DUALSPEED:
          - USB_GADGET_ATMEL_USBA
          - USB_GADGET_DWC2_OTG
          - USB_DWC3
          - CI_UDC
        - make USB_MUSB_GADGET select USB_GADGET_DUALSPEED
      
      While at it, make some related fixes:
        - remove DUALSPEED from configs that don't enable gadget support:
          - kwb.h
          - tseries.h
        - add missing USB_GADGET option to next configs:
          - novena_defconfig
          - pcm051_rev*_defconfig
          - xfi3_defconfig
      Signed-off-by: default avatarSam Protsenko <semen.protsenko@linaro.org>
      3457bbaf
    • Sam Protsenko's avatar
      usb: gadget: Move CONFIG_USB_GADGET_VBUS_DRAW to Kconfig · a59a77f8
      Sam Protsenko authored
      The description was borrowed from kernel. Definitions were added to
      defconfig files in a way that "make savedefconfig" generates exactly
      the same file as used defconfig.
      
      Boards using 0 mA as CONFIG_USB_GADGET_VBUS_DRAW value were moved to use
      2 mA (as minimal allowed by Kconfig).
      Signed-off-by: default avatarSam Protsenko <semen.protsenko@linaro.org>
      a59a77f8
  2. 25 Mar, 2016 1 commit
  3. 14 Mar, 2016 1 commit
    • Simon Glass's avatar
      Kconfig: Move CONFIG_FIT and related options to Kconfig · 73223f0e
      Simon Glass authored
      There are already two FIT options in Kconfig but the CONFIG options are
      still in the header files. We need to do a proper move to fix this.
      
      Move these options to Kconfig and tidy up board configuration:
      
         CONFIG_FIT
         CONFIG_OF_BOARD_SETUP
         CONFIG_OF_SYSTEM_SETUP
         CONFIG_FIT_SIGNATURE
         CONFIG_FIT_BEST_MATCH
         CONFIG_FIT_VERBOSE
         CONFIG_OF_STDOUT_VIA_ALIAS
         CONFIG_RSA
      
      Unfortunately the first one is a little complicated. We need to make sure
      this option is not enabled in SPL by this change. Also this option is
      enabled automatically in the host builds by defining CONFIG_FIT in the
      image.h file. To solve this, add a new IMAGE_USE_FIT #define which can
      be used in files that are built on the host but must also build for U-Boot
      and SPL.
      
      Note: Masahiro's moveconfig.py script is amazing.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      [trini: Add microblaze change, various configs/ re-applies]
      Signed-off-by: default avatarTom Rini <trini@konsulko.com>
      73223f0e
  4. 05 Dec, 2015 1 commit
  5. 25 Nov, 2015 1 commit
  6. 05 Aug, 2015 1 commit
  7. 22 Jul, 2015 3 commits
  8. 26 Jun, 2015 2 commits
  9. 06 Mar, 2015 1 commit
  10. 30 Jan, 2015 2 commits
  11. 29 Jan, 2015 1 commit
  12. 05 Jan, 2015 1 commit
  13. 05 Nov, 2014 1 commit
  14. 23 Oct, 2014 1 commit
  15. 10 Oct, 2014 1 commit
  16. 25 Sep, 2014 2 commits
  17. 24 Sep, 2014 1 commit
    • Nikita Kiryanov's avatar
      spl: replace CONFIG_SPL_SPI_* with CONFIG_SF_DEFAULT_* · 88e34e5f
      Nikita Kiryanov authored
      Currently, CONFIG_SPL_SPI_* #defines are used for controlling SPI boot in
      SPL. These #defines do not allow the user to select SPI mode for the SPI flash
      (there's no CONFIG_SPL_SPI_MODE, so the SPI mode is hardcoded in
      spi_spl_load.c), and duplicate information already provided by
      CONFIG_SF_DEFAULT_* #defines.
      
      Kill CONFIG_SPL_SPI_*, and use CONFIG_SF_DEFAULT_* instead.
      
      Cc: Tom Rini <trini@ti.com>
      Cc: Marek Vasut <marex@denx.de>
      Cc: Sudhakar Rajashekhara <sudhakar.raj@ti.com>
      Cc: Lokesh Vutla <lokeshvutla@ti.com>
      Cc: Vitaly Andrianov <vitalya@ti.com>
      Cc: Lars Poeschel <poeschel@lemonage.de>
      Cc: Bo Shen <voice.shen@atmel.com>
      Cc: Hannes Petermaier <hannes.petermaier@br-automation.com>
      Cc: Michal Simek <monstr@monstr.eu>
      Acked-by: default avatarMarek Vasut <marex@denx.de>
      Signed-off-by: default avatarNikita Kiryanov <nikita@compulab.co.il>
      Reviewed-by: default avatarJagannadha Sutradharudu Teki <jaganna@xilinx.com>
      88e34e5f
  18. 18 Sep, 2014 1 commit
  19. 25 Aug, 2014 3 commits
  20. 25 Jul, 2014 2 commits
    • pekon gupta's avatar
      ARM: omap: move board specific NAND configs out from ti_armv7_common.h · 434f2cfc
      pekon gupta authored
      This patch moves some board specific NAND configs:
      - FROM: generic config file 'ti_armv7_common.h'
      - TO:   individual board config files using these configs.
      So that each board can independently set the value as per its design.
      
      Following configs are affected in this patch:
        CONFIG_SYS_NAND_U_BOOT_OFFS: <refer doc/README.nand>
        CONFIG_CMD_SPL_NAND_OFS: <refer doc/README.falcon>
        CONFIG_SYS_NAND_SPL_KERNEL_OFFS: <refer doc/README.falcon>
        CONFIG_CMD_SPL_WRITE_SIZE: <refer doc/README.falcon>
      
      This patch also updates documentation for few of above NAND configs.
      Signed-off-by: default avatarPekon Gupta <pekon@ti.com>
      434f2cfc
    • pekon gupta's avatar
      ARM: omap: fix GPMC address-map size for NAND and NOR devices · 77cd89e7
      pekon gupta authored
      Fixes commit a0a37183
          ARM: omap: merge GPMC initialization code for all platform
      
      1) NAND device are not directly memory-mapped to CPU address-space, they are
       indirectly accessed via following GPMC registers:
       - GPMC_NAND_COMMAND_x
       - GPMC_NAND_ADDRESS_x
       - GPMC_NAND_DATA_x
       Therefore from CPU's point of view, NAND address-map can be limited to just
       above register addresses. But GPMC chip-select address-map can be configured
       in granularity of 16MB only.
       So this patch uses GPMC_SIZE_16M for all NAND devices.
      
      2) NOR device are directly memory-mapped to CPU address-space, so its
       address-map size depends on actual addressable region in NOR FLASH device.
       So this patch uses CONFIG_SYS_FLASH_SIZE to derive GPMC chip-select address-map
       size configuration.
      Signed-off-by: default avatarPekon Gupta <pekon@ti.com>
      77cd89e7
  21. 22 Jul, 2014 1 commit
  22. 19 Jun, 2014 1 commit
  23. 11 Jun, 2014 3 commits
  24. 05 May, 2014 2 commits
  25. 17 Apr, 2014 3 commits
  26. 28 Mar, 2014 1 commit