From 6e1449eb477f73dbba8bddf4c3dae907a93bb065 Mon Sep 17 00:00:00 2001 From: Dawid Niedzwiecki Date: Tue, 11 May 2021 13:37:40 +0200 Subject: zephyr: Rework CBI to be used as a driver Rework the CBI support in Zephyr to be used via driver API. Change also approach what to do with SSFC - let sensor drivers decide how to handle alternative sensors. BUG=b:183990188 BRANCH=none TEST=Add alternative motion sensors to the device tree, modify CBI SSFC with 'cbi set 8 value 4', reboot EC and verify that the new sensors are used with the 'accelinfo' command. Signed-off-by: Dawid Niedzwiecki Change-Id: I701af96bfa7a17333220530a5c63b8e8aaeb0d6b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2862727 Reviewed-by: Yuval Peress --- zephyr/dts/bindings/motionsense/motionsense-sensor-base.yaml | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'zephyr/dts/bindings/motionsense') diff --git a/zephyr/dts/bindings/motionsense/motionsense-sensor-base.yaml b/zephyr/dts/bindings/motionsense/motionsense-sensor-base.yaml index 9e8b7be2c3..6948ce6997 100644 --- a/zephyr/dts/bindings/motionsense/motionsense-sensor-base.yaml +++ b/zephyr/dts/bindings/motionsense/motionsense-sensor-base.yaml @@ -58,6 +58,10 @@ properties: type: phandle description: phandle to another sensor that can be swapped with this one at runtime. + alternate-indicator: + type: phandle + description: phandle to CBI SSGC value indicating that the sensor + should be used # # examples: -- cgit v1.2.1