1. 27 May, 2016 2 commits
    • Simon Glass's avatar
      reset: Drop the reset failure message · 5c086215
      Simon Glass authored
      This adds to code size and is not needed, since hang() will print a message.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      5c086215
    • Stephen Warren's avatar
      Rename reset to sysreset · 11636258
      Stephen Warren authored
      The current reset API implements a method to reset the entire system.
      In the near future, I'd like to introduce code that implements the device
      tree reset bindings; i.e. the equivalent of the Linux kernel's reset API.
      This controls resets to individual HW blocks or external chips with reset
      signals. It doesn't make sense to merge the two APIs into one since they
      have different semantic purposes. Resolve the naming conflict by renaming
      the existing reset API to sysreset instead, so the new reset API can be
      called just reset.
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
      11636258
  2. 23 May, 2016 4 commits
  3. 14 Mar, 2016 2 commits
    • 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
    • Simon Glass's avatar
      dm: Use uclass_first_device_err() where it is useful · 3f603cbb
      Simon Glass authored
      Use this new function in places where it simplifies the code.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      3f603cbb
  4. 21 Feb, 2016 1 commit
  5. 28 Jan, 2016 1 commit
  6. 22 Jan, 2016 2 commits
  7. 19 Jan, 2016 1 commit
  8. 20 Nov, 2015 3 commits
  9. 18 Nov, 2015 1 commit
  10. 06 Nov, 2015 1 commit
  11. 30 Oct, 2015 1 commit
  12. 29 Oct, 2015 1 commit
  13. 24 Oct, 2015 1 commit
    • Bernhard Nortmann's avatar
      allow LED initialization without STATUS_LED_BOOT · 13cfbe51
      Bernhard Nortmann authored
      For current U-Boot to initialize status LEDs via status_led_init(), it
      is required to have both CONFIG_STATUS_LED and STATUS_LED_BOOT defined.
      This may be a particular concern with GPIO LEDs, where __led_init() is
      required to correctly set up the GPIO (gpio_request and
      gpio_direction_output). Without STATUS_LED_BOOT the initialization isn't
      called, which could leave the user with a non-functional "led" command -
      due to the fact that the LED routines in gpio_led.c use gpio_set_value()
      just fine, but the GPIO never got set up properly in the first place.
      
      I think having CONFIG_STATUS_LED is sufficient to justify a
      corresponding call to status_led_init(), even with no STATUS_LED_BOOT
      defined. To do so, common/board_r.c needs call that routine, so it now
      is exposed via status_led.h.
      Signed-off-by: default avatarBernhard Nortmann <bernhard.nortmann@web.de>
      [trini: Add dummy __led_init to pca9551_led.c]
      Signed-off-by: default avatarTom Rini <trini@konsulko.com>
      13cfbe51
  14. 23 Oct, 2015 2 commits
  15. 22 Oct, 2015 2 commits
  16. 05 Oct, 2015 1 commit
  17. 11 Sep, 2015 1 commit
  18. 02 Sep, 2015 5 commits
  19. 26 Aug, 2015 1 commit
  20. 13 Aug, 2015 1 commit
  21. 06 Aug, 2015 3 commits
    • Simon Glass's avatar
      cros_ec: Remove the old tunnel code · 24696e2f
      Simon Glass authored
      This is not needed with driver mode. Remove it.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      24696e2f
    • Simon Glass's avatar
      cros_ec: Support the LDO access method used by spring · f48eaf01
      Simon Glass authored
      Add a driver to support the special LDO access used by spring. This is a
      custom method in the cros_ec protocol - it does not use an I2C
      pass-through.
      
      There are two implementation choices:
      
      1. Write a special LDO driver which can talk across the EC. Duplicate all
      the logic from TPS65090 for retrying when the LDO fails to come up.
      
      2. Write a special I2C bus driver which pretends to be a TPS65090 and
      transfers reads and writes using the LDO message.
      
      Either is distasteful. The latter method is chosen since it results in less
      code duplication and a fairly simple (30-line) implementation of the core
      logic.
      
      The crosec 'ldo' subcommand could be removed (since i2c md/mw will work
      instead) but is retained as a convenience.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      f48eaf01
    • Simon Glass's avatar
      dm: cros_ec: Convert the I2C tunnel code to use driver model · cc456bd7
      Simon Glass authored
      The Chrome OS EC supports tunnelling through to an I2C bus on the EC. This
      currently uses a copy of the I2C command code and a special 'crosec'
      sub-command.
      
      With driver model we can define an I2C bus which tunnels through to the EC,
      and use the normal 'i2c' command to access it. This simplifies the code and
      removes some duplication.
      
      Add an I2C driver which tunnels through to the EC. Adjust the EC code to
      support binding child devices so that it can be set up. Adjust the existing
      I2C xfer function to fit driver model better.
      
      For now the old code remains to allow things to still work. It will be
      removed in a later patch once the new flow is fully enabled.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      cc456bd7
  22. 27 Jul, 2015 1 commit
  23. 21 Jul, 2015 2 commits