tree e8e881c58eb7d0b0441ded15c301fa9890026466
parent dd648008787e40643ca2bc32441b97dfb531d7c3
author Jason Ling <jasonling@google.com> 1594501694 -0700
committer Jason Ling <jasonling@google.com> 1594679932 +0000

fan-sensors: add optional pwm name override

Problem: pwm sensors created by FanSensors have a naming scheme that is
hard coded. There are systems that need to have pwm sensors
named differently.

Solution: In a fan connector configuration the PwmName property will now
attempt to be detected. If this property exists then the name in PwmName
will be used; otherwise the pwm sensor name will be generated using the
old method.

Tested:
Entity-Manager json configuration fragment used:

        {
            "Name": "fan0_connector",
            "Pwm": 0,
            "PwmName": "fan0_pwm",
            "Status": "enabled",
            "Tachs": [0],
            "Type": "FanConnector"
        },
        {
            "Name": "fan1_connector",
            "Pwm": 1,
            "PwmName": "fan1_pwm",
            "Status": "enabled",
            "Tachs": [1],
            "Type": "FanConnector"
        },
        {
            "Name": "fan2_connector",
            "Pwm": 2,
            "Status": "enabled",
            "Tachs": [2],
            "Type": "FanConnector"
        },

results when running ipmitool sdr list on BMC:

Pwm_3            | 99.96 unspecifi   | ok
fan0_pwm         | 99.96 unspecifi   | ok
fan1_pwm         | 99.96 unspecifi   | ok
fan0_tach        | 0 RPM             | ok
fan1_tach        | 0 RPM             | ok
fan2_tach        | 0 RPM             | ok

Signed-off-by: Jason Ling <jasonling@google.com>
Change-Id: I780c4f377e2e4f23567e1196ae420bf3c57c05f2