diff options
| author | Gwendal Grignou <gwendal@chromium.org> | 2019-04-25 14:33:33 -0700 |
|---|---|---|
| committer | ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> | 2019-04-29 22:48:10 +0000 |
| commit | 84f7b3e60d7e4956350326d4552425f630336659 (patch) | |
| tree | 1162aa05beea009d87b1efeeeb66dd97c1ac5734 | |
| parent | 1ce09c0a75b566e0ccf40c7fb19a5e82ef5d9f64 (diff) | |
| download | chrome-ec-84f7b3e60d7e4956350326d4552425f630336659.tar.gz | |
common: Remove FIFO sensor feature
When Samus migrating from 3.14 (where FIFO support needed for ARC++) [aka
cros-ec-sensor-ring kernel module] was never merged) to 4.x where
cros-ec-sensor-ring is present, Android Sensor HAL will present the
sensors to application.
To preserve the existing experience and keep the sensors out of ARC++,
prevent the EC from reporting that the FIFO sensor feature is supported.
That way, cros-ec-sensor-ring is not loaded by the kernel, and ARC++
will ignore the sensors.
BUG=b:126799706
BRANCH=samus
TEST=Check with this fix cros-ec-ring is not present in
/sys/bus/iio/devices.
Check accel/gyro keep working in pull mode.
Change-Id: If249a42d79e845f044fdb5854748c63ee7df7dcf
Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/1585123
Reviewed-by: Ross Zwisler <zwisler@chromium.org>
| -rw-r--r-- | common/host_command.c | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/common/host_command.c b/common/host_command.c index 58342e0007..6963db6f9c 100644 --- a/common/host_command.c +++ b/common/host_command.c @@ -750,9 +750,6 @@ static int host_command_get_features(struct host_cmd_handler_args *args) #ifdef CONFIG_USB_SWITCH_TSU6721 | EC_FEATURE_MASK_0(EC_FEATURE_USB_MUX) #endif -#ifdef CONFIG_ACCEL_FIFO - | EC_FEATURE_MASK_0(EC_FEATURE_MOTION_SENSE_FIFO) -#endif ; return EC_RES_SUCCESS; } |