1. 22 Aug, 2016 1 commit
  2. 20 Aug, 2016 2 commits
  3. 06 Aug, 2016 8 commits
  4. 27 Jul, 2016 3 commits
  5. 22 Jul, 2016 2 commits
  6. 17 Jul, 2016 1 commit
  7. 15 Jul, 2016 5 commits
  8. 14 Jul, 2016 10 commits
  9. 08 Jul, 2016 3 commits
    • Daniel Schwierzeck's avatar
      test/py: support 'memstart =' in u_boot_utils.find_ram_base() · d56dd0b1
      Daniel Schwierzeck authored
      Some archs like MIPS or PPC have a different 'bdinfo' output
      than ARM regarding the memory configuration. Also support
      'memstart = 0x*' in u_boot_utils.find_ram_base() to make
      all tests requiring the RAM base working on those archs.
      Signed-off-by: default avatarDaniel Schwierzeck <daniel.schwierzeck@gmail.com>
      Acked-by: default avatarStephen Warren <swarren@nvidia.com>
    • Stephen Warren's avatar
      test/py: strip VT100 codes from match buffer · 085e64dd
      Stephen Warren authored
      Prior to this patch, any VT100 codes emitted by U-Boot are considered part
      of a command's output, which often causes tests to fail. For example,
      test_env_echo_exists executes printenv, and then considers any text on a
      line before an = sign as a valid U-Boot environment variable name. This
      includes any VT100 codes emitted. When the test later attempts to use that
      variable, the name would be invalid since it includes the VT100 codes.
      Solve this by stripping VT100 codes from the match buffer, so they are
      never seen by higher level test code.
      The codes are still logged unmodified, so that users can expect U-Boot's
      exact output without interference. This does clutter the log file a bit.
      However, it allows users to see exactly what U-Boot emitted rather than a
      modified version, which hopefully is better for debugging. It's also much
      simpler to implement, since logging happens as soon as text is received,
      and so stripping the VT100 codes from the log would require handling
      reception and stripping of partial VT100 codes.
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
    • Stephen Warren's avatar
      test/py: fix CONFIG_ tests · a82642f3
      Stephen Warren authored
      Some CONFIG_ variables were recently renamed, but test/py wasn't updated
      to match. This causes some tests to be skipped. Fix test/py so the tests
      are run.
      Fixes: 11636258 ("Rename reset to sysreset")
      Fixes: f1f9d4fa ("hush: complete renaming CONFIG_SYS_HUSH_PARSER to CONFIG_HUSH_PARSER")
      Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
  10. 24 Jun, 2016 1 commit
  11. 19 Jun, 2016 3 commits
    • Stephen Warren's avatar
      clk: convert API to match reset/mailbox style · 135aa950
      Stephen Warren authored
      The following changes are made to the clock API:
      * The concept of "clocks" and "peripheral clocks" are unified; each clock
        provider now implements a single set of clocks. This provides a simpler
        conceptual interface to clients, and better aligns with device tree
        clock bindings.
      * Clocks are now identified with a single "struct clk", rather than
        requiring clients to store the clock provider device and clock identity
        values separately. For simple clock consumers, this isolates clients
        from internal details of the clock API.
      * clk.h is split so it only contains the client/consumer API, whereas
        clk-uclass.h contains the provider API. This aligns with the recently
        added reset and mailbox APIs.
      * clk_ops .of_xlate(), .request(), and .free() are added so providers
        can customize these operations if needed. This also aligns with the
        recently added reset and mailbox APIs.
      * clk_disable() is added.
      * All users of the current clock APIs are updated.
      * Sandbox clock tests are updated to exercise clock lookup via DT, and
        clock enable/disable.
      * rkclk_get_clk() is removed and replaced with standard APIs.
      Buildman shows no clock-related errors for any board for which buildman
      can download a toolchain.
      test/py passes for sandbox (which invokes the dm clk test amongst
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
    • Stephen Warren's avatar
      reset: implement a reset test · 4581b717
      Stephen Warren authored
      This adds a sandbox reset implementation (provider), a test client
      device, instantiates them both from Sandbox's DT, and adds a DM test
      that excercises everything.
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Acked-by: default avatarSimon Glass <sjg@chromium.org>
    • Stephen Warren's avatar
      test/py: fix printenv signon message disable code · 7a8f8865
      Stephen Warren authored
      CONFIG_VERSION_VARIABLE isn't always defined, so we can't simply look up
      its value directly, or an exception will occur if it isn't defined.
      Instead, we must use .get() to supply a default value if the variable
      isn't defined.
      Fixes: da37f006 ("tests: py: disable main_signon check for printenv cmd")
      Acked-by: default avatarHeiko Schocher <hs@denx.de>
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
  12. 09 Jun, 2016 1 commit
    • Heiko Schocher's avatar
      tests: py: disable main_signon check for printenv cmd · da37f006
      Heiko Schocher authored
      if CONFIG_VERSION_VARIABLE is set, the U-Boot environment
      contains a "vers" variable with the current U-Boot version
      string. If now "printenv" is called, test/py fails as it
      detects the main_sign string, which is in this case correct.
      So check only the main_sign as an error, if CONFIG_VERSION_VARIABLE
      is not set.
      Signed-off-by: default avatarHeiko Schocher <hs@denx.de>