| 13e353729c400d029e9167ded3cdc3032cbf8411 |
|
02-Dec-2016 |
Chung-yih Wang <cywang@google.com> |
input_device: Add get_device_node() from keyboard_device.py
The function get_device_node() is for retrieveing the device node of
a given device type in general and is better to reside in input_device library.
BUG=none
TEST=none
Change-Id: I85db052eda97df34c29318e5245ce4747bf9db48
Signed-off-by: Chung-yih Wang <cywang@google.com>
Reviewed-on: https://chromium-review.googlesource.com/415653
Reviewed-by: Ben Cheng <bccheng@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/keyboard_device.py
|
| c8092cfaf50f967cb60918700d1db88ab0b9c130 |
|
05-Mar-2015 |
ZhengShunQian <zhengsq@rock-chips.com> |
TouchMTB: add cros_ec to keyboard regular expression
veyron boards use cros_ec keyboard, adding it accordingly.
BUG=chrome-os-partner:36032
TEST=run TouchMTB test on veyron_mighty
Change-Id: I899820f2d3a794772368e54c7017869dd1af7acf
Signed-off-by: ZhengShunQian <zhengsq@rock-chips.com>
Reviewed-on: https://chromium-review.googlesource.com/256252
Reviewed-by: Charlie Mooney <charliemooney@chromium.org>
Tested-by: Charlie Mooney <charliemooney@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/keyboard_device.py
|
| 51183f52aa2c3fd77c0b7e1d6a2856ac83260dd2 |
|
28-Oct-2013 |
Charlie Mooney <charliemooney@chromium.org> |
Add additional keyboard name to Touch FW test
I tried to run the fw test on my Daisy today and it couldn't find
the keyboard. It looks like it's using a different name for the
device node than we expected from on other platforms. This patch
just adds the new name to the list.
BUG=chromium:312309
TEST=ran the FW test and it found the keyboard and ran.
Change-Id: I2e2b74d5d565474ac0aa591fe0eb7ba0f067103f
Signed-off-by: Charlie Mooney <charliemooney@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/174881
Reviewed-by: Shyh-In Hwang <josephsih@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/keyboard_device.py
|
| ad3136c03a931b4c1742cdec472780be15f7e1ed |
|
12-Aug-2013 |
Joseph Hwang <josephsih@chromium.org> |
firmware_TouchMTB: replay with a mocked device
It is handy and sometimes essential to be able to replay the test
logs captured from a platform on another platform.
When replaying logs, the board on which the logs were captured could
be different from the board of the chromebook currently used. Hence,
the correct board should be extracted from the log specified in the
replay directory. The following priority is used to find the device
description file used to mock the particular touch device for that
board:
(1) use the device description file in the replay directory
(2) use the device description file found in tests/device directory
However, if "-d/--system_device" command line option is specified, use
the system touch device found on the chromebook instead as before.
BUG=chromium:274204
TEST=Replay the lumpy logs on both lumpy and link. Observe that
their summary reports are exactly the same.
$ cd /usr/local/autotest/tests/firmware_TouchMTB
$ tools/machine_replay.sh -b tests/logs/lumpy -s
$ ./summary.sh -d /tmp -m f
Change-Id: I95a39d0ead821de9379e2f3a26f19e42a9c829b9
Reviewed-on: https://gerrit.chromium.org/gerrit/66345
Reviewed-by: Charlie Mooney <charliemooney@chromium.org>
Tested-by: Joseph Shyh-In Hwang <josephsih@chromium.org>
Commit-Queue: Joseph Shyh-In Hwang <josephsih@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/keyboard_device.py
|
| 57067adf937e3a96ae161366bb6a0933cbe61a5a |
|
23-Jul-2013 |
Charlie Mooney <charliemooney@chromium.org> |
Add Pit's keyboard string to TouchMTB test
The keyboard device module for the Touch FW test didn't check for the
string that's used for the keyboard on Pit. As a result it would fail
to run the test on this device. This change adds that string.
BUG=none
TEST=manually tested on evt2 pit
Change-Id: I38585223b57fb0bc94f3f348959eb01e7791f03f
Signed-off-by: Charlie Mooney <charliemooney@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/63039
Reviewed-by: Joseph Shyh-In Hwang <josephsih@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/keyboard_device.py
|
| 0cbff8bf3666a81b886080f82712943e36dad95f |
|
22-Apr-2013 |
Joseph Hwang <josephsih@chromium.org> |
firmware_TouchMTB: Rename the test suite as firmware_TouchMTB
As the test suite is now applicable to both the touchpad
and the touchscreen, it is proper to rename the test name
from firmware_TouchpadMTB to firmware_TouchMTB.
BUG=chromium:234117
TEST=None. Will be combined with next patch.
Change-Id: I92ecc074023c76f7c2f292b7e22ef960d537819f
Reviewed-on: https://gerrit.chromium.org/gerrit/48781
Reviewed-by: Charlie Mooney <charliemooney@chromium.org>
Commit-Queue: Joseph Shyh-In Hwang <josephsih@chromium.org>
Tested-by: Joseph Shyh-In Hwang <josephsih@chromium.org>
/external/autotest/client/site_tests/firmware_TouchMTB/keyboard_device.py
|