1. 10 8月, 2017 1 次提交
  2. 09 8月, 2017 1 次提交
  3. 01 8月, 2017 1 次提交
  4. 23 7月, 2017 5 次提交
  5. 12 7月, 2017 4 次提交
  6. 11 7月, 2017 2 次提交
  7. 23 6月, 2017 1 次提交
  8. 16 6月, 2017 1 次提交
  9. 12 6月, 2017 1 次提交
  10. 10 6月, 2017 2 次提交
    • S
      arm: omap: Unify get_device_type() function · 00bbe96e
      Semen Protsenko 提交于
      Refactor OMAP3/4/5 code so that we have only one get_device_type()
      function for all platforms.
      
      Details:
       - Add ctrl variable for AM33xx and OMAP3 platforms (like it's done for
         OMAP4/5), so we can obtain status register in common way
       - For now ctrl structure for AM33xx/OMAP3 contains only status register
         address
       - Run hw_data_init() in order to assign ctrl to proper structure
       - Remove DEVICE_MASK and DEVICE_GP definitions as they are not used
         (DEVICE_TYPE_MASK and GP_DEVICE are used instead)
       - Guard structs in omap_common.h with #ifdefs, because otherwise
         including omap_common.h on non-omap4/5 board files breaks compilation
      
      Buildman script was run for all OMAP boards. Result output:
          arm: (for 38/616 boards)
              all +352.5
              bss -1.4
              data +3.5
              rodata +300.0
              spl/u-boot-spl:all +284.7
              spl/u-boot-spl:data +2.2
              spl/u-boot-spl:rodata +252.0
              spl/u-boot-spl:text +30.5
              text +50.4
          (no errors to report)
      
      Tested on AM57x EVM and BeagleBoard xM.
      Signed-off-by: NSam Protsenko <semen.protsenko@linaro.org>
      Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
      [trini: Rework the guards as to not break TI81xx]
      Signed-off-by: NTom Rini <trini@konsulko.com>
      00bbe96e
    • T
      am33xx: Finish migration of CONFIG_AM33XX/AM43XX · f2d78c1c
      Tom Rini 提交于
      Almost all users of CONFIG_AM33XX/AM43XX have been migrated.  Finish
      moving the last few over to Kconfig, and put all of the boards under the
      appropriate Kconfig chocie now.  This board choice is non-optional, so
      remove that keyword on am33xx.
      Signed-off-by: NTom Rini <trini@konsulko.com>
      f2d78c1c
  11. 05 6月, 2017 3 次提交
    • S
      arm: Include asm/setup.h explictly · 5d982856
      Simon Glass 提交于
      Include this header where needed so we do not need to rely on common.h.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      5d982856
    • T
      t81xx: Migrate TI81XX/TI816X/TI814X symbols to Kconfig · 8bb687fd
      Tom Rini 提交于
      The symbol CONFIG_TI81XX is used for the parts that are common to the
      TI816x and TI814x SoCs and are not part of CONFIG_ARCH_OMAP2PLUS nor
      CONFIG_AM33XX.  It however has so few uses that we can just modify the
      code to check for both and drop the symbol. The symbols CONFIG_TI816X
      and CONFIG_TI814X are for the repective SoCs.
      Signed-off-by: NTom Rini <trini@konsulko.com>
      8bb687fd
    • T
      ti816x: Rework DDR initialization sequence · 86277339
      Tom Rini 提交于
      The ti816x/am389x SoC is the first generation in what U-Boot calls the
      "am33xx" family.  In the first generation of this family the DDR
      initialization sequence is quite different from all of the subsequent
      generations.  Whereas with ti814x (second generation) we can easily work
      the minor differenced between that and am33xx (third generation), our
      attempts to do this for ti816x weren't sufficient.  Rather than add a
      large amount of #ifdef logic to make this different sequence work we add
      a new file, ti816x_emif4.c to handle the various required undocumented
      register writes and sequence and leverage what we can from
      arch/arm/mach-omap2/am33xx/ddr.c still.  As DDR2 has similar problems
      today but I am unable to test it, we drop the DDR2 defines from the code
      rather than imply that it works by leaving it.  We also remove a bunch
      of other untested code about changing the speed the DDR runs at.
      Signed-off-by: NTom Rini <trini@konsulko.com>
      86277339
  12. 15 5月, 2017 3 次提交
    • T
      omap: Drop CONFIG_OMAP_VC_I2C_HS_MCODE · 302acbed
      Tom Rini 提交于
      The symbol CONFIG_OMAP_VC_I2C_HS_MCODE always uses the default value.
      Restructure the comment and code such that if a need arises later to use
      another value we can address this then.
      Signed-off-by: NTom Rini <trini@konsulko.com>
      302acbed
    • T
      omap3: Migrate CONFIG_OMAP3_GPIO_X to Kconfig · 68ccab51
      Tom Rini 提交于
      The symbols CONFIG_OMAP3_GPIO_X control if we enable the clocks for a
      given GPIO bank in U-Boot.  select the required banks for each target.
      In some cases we need to also migrate from CONFIG_USB_EHCI (deprecated,
      in include/configs/) to CONFIG_USB_EHCI_HCD as we only require the GPIO
      bank to be enabled if USB is also enabled.
      Signed-off-by: NTom Rini <trini@konsulko.com>
      68ccab51
    • T
      omap5: Migrate CONFIG_OMAP_PLATFORM_RESET_TIME_MAX_USEC to Kconfig · d87f8296
      Tom Rini 提交于
      While in theory this value could be used in places outside of "omap5"
      (such as OMAP4), we only make use of it today in OMAP5, so place the
      Kconfig entry there.  Given that Kconfig lets us provide a default, we
      drop CONFIG_DEFAULT_OMAP_RESET_TIME_MAX_USEC entirely.  The contents of
      doc/README.omap-reset-time make a good help entry, so adjust them
      slightly and delete the file.  Move the comment about range to where we
      use the value now, and have Kconfig enforce the upper bound.
      Signed-off-by: NTom Rini <trini@konsulko.com>
      d87f8296
  13. 12 5月, 2017 9 次提交
  14. 10 5月, 2017 1 次提交
  15. 08 5月, 2017 3 次提交
  16. 28 4月, 2017 1 次提交
  17. 27 4月, 2017 1 次提交