diff options
author | Alec Berg <alecaberg@chromium.org> | 2014-03-24 10:03:56 -0700 |
---|---|---|
committer | chrome-internal-fetch <chrome-internal-fetch@google.com> | 2014-04-05 03:25:47 +0000 |
commit | 529548208cad436232cfba2c0b802523ddaf5383 (patch) | |
tree | 74e7b6febda2d30599ab72204befc8d61e0c3d7c /driver/accel_kxcj9.h | |
parent | f06ad7e2ab4fa1a03c2e48a8bca3fdf2abbdffa9 (diff) | |
download | chrome-ec-529548208cad436232cfba2c0b802523ddaf5383.tar.gz |
accel: add host command to modify accel params and add ectool command
Created a host command to set/get various motion sensor parameters and
added an ectool command to use that host command.
The host command is created such that the first argument is a
sub-command. Sub-commands created include:
dump: dumps all current motion sensor data
info: returns general information about each motion sensor
ec_rate: set/get the EC sampling rate of sensors
sensor_range: set/get the sensor range (ie +/- 2G,4G,8G)
sensor_odr: set/get the sensor output data rate (ie 50Hz, 100Hz, ...)
For sensor_range and sensor_odr parameters, since the host doesn't know
what are valid values for the parameter, the host can specify to round
up or down to the nearest valid value. For example, the host can specify
to set the output data rate to at least 100Hz, and the EC will return
the closest valid output data rate that is at least 100Hz.
BUG=chrome-os-partner:27321
BRANCH=rambi
TEST=Test on a glimmer using ectool from vt-2 prompt:
> ectool motionsense help
Usage:
motionsense - dump all motion data
motionsense info NUM - print sensor info
motionsense ec_rate [RATE_MS] - set/get sample rate
motionsense odr NUM [ODR [ROUNDUP]] - set/get sensor ODR
motionsense range NUM [RANGE [ROUNDUP]]- set/get sensor range
>
> ectool motionsense
Sensor 0: 0, 0, 1024
Sensor 1: 1024, 0, 0
Sensor 2: None
> ectool motionsense info 0
Type: accel
Location: base
Chip: kxcj9
> ectool motionsense ec_rate
10
> ectool motionsense ec_rate 1000
1000
> ectool motionsense odr 0
100000
> ectool motionsense odr 0 40000 1
50000
> ectool motionsense range 0 8
8
After running this I verified on the EC console that all the parameters
were set appropriately. I tested the EC sampling rate was 1000ms by
running lidangle on and making sure samples were displayed roughly every
second. I verified the sensor odr and range by defining
CONFIG_CMD_ACCELS and typing:
> accelrange 0
8
> accelrate 0
50000
Change-Id: I444e2f0eafabd607f1c7aa78b5c4e91f6cb06387
Signed-off-by: Alec Berg <alecaberg@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/192064
Reviewed-on: https://chromium-review.googlesource.com/193307
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'driver/accel_kxcj9.h')
-rw-r--r-- | driver/accel_kxcj9.h | 30 |
1 files changed, 0 insertions, 30 deletions
diff --git a/driver/accel_kxcj9.h b/driver/accel_kxcj9.h index a7137326d9..ea15b6ec17 100644 --- a/driver/accel_kxcj9.h +++ b/driver/accel_kxcj9.h @@ -100,36 +100,6 @@ #define KXCJ9_OSA_1600_HZ 7 -/** - * Write the accelerometer range. - * - * @param id Target accelerometer - * @param range Range (KXCJ9_GSEL_*). - * - * @return EC_SUCCESS if successful, non-zero if error. - */ -int accel_write_range(const enum accel_id id, const int range); - -/** - * Write the accelerometer resolution. - * - * @param id Target accelerometer - * @param range Resolution (KXCJ9_RES_*). - * - * @return EC_SUCCESS if successful, non-zero if error. - */ -int accel_write_resolution(const enum accel_id id, const int res); - -/** - * Write the accelerometer data rate. - * - * @param id Target accelerometer - * @param range Data rate (KXCJ9_OSA_*). - * - * @return EC_SUCCESS if successful, non-zero if error. - */ -int accel_write_datarate(const enum accel_id id, const int rate); - #ifdef CONFIG_ACCEL_INTERRUPTS /** * Setup a one-time accel interrupt. If the threshold is low enough, the |