summaryrefslogtreecommitdiff
path: root/zephyr/dts/bindings/motionsense/cros-ec,motionsense-sensor-info.yaml
diff options
context:
space:
mode:
authorJack Rosenthal <jrosenth@chromium.org>2021-11-04 12:11:58 -0600
committerCommit Bot <commit-bot@chromium.org>2021-11-05 04:22:34 +0000
commit252457d4b21f46889eebad61d4c0a65331919cec (patch)
tree01856c4d31d710b20e85a74c8d7b5836e35c3b98 /zephyr/dts/bindings/motionsense/cros-ec,motionsense-sensor-info.yaml
parent08f5a1e6fc2c9467230444ac9b582dcf4d9f0068 (diff)
downloadchrome-ec-stabilize-14333.B-ish.tar.gz
In the interest of making long-term branch maintenance incur as little technical debt on us as possible, we should not maintain any files on the branch we are not actually using. This has the added effect of making it extremely clear when merging CLs from the main branch when changes have the possibility to affect us. The follow-on CL adds a convenience script to actually pull updates from the main branch and generate a CL for the update. BUG=b:204206272 BRANCH=ish TEST=make BOARD=arcada_ish && make BOARD=drallion_ish Signed-off-by: Jack Rosenthal <jrosenth@chromium.org> Change-Id: I17e4694c38219b5a0823e0a3e55a28d1348f4b18 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3262038 Reviewed-by: Jett Rink <jettrink@chromium.org> Reviewed-by: Tom Hughes <tomhughes@chromium.org>
Diffstat (limited to 'zephyr/dts/bindings/motionsense/cros-ec,motionsense-sensor-info.yaml')
-rw-r--r--zephyr/dts/bindings/motionsense/cros-ec,motionsense-sensor-info.yaml56
1 files changed, 0 insertions, 56 deletions
diff --git a/zephyr/dts/bindings/motionsense/cros-ec,motionsense-sensor-info.yaml b/zephyr/dts/bindings/motionsense/cros-ec,motionsense-sensor-info.yaml
deleted file mode 100644
index e413e2bfff..0000000000
--- a/zephyr/dts/bindings/motionsense/cros-ec,motionsense-sensor-info.yaml
+++ /dev/null
@@ -1,56 +0,0 @@
-# Copyright 2021 The Chromium OS Authors. All rights reserved.
-# Use of this source code is governed by a BSD-style license that can be
-# found in the LICENSE file.
-
-description: The node has the information required by motion sense running
-
-compatible: "cros-ec,motionsense-sensor-info"
-
-properties:
- als-sensors:
- type: phandles
- required: false
- description: |
- List of ALS sensors to create motion_als_sensors array.
- The ALS sensors listed in the motion_als_sensors array
- are managed by motion sense task. The task reads the sensor
- data from the sensors and put them into the designated part
- in the ec mmap. For example, als_clear and als_rgb are aliases
- of ALS sensor noded defined in motionsense-sensor node.
- als-sensors = <&als_clear, &als_rgb>;
- This will automatically generate motion_als_sensors array from it.
- sensor-irqs:
- type: phandles
- required: false
- description: |
- List of GPIO interrupts from sensors to be enabled.
- GPIOs specified here will be enabled before motion sense task starts.
- sensor-irqs = <&gpio_ec_imu_int_l &gpio_ec_als_rgb_int_l>;
- accel-force-mode-sensors:
- type: phandles
- required: false
- description: |
- List of sensors should be handled in force mode. Sensors listed will be
- used to define CONFIG_ACCEL_FORCE_MODE_MASK so that motion sense task can
- manage them in force mode.
- accel-force-mode-sensors = <&lid_accel &als_clear>;
-
-#
-# examples:
-#
-# motionsense-sensor-info {
-# compatible = "cros-ec,motionsense-sensor-info";
-#
-# /* list of entries for motion_als_sensors */
-# als-sensors = <&als_clear>;
-#
-# /*
-# * list of GPIO interrupts that have to
-# * be enabled at initial stage
-# */
-# sensor-irqs = <&gpio_ec_imu_int_l &gpio_ec_als_rgb_int_l>;
-#
-# /* list of sensors in force mode */
-# accel-force-mode-sensors = <&lid_accel &als_clear>;
-# };
-#