Icetea: config: bump bsp version to v3.4.0-1 and update sensors calibration for tps25990 and ltc4287

[joywu-coder]

Description

1. Bump the BSP version to 3.4.0-1 in the platform config.
2. Change the sensor sysfs path of MCB_PU925_TPS25990_XP12R0V_COME_VOUT from in2_input to in3_input due to bsp tps25990 driver updated.
3. Update the sensors' calibration of MCB_PU925_TPS25990_XP12R0V_COME_IIN and MCB_PU925_TPS25990_XP12R0V_COME_PIN to 0.274.
4. Update the sensors' calibration of FCB_XP48R0V_HOTSWAP_IOUT and FCB_XP48R0V_HOTSWAP_PIN to 1.8.

Motivation

1. According to the latest BSP tag, bump the BSP version to 3.4.0-1 in the platform config.
2. To align with the HW requirement, we need to adjust the sensors' calibration value in the sensor config.

Test Plan

1. The format has been verified as correct on the JSONLint website.
2. Used the jq command to pretty-print the format.
3. Test log as follows:

platform_manager_log.txt
platform_manager_hw_test_log.txt
sensor_service_log.txt
sensor_service_hw_test_log.txt
fan_service_log.txt
fan_service_hw_test_log.txt

[binhuang00]

@joywu-coder, as you updated the compute formula, should the "maxAlarmVal" and "upperCriticalVal" be updated too?

[joywu-coder]

@joywu-coder, as you updated the compute formula, should the "maxAlarmVal" and "upperCriticalVal" be updated too?

@binhuang00 Thanks for your comments. The original threshold(maxAlarmVal/upperCriticalVal) setting is expected; we only need to correct the formula factor.

[binhuang00]

Ditto, "maxAlarmVal" and "upperCriticalVal" should be updated too?

[joywu-coder]

Ditto, "maxAlarmVal" and "upperCriticalVal" should be updated too?

Same as above

[meta-codesync]

@binhuang00 has imported this pull request. If you are a Meta employee, you can view this in D85219459.

[meta-codesync]

@binhuang00 merged this pull request in dc359f9.