refactor handleLeftOverTemplateVars

Handling of leftover template vars is only done on strings, the rest
of the function is just recursion to get there.

Break out some function overloads, which res

refactor handleLeftOverTemplateVars

Handling of leftover template vars is only done on strings, the rest
of the function is just recursion to get there.

Break out some function overloads, which results in smaller functions.

Tested: Existing and newly written unit tests pass.

Confirmed (via LSP) that the newly written overloads are actually called
in testcases.

Change-Id: Iefc496caca22a1495b2c3fdd6b39c0fe97ce1416
Signed-off-by: Alexander Hansen <alexander.hansen@9elements.com>

show more ...

configurations: nvidia: Fix cable cartridge name enumeration order

Summary:
In the current naming formula, the cable cartridge name
enumeration order is from HPM1 to HPM0, while in the NV switch,
th

configurations: nvidia: Fix cable cartridge name enumeration order

Summary:
In the current naming formula, the cable cartridge name
enumeration order is from HPM1 to HPM0, while in the NV switch,
the cable cartridge name enumeration order is from HPM0 to HPM1.

Cartridge NVLINK EEPROM bus and address in HPMs:
HPM1 I2C12 0x54
HPM1 I2C12 0x55
HPM0 I2C13 0x54
HPM0 I2C13 0x55

Therefore, this commit fixes the FRU device naming formula to
ensure correct ordering and aligns the order with the NV Switch.

Tested:
Check if the cable cartridge name enumeration order
is from HPM0 to HPM1.

root@bmc:~# busctl get-property xyz.openbmc_project.EntityManager \
/xyz/openbmc_project/inventory/system/board/\
NVIDIA_Cable_Cartridge_0/NVIDIA_CBC_FRU_0 \
xyz.openbmc_project.Configuration.EEPROM Bus Address
t 13
t 84

root@bmc:~# busctl get-property xyz.openbmc_project.EntityManager \
/xyz/openbmc_project/inventory/system/board/\
NVIDIA_Cable_Cartridge_1/NVIDIA_CBC_FRU_1 \
xyz.openbmc_project.Configuration.EEPROM Bus Address
t 13
t 85

root@bmc:~# busctl get-property xyz.openbmc_project.EntityManager \
/xyz/openbmc_project/inventory/system/board/\
NVIDIA_Cable_Cartridge_2/NVIDIA_CBC_FRU_2 \
xyz.openbmc_project.Configuration.EEPROM Bus Address
t 12
t 84

root@bmc:~# busctl get-property xyz.openbmc_project.EntityManager \
/xyz/openbmc_project/inventory/system/board/\
NVIDIA_Cable_Cartridge_3/NVIDIA_CBC_FRU_3 \
xyz.openbmc_project.Configuration.EEPROM Bus Address
t 12
t 85

Change-Id: Ia163cbfdf0eeeaacc162170662d43a3a75caf5e8
Signed-off-by: Kimi Chen <kimi.zy.chen@fii-foxconn.com>

show more ...

Alphabetize type list

Keeping this alphabetical prevents some merge conflicts.

Change-Id: Ie94ed765057f3ce871c554d464350129f46e0fad
Signed-off-by: Ed Tanous <etanous@nvidia.com>

add FlowMeter for coolant as inventory item

The purpose of the coolant FlowMeter is to measure various properties of
coolant flow such as pressure, temperature etc on the connected
valve train. Add

add FlowMeter for coolant as inventory item

The purpose of the coolant FlowMeter is to measure various properties of
coolant flow such as pressure, temperature etc on the connected
valve train. Add the coolant FlowMeter as an inventory item so it can
expose its related inventory properties.

Change-Id: I392bcd72a73412719d7d47481cf1670be690d837
Signed-off-by: Jagpal Singh Gill <paligill@gmail.com>

show more ...

entity-manager: Remove duplicate PIC32 export template

PIC32 export template entry was duplicated in devices.hpp.
Remove the redundant entry.

Change-Id: If2df7da9b04fddbe9ed3352cbb4a55e59ca2d0e0
Si

entity-manager: Remove duplicate PIC32 export template

PIC32 export template entry was duplicated in devices.hpp.
Remove the redundant entry.

Change-Id: If2df7da9b04fddbe9ed3352cbb4a55e59ca2d0e0
Signed-off-by: Nagavarapu Sai Pavan <saipavann@ami.com>

show more ...

configurations: harma_hdd_nvme: Enable PEC for NVMe sensors

Enable SMBus PEC (Packet Error Checking) for NVMe temperature sensors
to prevent incorrect sensor readings.

Change-Id: I4e55861157f417d91

configurations: harma_hdd_nvme: Enable PEC for NVMe sensors

Enable SMBus PEC (Packet Error Checking) for NVMe temperature sensors
to prevent incorrect sensor readings.

Change-Id: I4e55861157f417d919adce3299c86e7a5de838a7
Signed-off-by: Peter Yin <peter.yin@quantatw.com>

show more ...

configurations: anacapa: add T20 bridge board configuration

Description:
EVT2 bridge board also has T20 design, so new configuration needs
to be created for T20.
Adjust ambient temperature sensor n

configurations: anacapa: add T20 bridge board configuration

Description:
EVT2 bridge board also has T20 design, so new configuration needs
to be created for T20.
Adjust ambient temperature sensor naming for T16/T20.
Add retimer temperature sensor support for T20.

Tested:
Check that sensors can be created successfully.

Change-Id: I2679b4c487ff9b9e491a75b25ca23611794d1f27
Signed-off-by: Carl Lee <carl.lee@amd.com>

show more ...

configurations: anacapa: update SCM configuration

- Remove unused chassis intrusion configuration
- Update SCM EEPROM access to use dynamic bus/address
(required due to EEPROM address change in Re

configurations: anacapa: update SCM configuration

- Remove unused chassis intrusion configuration
- Update SCM EEPROM access to use dynamic bus/address
(required due to EEPROM address change in RevD)

Tested:
Verified SCM information can be created successfully

Change-Id: I7487aba79b5a04f76294447e655b8e695ee6887b
Signed-off-by: Carl Lee <carl.lee@amd.com>

show more ...

entity-manager: anacapa: add VR firmware information

Add MP29612 and MP2869 VR firmware information to enable
firmware updates.

Tested:
Confirmed that the VR objects are created on DBus and
visible

entity-manager: anacapa: add VR firmware information

Add MP29612 and MP2869 VR firmware information to enable
firmware updates.

Tested:
Confirmed that the VR objects are created on DBus and
visible via the software inventory on Anacapa hardware.

$ busctl tree xyz.openbmc_project.Software.I2CVR
`- /xyz
`- /xyz/openbmc_project
`- /xyz/openbmc_project/software
|- /xyz/openbmc_project/software/Anacapa_MB_VR_pvddcr_cpu0_p0_9401
|- /xyz/openbmc_project/software/Anacapa_MB_VR_pvddcr_cpu1_p0_6009
`- /xyz/openbmc_project/software/Anacapa_MB_VR_pvddcr_soc_p0_6697

Change-Id: I7f03ecb8e3167d57aafb1f49f952c99009be55c8
Signed-off-by: Dirk Chen <dirkchen@amd.com>

show more ...

configurations: anacapa: update MB VR PVDD33_S5_P0 sensor name and type

Description:
Update PVDD33_S5_P0 sensor name and sensor type to match the actual
hardware design.

The sensor at address 0x46

configurations: anacapa: update MB VR PVDD33_S5_P0 sensor name and type

Description:
Update PVDD33_S5_P0 sensor name and sensor type to match the actual
hardware design.

The sensor at address 0x46 corresponds to MPQ8785 and represents
PVDD33_S5_P0.

Tested:
Verified that the MB VR PVDD33_S5_P0 sensor is created successfully.

MB_VR_CPU_PVDD33_S5_P0_CURR_A ok 0.875 Amperes
MB_VR_CPU_PVDD33_S5_P0_TEMP_C ok 31 DegreesC
MB_VR_CPU_PVDD33_S5_P0_VIN_VOLT_V ok 12.2 Volts
MB_VR_CPU_PVDD33_S5_P0_VOUT_VOLT_V ok 3.293 Volts

Change-Id: Ia3f58c61894b864de393a3edf9f49a641a487811
Signed-off-by: Carl Lee <carl.lee@amd.com>

show more ...

Add support for PCF85053 RTC device

Add support for PCF85053 RTC device in entity-manager to enable dynamic
RTC configuration for modular platforms (1S/2S/4S). This allows RTC
devices behind MUX's t

Add support for PCF85053 RTC device

Add support for PCF85053 RTC device in entity-manager to enable dynamic
RTC configuration for modular platforms (1S/2S/4S). This allows RTC
devices behind MUX's to be properly managed instead of being hardcoded
in device tree, which doesn't work for modular configurations where RTC
is accessed through different I2C bus paths.

Tested:
1S and 2S platforms - RTC devices are properly detected and functional.
:~# dmesg | grep rtc
[ 1.763117] rtc-pcf85053 12-006f: registered as rtc0
[ 1.770755] rtc-pcf85053 12-006f: setting system clock to
2025-10-31T06:20:21 UTC (1761891621)
Command: :~# timedatectl
Local time: Wed 2025-11-05 04:30:45 UTC
Universal time: Wed 2025-11-05 04:30:45 UTC
RTC time: Wed 2025-11-05 04:30:45
Time zone: UTC (UTC, +0000)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no

Change-Id: Ibd00c190614d5bc8e33a4a1926e89c5872a2cb00
Signed-off-by: Jayaprakash Mutyala <mutyalax.jayaprakash@intel.com>
Signed-off-by: poram srinivasa rao <poramx.srinivasa.rao@intel.com>
Signed-off-by: Ed Tanous <etanous@nvidia.com>

show more ...

fru-device: use lg2::error instead of cerr

An old commit was rebased and applied without testing. It does not
compile due to other refactoring that migrated from cerr to lg2.
Adjust the correspondi

fru-device: use lg2::error instead of cerr

An old commit was rebased and applied without testing. It does not
compile due to other refactoring that migrated from cerr to lg2.
Adjust the corresponding log statement in fru-device.

Fixes: 1cd0b0440109 ("fru-device: use ioctl to write fru for 16-bit address")
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I465624f40f553f184b53294d5c355aff28d238e9

show more ...

fru-device: use ioctl to write fru for 16-bit address

smbus commands only support eeproms with 8-bit address [1]. this patch
checks device address type and uses ioctl if uses 16-bit addressing.

tes

fru-device: use ioctl to write fru for 16-bit address

smbus commands only support eeproms with 8-bit address [1]. this patch
checks device address type and uses ioctl if uses 16-bit addressing.

tested on 24AA64 eeprom.

[1] https://docs.kernel.org/i2c/smbus-protocol.html -> command byte is
only 8 bits.

Change-Id: Iff999acab7c8d04757826a389af3e5f19759bd0b
Signed-off-by: Robin Cheng <rocheng@nvidia.com>

show more ...

Revert "configurations: yosemite4: Add additional allowed probe conditions"

This reverts commit 41ce5ab0eb4c04ada2ec44aa273eb97688cf639f.

Reason for revert: After internal discussion, it was conclu

Revert "configurations: yosemite4: Add additional allowed probe conditions"

This reverts commit 41ce5ab0eb4c04ada2ec44aa273eb97688cf639f.

Reason for revert: After internal discussion, it was concluded that keeping the current FRU name NCT is sufficient and no additional support for the FRU name NUV is required.

Change-Id: I2827e9c8d44a1473193f47ddea453227761bf1ad
Signed-off-by: Andy Hsu <andy.hsu.wiwynn@gmail.com>

show more ...

entity-manager: Fix addValueToDBus permission handling

The addValueToDBus() helper was hardcoding the property permission to
readOnly for non-array values, ignoring the permission argument passed
by

entity-manager: Fix addValueToDBus permission handling

The addValueToDBus() helper was hardcoding the property permission to
readOnly for non-array values, ignoring the permission argument passed
by the caller.

Update the implementation to honor the provided permission so that
properties can be correctly registered as read-write when required.

Inspection:

callers of addValueToDBus:
- populateInterfacePropertyFromJson

callers of populateInterfacePropertyFromJson:
- EMDBusInterface::populateInterfaceFromJson

callers of EMDBusInterface::populateInterfaceFromJson:
```
1 src/entity_manager/dbus_interface.cpp|369 col 5
2 src/entity_manager/entity_manager.cpp|182 col 20
3 src/entity_manager/entity_manager.cpp|194 col 28
4 src/entity_manager/entity_manager.cpp|273 col 24
5 src/entity_manager/entity_manager.cpp|285 col 24
6 src/entity_manager/entity_manager.cpp|309 col 20
7 src/entity_manager/entity_manager.cpp|329 col 24
8 src/entity_manager/entity_manager.cpp|372 col 28
```

1 is 'AddObject' use-case and sets read-write permission.
See no issue with it since that seems to be the intent of 'AddObject',
to be able to modify config externally.

2,3 uses default overload with read-only permission => no changes

inside `EntityManager::postExposesRecordsToDBus`
4,5,6 uses getPermission function to determine permission

inside `EntityManager::postConfigurationRecord`:
7,8 uses getPermission function to determine permission

`getPermission` looks at `settableInterfaces` which are
```
static constexpr std::array<const char*, 6> settableInterfaces = {
"FanProfile", "Pid", "Pid.Zone", "Stepwise", "Thresholds", "Polling"};
```

Tested: on Tyan S8030 (with full board, chassis, psu configs)

Using following script to dump the full EM D-Bus tree:
```
busctl tree --system xyz.openbmc_project.EntityManager --list |
while read -r obj; do
echo "### $obj"
busctl introspect --xml-interface xyz.openbmc_project.EntityManager "$obj"
done
```

which will dump everything similar to below format:
```
<interface name="xyz.openbmc_project.Configuration.Port">
<property name="Name" type="s" access="read">
</property>
<property name="PortType" type="s" access="read">
</property>
<property name="Type" type="s" access="read">
</property>
</interface>
```

step 1: dump without this change (master branch,
1f08ce74119b4cbd97e542e11eefc5fe99de9d94)

```
./em-recursive-permission.sh > busctl-em-output-master.txt
```

As expected, with the unpatched code the `getPermission` function only
has effect on the array properties of the intended 'settable'
interfaces. For example Type 'Pid' is intended settable but only a few
properties are actually read-write.

```
<interface name="xyz.openbmc_project.Configuration.Pid">
<property name="Class" type="s" access="read">
</property>
<property name="FFGainCoefficient" type="d" access="read">
</property>
<property name="FFOffCoefficient" type="d" access="read">
</property>
<property name="ICoefficient" type="d" access="read">
</property>
<property name="ILimitMax" type="d" access="read">
</property>
<property name="ILimitMin" type="d" access="read">
</property>
<property name="Inputs" type="as" access="readwrite">
<annotation name="org.freedesktop.systemd1.Privileged" value="true"/>
...
```

step 2: dump with this change
```
./em-recursive-permission.sh > busctl-em-output-permission-fixed.txt
```

```
diff busctl-em-output-master.txt busctl-em-output-permission-fixed.txt | wc -l
2466
```

Now the effect of 'getPermission' function fully appears
```
<interface name="xyz.openbmc_project.Configuration.Pid">
<property name="Class" type="s" access="readwrite">
<annotation name="org.freedesktop.systemd1.Privileged" value="true"/>
</property>
<property name="FFGainCoefficient" type="d" access="readwrite">
<annotation name="org.freedesktop.systemd1.Privileged" value="true"/>
</property>
<property name="FFOffCoefficient" type="d" access="readwrite">
<annotation name="org.freedesktop.systemd1.Privileged" value="true"/>
</property>
<property name="ICoefficient" type="d" access="readwrite">
<annotation name="org.freedesktop.systemd1.Privileged" value="true"/>
</property>
<property name="ILimitMax" type="d" access="readwrite">
<annotation name="org.freedesktop.systemd1.Privileged" value="true"/>
</property>
<property name="ILimitMin" type="d" access="readwrite">
<annotation name="org.freedesktop.systemd1.Privileged" value="true"/>
</property>
<property name="Inputs" type="as" access="readwrite">
<annotation name="org.freedesktop.systemd1.Privileged" value="true"/>
</property>
```

Setting the property works but returns a false error:
```
root@s8030-bmc-30303035c0c1:~# busctl set-property xyz.openbmc_project.EntityManager /xyz/openbmc_project/inventory/system/chassis/MBX_1_57_Chassis/Fan_Control xyz.openbmc_project.Configuration.Pid FFGainCoefficient d 4.0
Failed to set property FFGainCoefficient on interface xyz.openbmc_project.Configuration.Pid: Invalid argument
root@s8030-bmc-30303035c0c1:~# busctl get-property xyz.openbmc_project.EntityManager /xyz/openbmc_project/inventory/system/chassis/MBX_1_57_Chassis/Fan_Control xyz.openbmc_project.Configuration.Pid FFGainCoefficient
d 4
```

Trying the same for array properties works as well, same bug (unrelated
to this change).
```
busctl set-property xyz.openbmc_project.EntityManager /xyz/openbmc_project/inventory/system/chassis/MBX_1_57_Chassis/Fan_Control xyz.openbmc_project.Configuration.Pid Outputs as 4 "Pwm 3" "Pwm 4" "Pwm 5" "Pwm 6"
Failed to set property Outputs on interface xyz.openbmc_project.Configuration.Pid: Invalid argument
root@s8030-bmc-30303035c0c1:~# busctl get-property xyz.openbmc_project.EntityManager /xyz/openbmc_project/inventory/system/chassis/MBX_1_57_Chassis/Fan_Control xyz.openbmc_project.Configuration.Pid Outputs
as 4 "Pwm 3" "Pwm 4" "Pwm 5" "Pwm 6"
```

Since it's currently impossible to search for usages of D-Bus interfaces
in OpenBMC [1], it may not be possible to make things read-only without
breaking anyone. Passing through the intended permission is more
consistent, the correct permission has to be set by the caller.

References:

[1] https://gerrit.openbmc.org/c/openbmc/docs/+/86505/comments/d00a8148_e38bbdf8

Change-Id: I8372e5068cd18da3c336f793ca2478d5d1002fde
Signed-off-by: Nagavarapu Sai Pavan <saipavann@ami.com>
Signed-off-by: Alexander Hansen <alexander.hansen@9elements.com>

show more ...

entity-manager: Skip retries for removed D-Bus objects during scan

Detect when GetAll fails with EBADR (errno 53) and skip retry logic
instead of exhausting all retry attempts. This error code corre

entity-manager: Skip retries for removed D-Bus objects during scan

Detect when GetAll fails with EBADR (errno 53) and skip retry logic
instead of exhausting all retry attempts. This error code corresponds
to org.freedesktop.DBus.Error.UnknownObject and indicates the target
object was removed between GetSubTree enumeration and the subsequent
GetAll property fetch.

Log the condition at info level to provide visibility without flooding
error logs, as concurrent object removal is expected during device
hotplug or FRU rescanning operations.

Motivation:
Entity manager performs asynchronous D-Bus enumeration by first calling
GetSubTree to discover objects, then scheduling Properties.GetAll calls
to retrieve properties. If devices are removed during this window, for
example during multi-slot power cycles or FRU rescans, GetAll fails
because the target object no longer exists.

The existing retry mechanism treats all errors uniformly, exhausting
five retries with two-second delays (totaling ten seconds per removed
object) before giving up. When many objects churn concurrently, these
retries accumulate and significantly extend scan completion time.

sdbusplus obtains the mapped errno from sd-bus via message.get_errno()
and converts it to a boost::system::error_code for callers. Detecting
EBADR lets the scan logic treat the failure as an object removed
condition and skip futile retries, reducing scan latency and log noise
during device churn.

Change-Id: I87ab1979a190734d321e580370779bff1b26ebd2
Signed-off-by: Eric Yang <eric.yang.wiwynn@gmail.com>

show more ...

configurations: yosemite5: update PDB and paddle sensor name

Update PDB and paddle sensor names to comply Meta naming rule.

Tested on Yosemite5; sensor readings are correct.

Change-Id: I9b568669a6

configurations: yosemite5: update PDB and paddle sensor name

Update PDB and paddle sensor names to comply Meta naming rule.

Tested on Yosemite5; sensor readings are correct.

Change-Id: I9b568669a69a24ca50d8e1379d5f98388b02bc7a
Signed-off-by: Jackson Liu <Jackson.Liu@quantatw.com>

show more ...

configurations: yosemite4: Add additional allowed probe conditions

Description
Add additional FSC-NUV probe conditions.

Motivation
Changes have been made to the new FRU.

Change-Id: I0339f676ea41c8

configurations: yosemite4: Add additional allowed probe conditions

Description
Add additional FSC-NUV probe conditions.

Motivation
Changes have been made to the new FRU.

Change-Id: I0339f676ea41c8acb232fe22994778a1b0891cdc
Signed-off-by: Andy Hsu <andy.hsu.wiwynn@gmail.com>

show more ...

meta-facebook: minerva: change the voltage threshold of fans

Change the voltage threshold of fans because the previous values are
wrong, then cause the threshold assertion.

Change-Id: I9186aec4e675

meta-facebook: minerva: change the voltage threshold of fans

Change the voltage threshold of fans because the previous values are
wrong, then cause the threshold assertion.

Change-Id: I9186aec4e6755da11d6afd194a667fe463e2d21c
Signed-off-by: Yang Chen <yang.chen@quantatw.com>

show more ...

configurations: clemente_hdd: Remove HDD CPLD firmware config

Description:
Temporarily remove the HDD CPLD firmware configuration, because
during an AC power cycle, the phosphor-cpld-software-update

configurations: clemente_hdd: Remove HDD CPLD firmware config

Description:
Temporarily remove the HDD CPLD firmware configuration, because
during an AC power cycle, the phosphor-cpld-software-update
daemon reads the CPLD version during device initialization,
which causes SSD devices to be lost during the Host BIOS PCIe
enumeration process.

Change-Id: I5e03adf43581f6a3493b6b2ef9d76219f87d12ee
Signed-off-by: Kimi Chen <kimi.zy.chen@fii-foxconn.com>

show more ...

configuration: Add Axiado SCM configs

These json configurations provides 1 temperature sensor on Axiado
SCM3003 and 2 temperature sensors on Axiado SCM3002 for AX3000 SoC
family

Tested on Axiado SC

configuration: Add Axiado SCM configs

These json configurations provides 1 temperature sensor on Axiado
SCM3003 and 2 temperature sensors on Axiado SCM3002 for AX3000 SoC
family

Tested on Axiado SCM3002:
busctl tree xyz.openbmc_project.EntityManager

|- /xyz/openbmc_project/inventory/system/board/SCM3002/DCSCM_0_Temp
`- /xyz/openbmc_project/inventory/system/board/SCM3002/DCSCM_1_Temp

Change-Id: I4eabcc4ae722a96762f7d4a19c5ff76650d38829
Signed-off-by: Kuan-Jui Chiu <kchiu@axiado.com>

show more ...

Create Inventory.Item with boardNameOrig as parent

In EntityManager::postBoardToDBus, use boardNameOrig as the parent when
creating the initial xyz.openbmc_project.Inventory.Item interface so it
mat

Create Inventory.Item with boardNameOrig as parent

In EntityManager::postBoardToDBus, use boardNameOrig as the parent when
creating the initial xyz.openbmc_project.Inventory.Item interface so it
matches the parent used by subsequent interfaces for the same device.

Motivation:
EMDBusInterface::inventory groups interfaces by the “parent” string
passed to createInterface, and getDeviceInterfaces / pruneConfiguration
access that grouping using device["Name"].

Previously, the first interface for a device (Inventory.Item) was
grouped under the underscored, sanitized name, while the rest were
grouped under the non-sanitized name. This split a single device across
two inventory groups, so pruning removed only the non-sanitized group
and left the underscored group behind.

By creating the initial Inventory.Item with boardNameOrig, all
interfaces for a device land under a single key, pruneConfiguration
removes them together, and re-scan/re-add no longer accumulates stray
interfaces.

Change-Id: I01abb26ff139d6aa802d9161113b54777f8861fb
Signed-off-by: Eric Yang <eric.yang.wiwynn@gmail.com>

show more ...

configurations: santabarbara: add PDB2 HSC MP5998 sensor

Add mp5998 HSC sensor support for P12V AUX voltage and current
monitoring.

Change-Id: I9b05f445c7a79668cd3f3e1a9418e9dd31e9c651
Signed-off-b

configurations: santabarbara: add PDB2 HSC MP5998 sensor

Add mp5998 HSC sensor support for P12V AUX voltage and current
monitoring.

Change-Id: I9b05f445c7a79668cd3f3e1a9418e9dd31e9c651
Signed-off-by: Fred Chen <Fred.Chen@quantatw.com>

show more ...

schemas: legacy: add iin scale and offset support

Add iin_Scale and iin_Offset to legacy schema to support input current
calibration for psu sensors.

Change-Id: Ic411d6d9149a385a335c5de04d52e45ffe2

schemas: legacy: add iin scale and offset support

Add iin_Scale and iin_Offset to legacy schema to support input current
calibration for psu sensors.

Change-Id: Ic411d6d9149a385a335c5de04d52e45ffe24c6af
Signed-off-by: Fred Chen <Fred.Chen@quantatw.com>

show more ...

meson: reformat with meson formatter

Apply the `meson format` results.

Change-Id: I0bad72781974fbf4d87f1dc6a6bb68ed7568da24
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>