summaryrefslogtreecommitdiff
path: root/meta-openbmc-machines/meta-openpower/meta-ibm/meta-witherspoon/recipes-phosphor/fans/phosphor-fan-monitor-config-native/monitor.yaml
AgeCommit message (Collapse)AuthorFilesLines
2018-08-23[Subtree] Bring openbmc machines to top levelDave Cobbley1-73/+0
The new subtree model brings the subtrees up from the openbmc-machines layer. Change-Id: I58a03ae1be374bc79ae1438e65e888375d12d0c0 Signed-off-by: Dave Cobbley <david.j.cobbley@linux.intel.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2018-05-08wspoon: Only create/monitor fan1 on air cooledMatthew Barth1-0/+10
Add a condition check for fan1 that will only create fan1 associated functional properties and actively monitor fan1 if the condition passes. The condition checks the CoolingType is not WaterCooled. Tested: Fan1 functional properties are created when condition passes Fan1 is monitored when condition passes Change-Id: I0d9a91ceea500f82e4ccad2dbdc887a14286cf95 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
2018-03-07wspoon: MAX31785revA fan controller workaroundMatthew Barth1-1/+16
The MAX31785revA specification does not match how it functions. The MAX31785revA's functionality reports the rotor feedback speeds in a slow/fast relationship instead of rotor positions, therefore the fan*_0 object will always represent the slowest rotor. In combination with how the MAX31785revA latches its TACHSEL = 0 during a speed transition, it made it difficult to fault isolate the rear rotor of a fan. Using a combination of the fan monitor trust groups on all fan rotors and enabling a delay timer to determine when a fan rotor becomes functional, fan monitor is able to correctly reflect each fan rotor and fan enclosure's functional state in inventory. Fan faults are unable to be monitored on all fans when transitioning to a target speed. Tested: Each fan rotor's functional state is updated when blocked Correct amount of time to mark a fan nonfunctional is still honored A fan is functional after remaining in spec for 5 seconds Resolves openbmc/openbmc#2798 Change-Id: I834d63f6082eae4cb03ec501f0fb8272a9f5b673 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
2017-11-28wspoon: Allow fans 30sec before nonfunctionalMatthew Barth1-4/+4
Increasing the allowed out-of-range time to 30sec for large fan speed changes where the fan hardware was unable to reach the allowed minimum target speed within 20sec. This effectively bumps the shutdown due to fan fail/missing to 35sec since its a 5sec delay after the fans would be marked nonfunctional. Resolves openbmc/openbmc#2660 Change-Id: I48f83b89cfbe91e8d5a6ff9387998644c51b6174 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
2017-10-11Add tach trust groups to witherspoon monitor YAMLMatt Spinler1-0/+9
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>
2017-07-21wspoon: Normalize native fan bbappend search pathsBrad Bishop1-0/+39
Set FILESEXTRAPATHS to PN for all native recipe appends. Resolves: openbmc/openbmc#1991 Change-Id: I4f2fc9548dfab5d50970fcfcf1cb6082ae5d9288 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>