ish: Trim down the release branchstabilize-wristpin-14469.59.B-ishstabilize-voshyr-14637.B-ishstabilize-quickfix-14695.187.B-ishstabilize-quickfix-14695.124.B-ishstabilize-quickfix-14526.91.B-ishstabilize-14695.85.B-ishstabilize-14695.107.B-ishstabilize-14682.B-ishstabilize-14633.B-ishstabilize-14616.B-ishstabilize-14589.B-ishstabilize-14588.98.B-ishstabilize-14588.14.B-ishstabilize-14588.123.B-ishstabilize-14536.B-ishstabilize-14532.B-ishstabilize-14528.B-ishstabilize-14526.89.B-ishstabilize-14526.84.B-ishstabilize-14526.73.B-ishstabilize-14526.67.B-ishstabilize-14526.57.B-ishstabilize-14498.B-ishstabilize-14496.B-ishstabilize-14477.B-ishstabilize-14469.9.B-ishstabilize-14469.8.B-ishstabilize-14469.58.B-ishstabilize-14469.41.B-ishstabilize-14442.B-ishstabilize-14438.B-ishstabilize-14411.B-ishstabilize-14396.B-ishstabilize-14395.B-ishstabilize-14388.62.B-ishstabilize-14388.61.B-ishstabilize-14388.52.B-ishstabilize-14385.B-ishstabilize-14345.B-ishstabilize-14336.B-ishstabilize-14333.B-ishrelease-R99-14469.B-ishrelease-R98-14388.B-ishrelease-R102-14695.B-ishrelease-R101-14588.B-ishrelease-R100-14526.B-ishfirmware-cherry-14454.B-ishfirmware-brya-14505.B-ishfirmware-brya-14505.71.B-ishfactory-kukui-14374.B-ishfactory-guybrush-14600.B-ishfactory-cherry-14455.B-ishfactory-brya-14517.B-ish

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>

1 files changed, 0 insertions, 66 deletions

diff --git a/zephyr/dts/bindings/motionsense/cros-ec,motionsense-sensor-config.yaml b/zephyr/dts/bindings/motionsense/cros-ec,motionsense-sensor-config.yaml
deleted file mode 100644
index 68cdd15637..0000000000
--- a/zephyr/dts/bindings/motionsense/cros-ec,motionsense-sensor-config.yaml
+++ /dev/null
@@ -1,66 +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: |
-    There are 4 configuration parameters to deal with different
-    configuration
-    Power   |         S0        |            S3     |      S5
-    --------+-------------------+-------------------+-----------------
-    From AP | <------- SENSOR_CONFIG_AP ----------> |
-            | Use for normal    | While sleeping    | Always disabled
-            | operation (game,  | For Activity      |
-            | screen rotation)  | Recognition       |
-    --------+-------------------+-------------------+------------------
-    From EC |SENSOR_CONFIG_EC_S0|SENSOR_CONFIG_EC_S3|SENSOR_CONFIG_EC_S5
-            | Background        | Gesture  Recognition (Double tap, ...)
-            | Activity (compass,|
-            | ambient light)    |
-
-compatible: "cros-ec,motionsense-sensor-config"
-
-child-binding:
-  description: |
-    A config node is used to create a motion_data_t instance.
-    Node name can only be either ap, ec-s0, ec-s3, or ec-s5,
-    and it is used to indicate one of the 4 configurations.
-    For example, node name ec-s0 is for SENSOR_CONFIG_EC_S0.
-    ec-s0 {
-       label = "SENSOR_CONFIG_EC_S0";
-       odr = <1000>;
-       ec_rate = <1000>;
-    };
-  properties:
-    label:
-      type: string
-      required: false
-      description: |
-        Human-readable string describing the config.
-        see the example the above.
-    odr:
-      type: int
-      required: false
-      description: |
-        Sensor output data rate in mHz.
-        MSB is used to know if we are rounding up.
-    ec-rate:
-      type: int
-      required: false
-      description: Delay between collection by EC, in us.
-
-#
-# examples:
-#
-# configs {
-#         compatible =
-#                 "cros-ec,motionsense-sensor-config";
-#         ec-s0 {
-#                 label = "SENSOR_CONFIG_EC_S0";
-#                 odr = <(10000 | ROUND_UP_FLAG)>;
-#         };
-#         ec-s3 {
-#                 label = "SENSOR_CONFIG_EC_S3";
-#                 odr = <(10000 | ROUND_UP_FLAG)>;
-#         };
-# };
-#