kled: Set the max charging voltage to 15V

Kled will be shipped with 45W charger.
So we should limit to test PD voltage to 15V.

BUG=b:153612746
TEST=Pass firmware_PDVbusRequest with a 45W charger

Change-Id: I6e2e6cf5b2b4f6dcde2e6bb57d6127cb2403f0f2
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/fw-testing-configs/+/2176403
Reviewed-by: Greg Edelston <gredelston@google.com>
Reviewed-by: Wai-Hong Tam <waihong@google.com>
Commit-Queue: Philip Chen <philipchen@chromium.org>
Tested-by: Philip Chen <philipchen@chromium.org>
1 file changed
tree: 9a2ecb699122319897383c7de9ee74cfe7afa0c4
  1. DEFAULTS.json
  2. OWNERS
  3. README.md
  4. arkham.json
  5. asuka.json
  6. atlas.json
  7. auron.json
  8. banjo.json
  9. banon.json
  10. bob.json
  11. brain.json
  12. buddy.json
  13. candy.json
  14. caroline.json
  15. cave.json
  16. celes.json
  17. chell.json
  18. cheza.json
  19. cid.json
  20. coral.json
  21. cyan.json
  22. dragonegg.json
  23. drallion.json
  24. edgar.json
  25. elm.json
  26. enguarde.json
  27. eve.json
  28. expresso.json
  29. fievel.json
  30. fizz.json
  31. gale.json
  32. gandof.json
  33. glados.json
  34. gnawty.json
  35. gru.json
  36. grunt.json
  37. guado.json
  38. gus.json
  39. hana.json
  40. hatch.json
  41. heli.json
  42. jacuzzi.json
  43. jaq.json
  44. jecht.json
  45. jerry.json
  46. jetstream.json
  47. kalista.json
  48. kefka.json
  49. kevin-tpm2.json
  50. kevin.json
  51. kip.json
  52. kitty.json
  53. kukui.json
  54. kunimitsu.json
  55. lars.json
  56. lulu.json
  57. mickey.json
  58. mighty.json
  59. minnie.json
  60. mistral.json
  61. monroe.json
  62. nami.json
  63. nasher.json
  64. nautilus.json
  65. ninja.json
  66. nocturne.json
  67. nyan.json
  68. oak.json
  69. octopus.json
  70. orco.json
  71. paine.json
  72. pinky.json
  73. poppy.json
  74. puff.json
  75. pyro.json
  76. rambi.json
  77. rammus.json
  78. reef.json
  79. reef_uni.json
  80. reks.json
  81. relm.json
  82. rikku.json
  83. samus.json
  84. sand.json
  85. sarien.json
  86. scarlet.json
  87. sentry.json
  88. setzer.json
  89. slippy.json
  90. snappy.json
  91. soraka.json
  92. speedy.json
  93. storm.json
  94. strago.json
  95. sumo.json
  96. swanky.json
  97. terra.json
  98. tidus.json
  99. tiger.json
  100. trogdor.json
  101. ultima.json
  102. umaro.json
  103. veyron.json
  104. volteer.json
  105. whirlwind.json
  106. winky.json
  107. wizpig.json
  108. yuna.json
  109. zork.json
README.md

CrOS fw-testing-configs: User’s Guide

go/cros-fw-testing-configs-guide

Background

End-to-end firmware testing in ChromeOS relies on board-specific configuration files. Previously, those files were stored in Autotest. Now, they have been moved into a separate repository, fw-testing-configs, so that other testing frameworks (e.g. Tast, SerialTest) can access them too.

The design document for the new repository is at go/cros-fw-testing-configs.

Working With Configs

File Locations & Names

All the config files are located at the top directory of the fw-testing-configs repository.

The fw-testing-configs repository currently has two checkouts in the ChromeOS manifest: one inside of Autotest, and one inside of tast-tests.

There is one config file for each platform, named as ${PLATFORM}.json: for example, octopus.json. There is also one special config file, DEFAULTS.json, which contains default values and documentation for each attribute. (For now, platform names are defined according to mosys platform name.)

File Contents

Each config file should contain a single object whose fields override the values specified in DEFAULTS.json. Any fields which do not have a corresponding value in DEFAULTS.json will be ignored.

There are a few special fields to be aware of:

  • platform (required): A string which should exactly match the config file’s basename (minus the .json extension).
  • parent (optional): A string which can contain the name of a parent platform, whose fields will be inherited with lower precedence. See “Inheritance” below. Example: asuka.json
  • models (optional): An object which can contain the names of any models, whose fields will be inherited with higher precedence. See “Inheritance” below. Example: octopus.json

Inheritance

There is an inheritance model in these config files. In all cases, the most specific configuration is used:

[Model > ] Platform [ > Parent [...] ] > DEFAULTS

For each attribute that exists in DEFAULTS.json (besides the documentation attributes):

  • If that attribute is given a value in the platform’s models[${MODEL}], then that is the value that is used.
  • Otherwise, if that attribute is given a value in the ${PLATFORM}.json, then that is the value that is used.
  • Otherwise, if ${PLATFORM}.json specifies a parent configuration via the parent attribute, then that is the value that is used.
  • Parent configurations can specify parents as well, and the inheritance recurses until a config file does not have a parent attribute.
  • Finally, for any attribute which was not otherwise given a value, the value from DEFAULTS.json is used.

Accessing Configs

In Autotest, configs are loaded during FirmwareTest.initialize. Config values can be accessed via self.faft_config.${ATTRIBUTE}, such as self.faft_config.chrome_ec.

In Tast, configs can be created via firmware.NewConfig. In order to conform with Go’s style, attribute names are modified to MixedCaps. Config values can be accessed via cfg[${ATTRIBUTE}], such as cfg[ChromeEC].

Modifying Tests and Configs

Configs are now in a separate repository from Autotest or tast-tests. Thus, config edits now require a separate CL from Autotest/tast-tests edits. If you are accustomed to working with config files directly in Autotest, this is a slightly different workflow.

When you are editing config files, please be sure to run git commands from within the fw-testing-configs checkout. If you run git add . or repo upload --cbr . from within autotest/server/cros/faft/, then your changes to the config files will not be captured.

If you are modifying both test files and config files, then you will need at least two CL’s: one for the test change, and one for the fw-testing-configs change. Consider also whether your change will impact the other testing repositories (Autotest, Tast, SerialTest): you might need to run tests or make changes there, too.

When submitting multiple CL’s like that, please use the Cq-Depend syntax as appropriate. If you don‘t use Cq-Depend, you risk the name of a config attribute changing while tests are still looking for the old name, and then tests will break. The reverse is a risk, too. You might need both CL’s to depend on each other. Note that this while this precaution mitigates risk, it does not fully eliminate risk: only one of the CL’s might get uploaded to the lab machines running Autotest/Tast, or one CL may be reverted without the other.