Add tach trust groups to witherspoon monitor YAML

These will be used to specify that the 2nd rotor tach values
shouldn't be trusted when all of them are zero, because
that just means the fans are moving to a new target.

Resolves openbmc/openbmc#2336

Change-Id: I4b2ca6bb732d214dca67096817612025e1319226
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
diff --git a/meta-witherspoon/recipes-phosphor/fans/phosphor-fan-monitor-config-native/monitor.yaml b/meta-witherspoon/recipes-phosphor/fans/phosphor-fan-monitor-config-native/monitor.yaml
index dc5680d..0d68c70 100644
--- a/meta-witherspoon/recipes-phosphor/fans/phosphor-fan-monitor-config-native/monitor.yaml
+++ b/meta-witherspoon/recipes-phosphor/fans/phosphor-fan-monitor-config-native/monitor.yaml
@@ -1,3 +1,4 @@
+fans:
   - inventory: /system/chassis/motherboard/fan0
     allowed_out_of_range_time: 20
     deviation: 15
@@ -37,3 +38,11 @@
         has_target: true
       - name: fan3_1
         has_target: false
+
+sensor_trust_groups:
+  - class: NonzeroSpeed
+    sensors:
+      - name: fan0_1
+      - name: fan1_1
+      - name: fan2_1
+      - name: fan3_1