c3c21bb888c36df0a0e1f695e4845309af659a1b |
|
21-Aug-2016 |
Shawn Nematbakhsh <shawnn@chromium.org> |
firmware_ECBootTime: Choose power-on console command based on config Going forward, we should support 'powerbtn' on our EC power-state drivers, so use it by default. BUG=chrome-os-partner:55999 BRANCH=None TEST=pass firmware_ECBootTime on kevin Signed-off-by: Shawn Nematbakhsh <shawnn@chromium.org> Change-Id: I683b3c84aff88ffb6b88fc85bb7368e561cc3057 Reviewed-on: https://chromium-review.googlesource.com/373563 Commit-Ready: Shawn N <shawnn@chromium.org> Tested-by: Shawn N <shawnn@chromium.org> Reviewed-by: danny chan <dchan@chromium.org> Reviewed-by: Wai-Hong Tam <waihong@google.com>
/external/autotest/server/cros/faft/config/snow.py
|
9ece2c6fb01d4c29d23a7238def15bdf656c885c |
|
12-Dec-2014 |
Julius Werner <jwerner@chromium.org> |
Add firmware_EventLog test to verify event log generation and timestamps This patch adds a new faft_lv4 test to validate the functionality of the firmware event log. It will boot the system in normal, developer and recovery mode, verifying that the right events are logged for each. It also tests a suspend/resume cycle, allowing either the ACPI events used on x86 boards or the userspace Sleep/Wake events introduced with Spring and Pit. (We can't check for 'FW Wake' because not all not-x86 boards have a resume component in firmware.) The events are correlated to the test section they were generated in by their timestamps, so this also confirms that accurate timestamps are generated. CQ-DEPEND=CL:238467 BUG=chrome-os-partner:34108 TEST=Tested on Falco (ToT), Blaze (ToT) and Pi (release). Pi failed in the expected manner because U-Boot is missing RTC support (and all timestamps are added as 2000-00-00). Blaze failed because its timestamps' months are off by one... turns out the RTC driver code was incorrectly copied from the 0-based-month-using kernel to our 1-based-month-using coreboot. Change-Id: I2760080030468ed71dd0b7359ac69a269f6ab47a Signed-off-by: Julius Werner <jwerner@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/238078 Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
/external/autotest/server/cros/faft/config/snow.py
|
5d1522e5231065d4372b2a6c5d752143a5074e9e |
|
10-Jul-2014 |
Danny Chan <dchan@google.com> |
File cleanup for presubmit hook. -Add missing docstring. BUG=chromium:389247 TEST=None Change-Id: I844fb2845dfb48f4d9b3d082a4f221319d992d05 Reviewed-on: https://chromium-review.googlesource.com/207246 Reviewed-by: danny chan <dchan@chromium.org> Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org> Commit-Queue: danny chan <dchan@chromium.org> Tested-by: danny chan <dchan@chromium.org>
/external/autotest/server/cros/faft/config/snow.py
|
6f59efa78ba6765b5ebf1d847865ae5a18bbe019 |
|
12-Feb-2014 |
Vic (Chun-Ju) Yang <victoryang@chromium.org> |
Add use_u_boot attribute to FAFT config This attribute indicates whether U-boot or depthcharge is used for a platform. BUG=None TEST=Lint Change-Id: I5d0c3781221cff900f5c4e587c797c58839047c2 Signed-off-by: Vic (Chun-Ju) Yang <victoryang@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/186041 Reviewed-by: Yusuf Mohsinally <mohsinally@chromium.org>
/external/autotest/server/cros/faft/config/snow.py
|
a39f97038dfa865c7bfcea2625d516d098207066 |
|
16-Aug-2013 |
Yusuf Mohsinally <mohsinally@google.com> |
Refactoring config settings for devices in FAFT tests. Created a new config system for faft tests which allow for a default file of settings and override file for each board that requires it. The default and override files contain a class called 'Values', in which the config attributes are stored. The class allows for inheritence of config values from to better organize related board settings. The new config system provides for one 'Config' class which is the main interface to settings for all tests. It does a cascading search, for the requested attribute, first checking a platform specific overrides, and then through the defaults. Modified FAFTSequence to contain one attribute 'faft_config' which replaces self.client_attr and self.delay which it made available to tests. BUG=None TEST=Manual runs of various tests at desk on link device Change-Id: I06da7be07364d5d99bdf6b204d628ad849f8d617 Reviewed-on: https://gerrit.chromium.org/gerrit/66006 Reviewed-by: Tom Wai-Hong Tam <waihong@chromium.org> Tested-by: Yusuf Mohsinally <mohsinally@chromium.org> Tested-by: Yusuf Mohsinally <mohsinally@google.com>
/external/autotest/server/cros/faft/config/snow.py
|