A recent change to the OCC hwmon driver modified the default behavior to no longer poll the OCC during initialization. This does change the interface, meaning that old applications will not work with the more recent driver. To resolve this issue, introduce a new dts property to control the behavior of the driver during initialization, similar to the FSI master property "no-scan-on-init". Without the new "ibm,inactive-on-init" boolean present, the driver will now do the previous behavior of polling the OCC. Eddie James (3): dt-bindings: hwmon: Add IBM OCC bindings fsi: occ: Support probing the hwmon child device from dts node hwmon: (occ) Check for device property for setting OCC active during probe .../bindings/hwmon/ibm,occ-hmwon.yaml | 40 ++++++++++++++++++ drivers/fsi/fsi-occ.c | 41 +++++++++++++++---- drivers/hwmon/occ/common.c | 11 ++++- drivers/hwmon/occ/p9_sbe.c | 9 ++++ 4 files changed, 93 insertions(+), 8 deletions(-) create mode 100644 Documentation/devicetree/bindings/hwmon/ibm,occ-hmwon.yaml -- 2.31.1