1. 08 7月, 2021 1 次提交
  2. 07 7月, 2021 1 次提交
    • A
      sandbox: cros-ec: Add tests for the Chromium OS EC PWM driver · e712245d
      Alper Nebi Yasak 提交于
      This patch adds a limited pulse-width modulator to sandbox's Chromium OS
      Embedded Controller emulation. The emulated PWM device supports multiple
      channels but can only set a duty cycle for each, as the actual EC
      doesn't expose any functionality or information other than that. Though
      the EC supports specifying the PWM channel by its type (e.g. display
      backlight, keyboard backlight), this is not implemented in the emulation
      as nothing in U-Boot uses this type specification.
      
      This emulated PWM device is then used to test the Chromium OS PWM driver
      in sandbox. Adding the required device node to the sandbox test
      device-tree unfortunately makes it the first PWM device, so this also
      touches some other tests to make sure they still use the sandbox PWM.
      Signed-off-by: NAlper Nebi Yasak <alpernebiyasak@gmail.com>
      Reviewed-by: NSimon Glass <sjg@chromium.org>
      e712245d
  3. 28 6月, 2021 1 次提交
  4. 17 6月, 2021 1 次提交
  5. 08 6月, 2021 1 次提交
    • S
      sandbox: log: Avoid build error with !CONFIG_LOG · 8d9bb98f
      Simon Glass 提交于
      The pr_cont_test.c test requires CONFIG_LOG since it directly accesses
      fields in global_data that require it. Move the test into the CONFIG_LOG
      condition to avoid build errors.
      
      Enable CONFIG_LOG on sandbox (not sandbox_spl, etc.) so that we still run
      this test. This requires resyncing of the configs.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      8d9bb98f
  6. 05 5月, 2021 1 次提交
  7. 04 5月, 2021 1 次提交
  8. 28 4月, 2021 1 次提交
  9. 27 4月, 2021 1 次提交
  10. 20 4月, 2021 2 次提交
  11. 13 4月, 2021 1 次提交
  12. 12 4月, 2021 1 次提交
  13. 06 4月, 2021 1 次提交
  14. 26 2月, 2021 1 次提交
  15. 18 2月, 2021 2 次提交
  16. 30 1月, 2021 1 次提交
  17. 19 1月, 2021 1 次提交
  18. 04 12月, 2020 1 次提交
  19. 01 12月, 2020 1 次提交
  20. 06 11月, 2020 1 次提交
    • S
      board: Rename uclass to sysinfo · 3a8ee3df
      Simon Glass 提交于
      This uclass is intended to provide a way to obtain information about a
      U-Boot board. But the concept of a U-Boot 'board' is the whole system,
      not just one circuit board, meaning that 'board' is something of a
      misnomer for this uclass.
      
      In addition, the name 'board' is a bit overused in U-Boot and we want to
      use the same uclass to provide SMBIOS information.
      
      The obvious name is 'system' but that is so vague as to be meaningless.
      Use 'sysinfo' instead, since this uclass is aimed at providing information
      on the system.
      
      Rename everything accordingly.
      
      Note: Due to the patch delta caused by the symbol renames, this patch
      shows some renamed files as being deleted in one place and created in
      another.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      Reviewed-by: NBin Meng <bmeng.cn@gmail.com>
      3a8ee3df
  21. 29 10月, 2020 1 次提交
  22. 28 10月, 2020 2 次提交
  23. 18 10月, 2020 1 次提交
  24. 14 10月, 2020 1 次提交
  25. 06 10月, 2020 1 次提交
  26. 01 10月, 2020 1 次提交
  27. 30 9月, 2020 3 次提交
    • E
      firmware: smci: sandbox test for SCMI reset controllers · c0dd177a
      Etienne Carriere 提交于
      Add tests for SCMI reset controllers. A test device driver
      sandbox-scmi_devices.c is used to get reset resources, allowing further
      resets manipulation.
      
      Change sandbox-smci_agent to emulate 1 reset controller exposed through
      an agent. Add DM test scmi_resets to test this reset controller.
      Signed-off-by: NEtienne Carriere <etienne.carriere@linaro.org>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Peng Fan <peng.fan@nxp.com>
      Cc: Sudeep Holla <sudeep.holla@arm.com>
      Reviewed-by: NSimon Glass <sjg@chromium.org>
      c0dd177a
    • E
      firmware: scmi: sandbox test for SCMI clocks · 87d4f277
      Etienne Carriere 提交于
      Add tests for SCMI clocks. A test device driver sandbox-scmi_devices.c
      is used to get clock resources, allowing further clock manipulation.
      
      Change sandbox-smci_agent to emulate 3 clocks exposed through 2 agents.
      Add DM test scmi_clocks to test these 3 clocks.
      Update DM test sandbox_scmi_agent with load/remove test sequences
      factorized by {load|remove}_sandbox_scmi_test_devices() helper functions.
      Signed-off-by: NEtienne Carriere <etienne.carriere@linaro.org>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Peng Fan <peng.fan@nxp.com>
      Cc: Sudeep Holla <sudeep.holla@arm.com>
      Reviewed-by: NSimon Glass <sjg@chromium.org>
      87d4f277
    • E
      firmware: add SCMI agent uclass · 358599ef
      Etienne Carriere 提交于
      This change introduces SCMI agent uclass to interact with a firmware
      using the SCMI protocols [1].
      
      SCMI agent uclass currently supports a single method to request
      processing of the SCMI message by an identified server. A SCMI message
      is made of a byte payload associated to a protocol ID and a message ID,
      all defined by the SCMI specification [1]. On return from process_msg()
      method, the caller gets the service response.
      
      SCMI agent uclass defines a post bind generic sequence for all devices.
      The sequence binds all the SCMI protocols listed in the FDT for that
      SCMI agent device. Currently none, but later change will introduce
      protocols.
      
      This change implements a simple sandbox device for the SCMI agent uclass.
      The sandbox nicely answers SCMI_NOT_SUPPORTED to SCMI messages.
      To prepare for further test support, the sandbox exposes a architecture
      function for test application to read the sandbox emulated devices state.
      Currently supports 2 SCMI agents, identified by an ID in the FDT device
      name. The simplistic DM test does nothing yet.
      
      SCMI agent uclass is designed for platforms that embed a SCMI server in
      a firmware hosted somewhere, for example in a companion co-processor or
      in the secure world of the executing processor. SCMI protocols allow an
      SCMI agent to discover and access external resources as clock, reset
      controllers and more. SCMI agent and server communicate following the
      SCMI specification [1]. This SCMI agent implementation complies with
      the DT bindings defined in the Linux kernel source tree regarding
      SCMI agent description since v5.8.
      
      Links: [1] https://developer.arm.com/architectures/system-architectures/software-standards/scmiSigned-off-by: NEtienne Carriere <etienne.carriere@linaro.org>
      Cc: Simon Glass <sjg@chromium.org>
      Cc: Peng Fan <peng.fan@nxp.com>
      Cc: Sudeep Holla <sudeep.holla@arm.com>
      Reviewed-by: NSimon Glass <sjg@chromium.org>
      358599ef
  28. 27 8月, 2020 1 次提交
  29. 25 8月, 2020 1 次提交
  30. 24 8月, 2020 1 次提交
  31. 20 8月, 2020 1 次提交
  32. 11 8月, 2020 1 次提交
  33. 08 8月, 2020 2 次提交
  34. 31 7月, 2020 1 次提交