summaryrefslogtreecommitdiff
path: root/meta-facebook
AgeCommit message (Collapse)AuthorFilesLines
5 daysmeta-facebook: santabarbara: back up USB UART logs before BMC rebootFred Chen4-0/+52
USB UART console logs were being lost on chassis AC cycle and BMC reboot since they only lived in volatile storage. Back them up first so they are still available for debugging afterward. Change-Id: I2f9661cf1ac686e892b3aa75ed37c47c28b4c07e Signed-off-by: Fred Chen <Fred.Chen@quantatw.com>
5 daysmeta-facebook: santabarbara: move USB UART console logs to /run/logFred Chen61-122/+122
Logging to /var/log could block while the UBI background thread (ubi_bgt0d) was running garbage collection, and heavy UART traffic during that block could overflow the buffer. Move the log path to /run/log, which lives in memory and avoids the write block. Change-Id: I36799195bd6ce9898fd66a6540439bb77a6ba54e Signed-off-by: Fred Chen <Fred.Chen@quantatw.com>
5 daysmeta-facebook: sanmiguel: add leak detected LED indicationMike Hsieh2-1/+15
Configure the amber ID LED to blink when a leak is detected. This adds the `leak_detected` LED group configuration and modifies `critical-leak-assert-handler` to trigger it upon leak assertion. Change-Id: Ia0e47ba1cd508ef55e495986ea312282211ae46a Signed-off-by: Mike Hsieh <mike_hsieh@quantatw.com>
5 daysmeta-facebook: sanmiguel: support various leak types in assert handlerMike Hsieh3-26/+15
Enhance `critical-leak-assert-handler` to dynamically handle both small and large leak events by parsing the incoming sensor name. - Map SMA 10/20 leak sensors to large leak actions (request host power off and assert large leak GPIO). - Map SMA 40/60/70 leak sensors to small leak actions (assert small leak GPIO). Change-Id: I569f3e03ecee33395d7957782a186370f129b021 Signed-off-by: Mike Hsieh <mike_hsieh@quantatw.com>
5 daysmeta-facebook: sanmiguel: remove unused CX9 and Clover SMA reset codePotin Lai1-21/+0
A USB bus issue was observed during host power-on when resetting the Clover SMA. Resetting the Clover SMA during host power-on is not required, and NVIDIA has removed the corresponding reset sequence from the host power control specification. Remove the unused CX9 SMA and Clover SMA reset GPIO toggling from the host_power_on sequence in power-cmd to prevent USB bus issues. Change-Id: I4c37c18597a4696e7d15d92de802bb1637d5af19 Signed-off-by: Potin Lai <potin.lai@quantatw.com>
5 daysmeta-facebook: sanmiguel: Add an IOEXP driver binding check mechanismMik Lin1-0/+17
Add an IOEXP driver binding check mechanism to HPM0/1 (Bus70/71) to prevent the driver from failing to hang up properly due to abnormal conditions; this check is performed up to three times. Change-Id: If2598cff2d6edb03b58a4c4f83a932b70159a26f Signed-off-by: Mik Lin <mik.lin@quantatw.com>
5 daysmeta-facebook: sanmiguel: add MPS HSC configurationPotin Lai1-23/+61
Add MPS HSC configuration and enhance HSC error handling in platform-early-sys-init during early system init: - Add config_mps_hsc() to configure the IIN_TUNE (0x38) register on MPS HSCs via i2ctransfer. - Refactor config_ti_hsc() and config_mps_hsc() to loop through HSCs, track i2cset / i2ctransfer command failures, and return non-zero if any command fails. - Add retry logic (up to 3 attempts) in config_hsc() before reporting failure. Change-Id: I3295b90ea1b606bc1f490292a803f232721584fb Signed-off-by: Potin Lai <potin.lai@quantatw.com>
6 daysmeta-facebook: yosemite4: Early exit rescan-cxl-eid for ASIC-less boards.Andy Hsu1-0/+11
Description: Add logic to determine whether to rescan EIDs based on whether the FRU information contains "Wailua Falls without ASIC". Motivation: To support the additional Wailua Falls without ASIC boards, boards without ASIC do not require CXL EIDs. Change-Id: I0761f01f72e7d73f98517d497d31f476171e9bb3 Signed-off-by: Andy Hsu <andy.hsu.wiwynn@gmail.com>
7 daysmeta-facebook: yosemite5: clear Paddle HSC faults during system initJackson Liu1-0/+4
Clear Paddle HSC faults at the end of Paddle HSC initialization. This clears transient faults that may be triggered by noise during initialization and prevents them from being reported after BMC startup. Change-Id: Ie636a1583bfe5fb0e9f0fc249ccff7fcba285609 Signed-off-by: Jackson Liu <Jackson.Liu@quantatw.com>
7 daysmeta-facebook: clemente: use the Clemente device treeEmmanuel Blot1-4/+0
The Clemente device tree was merged in Linux v6.18 and linux-aspeed already tracks dev-6.18, so the temporary fallback to the Catalina device tree is no longer needed. Change-Id: I80cb2653b795b7fa398cf86fb774e6275390ffe1 Signed-off-by: Emmanuel Blot <emmanuel.blot@free.fr>
11 daysfb-ipmi-oem: srcrev bump 4579db69ec..9a1c70df74Andrew Geissler1-1/+1
Sean Lee (1): oemcommands: Add OEM commands for Boot-Time PPR Change-Id: I672b4a09701f2c2974977db9271335c7d6b0a2d9 Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
12 daysmeta-facebook: santabarbara: support NIC hotplugFrank Chen5-0/+207
Add NIC hotplug monitoring for NIC slots 0 through 4. Trigger FRU rescan on both insertion and removal events to dynamically discover or remove the corresponding NIC devices. Change-Id: Ic3ee8d020a6a6bde3db1cbe3ff5174c8328d030a Signed-off-by: Frank Chen <FrankChen4@quantatw.com>
13 daysmeta-facebook: sanmiguel: switch to common leak handler frameworkMike Hsieh5-41/+18
The reusable common framework for leak handling has already been implemented under meta-facebook. Update sanmiguel to use the common leak handler framework instead of maintaining a platform-specific implementation. This keeps the leak handling behavior aligned with the common layer implementation and reduces duplicated services. Change-Id: I067c1f53058155be94d5d4a9834946c1f325859f Signed-off-by: Mike Hsieh <mike_hsieh@quantatw.com>
13 daysmeta-facebook: santabarbara: Update calibrated FIO inlet temperature sensorHenry Wu1-0/+61
Update the conversion table to apply to FIOBOARD_REMOTE_INLET_TEMP_C instead of FIOBOARD_INLET_TEMP_C, in align with the thermal team's latest expectations. Change-Id: I25d9e4e1a44aae141399484b111f9ff0facc3fc9 Signed-off-by: Henry Wu <Henry_Wu@quantatw.com>
13 daysmeta-facebook: ventura2a7: initial commitKyle Hsieh15-40/+413
Add support for the new AST2700-based Ventura2A7 platform while maintaining compatibility with the existing AST2600-based Ventura2. Due to missing AST2700 Linux/U-Boot support in upstream, this config uses `linux-dummy` and bypasses image generation to serve as a placeholder. Change-Id: I7684c47ceff5b216821cd732d2178b130b8adfad Signed-off-by: Kyle Hsieh <Kyle.Hsieh@quantatw.com>
2026-08-25phosphor-bmc-code-mgmt: srcrev bump dad5ae57eb..484f77929fAndrew Geissler1-1/+1
Kyle Hsieh (1): spi-flash: introduce generic pattern for SPI devices Change-Id: I439f1795dc89aee25ed788b769486222b8c95172 Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com> Signed-off-by: Jagpal Singh Gill <paligill@gmail.com>
2026-08-24meta-facebook: meta-ventura2: check host presence in power-cmdKyle Hsieh1-0/+25
In Ventura2, different SKU configurations determine whether the COMe module is physically present. Currently, power-cmd executes GPIO toggles and enters wait-loops regardless of host presence. For SKUs without a COMe board, this leads to unnecessary 10-second timeouts and potential illegal GPIO accesses during power transitions. This commit introduces a host presence check using the mapper tool to verify the PRSNT_COMe inventory object. This allows the script to adapt dynamically to different hardware SKUs. Change-Id: I7cea1d99d0ced3367f199f38882bbb54b7c5fd74 Signed-off-by: Kyle Hsieh <Kyle.Hsieh@quantatw.com>
2026-08-21meta-facebook: ventura2: Add virtual sensors for SKU4 2ndKyle Hsieh3-2/+471
Summary: Add calibrated sensors for SKU4 2nd. Change-Id: I663560471b3f3b438c62d6d77093b64472e9f325 Signed-off-by: Kyle Hsieh <Kyle.Hsieh@quantatw.com>
2026-08-21meta-facebook: ventura2: fix host power cycleMichael Kao1-1/+5
When host power off or host power cycle is requested, the default phosphor-state-manager target dependency can also pull in chassis power off. Ventura2 does not support chassis power off, so this dependency can block host power off and host power cycle from completing properly. Remove the chassis power-off dependency from the host shutdown path. Tested on Ventura2 platform: ``` root@bmc-9082C307CDB8:~# mfg-tool power-control -p 0 -a off <6> Attempting runtime:off on 0. "success" root@bmc-9082C307CDB8:~# mfg-tool power-state <7> Finding chasses. <7> Iterating over entries. <7> Examining xyz.openbmc_project.State.Chassis at /xyz/openbmc_project/state/chassis0. <7> State for /xyz/openbmc_project/state/chassis0: on <7> Finding hosts. <7> Iterating over entries. <7> Examining xyz.openbmc_project.State.Host at /xyz/openbmc_project/state/host0. <7> State for /xyz/openbmc_project/state/host0: off { "0": { "runtime": "off", "standby": "on" } } ``` Change-Id: Ie0f5ff810601052feeca8585de481b5e35389a9d Signed-off-by: Michael Kao <michael.kao@quantatw.com>
2026-08-21meta-facebook: meta-ventura2: Add blacklist for FruDeviceKyle Hsieh2-0/+197
To improve Fru scanning efficiency for FruDevice. Change-Id: I1358e56581eefc195267769bb915fe73d833b673 Signed-off-by: Kyle Hsieh <Kyle.Hsieh@quantatw.com>
2026-08-21meta-facebook: rainiera7: Add system airflow virtual sensorNeil Cheng1-0/+52
Add the SYSTEM_AIRFLOW_CFM virtual sensor to report the system airflow based on the current fan duty. Change-Id: I23a5e91c317c6d9ed20311695f206d1db9729014 Signed-off-by: Neil Cheng <Neil.Cheng@quantatw.com>
2026-08-21meta-facebook: rainiera7: Add MB_CPU_TEMP_C UNRNeil Cheng1-1/+2
Add MB_CPU_TEMP_C UNR threshold requested by the thermal team. Change-Id: Ied2c53824870b80d1a28f9e06dd7cbdc16ad68cb Signed-off-by: Neil Cheng <Neil.Cheng@quantatw.com>
2026-08-21meta-facebook: rainiera7: Fix SCM board nameFrank Tsao1-1/+1
Fix SCM board name in virtual sensor configuration. Change-Id: Ibee903b7af7dca41d2a2bd336341cb75a0ea0dd5 Signed-off-by: Frank Tsao <Frank.Tsao@quantatw.com>
2026-08-21meta-facebook: rainiera6: Follow up layer migrationFrank Tsao5-14/+234
Follow up on the layer migration. Remove redundant content from fb-rainiera6-phosphor-image.inc. Restore platform-specific differences between rainiera6 and rainiera7: - i3c device path - spi path Change-Id: I0e0da1f14c17b346bed30b3f1a3db59c0337f44e Signed-off-by: Frank Tsao <Frank.Tsao@quantatw.com>
2026-08-21meta-facebook: meta-rainiera6: Move layer to meta-rainiera7Amithash Prasad44-3184/+5
This is the first commit to move the layer and have basic build functional. There might still be some redundancies which needs to be cleaned up in a subsequent commit. Change-Id: I31e350ad83a8119ec54e2a378020e84ccf86eaad Signed-off-by: Amithash Prasad <amithash@meta.com>
2026-08-20meta-facebook: meta-rainiera7: Bind kernel configs to aspeed-g7Amithash Prasad1-1/+1
Ensure that the kernel configs are used only by aspeed-g7 kernel which would prevent it from being used by rainiera6 which will in the future move to be a sub-layer Change-Id: Ie0647af803963692259dc84f2040d36e9b5474dc Signed-off-by: Amithash Prasad <amithash@meta.com>
2026-08-20meta-facebook: meta-rainiera7: Fix shellcheck point to wrong fileAmithash Prasad11-11/+11
shellcheck comment was pointing at `yosemite5-common-functions` instead of `fb-common-functions`. Also ensure we are using the new source instead. Also, some shellcheck comments were pointing at recipes-phosphor/state/phosphor-state-manager/power-cmd under `meta-yosemite5` layer instead of `meta-rainiera7` layer. Change-Id: I3dc0263be38722d49eebe23f369056cb1b1ebd2b Signed-off-by: Amithash Prasad <amithash@meta.com> Signed-off-by: Frank Tsao <Frank.Tsao@quantatw.com>
2026-08-20meta-facebook: meta-rainiera7: remove cxl from mctp setupFrank Tsao1-35/+0
Remove CXL from mctp setup as it is no need to support in Rainier platform. Hence sourcing yosemite5-commom-functions is not needed. Change-Id: Ibcb11b41193fba532785d0fb6a23d1153f51a56c Signed-off-by: Frank Tsao <Frank.Tsao@quantatw.com>
2026-08-20meta-facebook: yosemite4: Re-triggering console Connect after power-on/cycleSean He2-0/+2
Description: Add ExecStartPost busctl call to re-establish console connection after chassis power-on and power-cycle operations. Motivation: Host history logs were missing from /var/log/obmc-console-hostx.log after AC-cycling a slot if 'obmc-console-client -i hostX' had not been run beforehand. This occurs because when a UART mux switch happens (e.g. via 'obmc-console-client -i sd_bic<slot>' followed by an AC-cycle), the downstream console-id is not updated when the mux is switched back to the host. As a result, the console service does not reconnect to the correct host console, and host data is captured into obmc-console-sd-bicx.log by mistake. Tested: - Build code pass. - Verified obmc-chassis-poweron@.service and obmc-chassis-powercycle@.service successfully trigger the busctl Connect call via ExecStartPost after normal completion. - Reproduced the original issue by running 'obmc-console-client -i sd_bic<slot>' followed by an AC-cycle, and confirmed SOL history logs are now correctly generated in /var/log/ without requiring a manual 'obmc-console-client -i hostX' call. Change-Id: If046e9b9f59acfcc9f4dfa78b94f186ae62034fe Signed-off-by: Sean He <sean.he.wiwynn@gmail.com>
2026-08-20meta-facebook: yosemite4: Fix PMIC power-state updateEric Yang1-21/+6
Replace the service-list based check for an in-progress power-control operation with a lock-based check, and restore allow_force_off=true in the check-interrupt fallback path (interrupt fired, no VR fault bit set). Every power-control operation already holds a per-slot lock for its full duration, so checking that lock covers all of them without needing to track which services are involved. Motivation: The previous change [1] disabled force-off in this fallback path to fix a false DC-off during ACPI reset. That fallback path is also the only place the BMC learns about a real, unexpected DC-off that sets no VR fault bit, such as a PMIC error tripping CPLD's hardware protection directly. Disabling force-off fixed the ACPI reset case but left D-Bus power state stuck on for the PMIC-error case, even though the CPU had actually lost power. Tested: - PMIC error injection: BMC detects DC-off and updates power state - ACPI reset: lock held by the reset operation, interrupt skipped correctly - DC on/off/cycle: lock held by the respective operation, interrupt skipped Reference: [1] https://gerrit.openbmc.org/c/openbmc/openbmc/+/86077 Change-Id: I46bdcc3587bd7fbf7fce87f2a75375f29d6e7b8c Signed-off-by: Eric Yang <eric.yang.wiwynn@gmail.com>
2026-08-20meta-facebook: yosemite4: Keep console up across 12V offPete O_o1-1/+1
Description: Drop chassis-poweroff@@HOST_ID@.service from the obmc-console drop-in's Conflicts=, keeping only slot-unplug@@HOST_ID@.service. Motivation: On Yosemite4 chassis-poweroff@@HOST_ID@.service is the slot 12V/standby power-off path, so systemd stops the console server at the start of a 12V power cycle. An attached obmc-console-client dies within ~1s and the console stays blind for the whole ~115s power-off window, which is exactly when its output is most useful. With this change the console survives the power cycle. The start rate limit protection that motivated https://gerrit.openbmc.org/c/openbmc/openbmc/+/86809 comes from Conflicts=slot-unplug@@HOST_ID@.service, which is driven by the PRSNT_SB_SLOT<N>_N GPIO and is orthogonal to 12V state, so it is kept. Tested: - Build code - PASS - Host reset: Console stays connected - PASS - Slot unplug: Console disconnects - PASS - 12V off/on (mfg-tool power-control -p 6 -a cycle -s standby) with obmc-console-client -i host6 attached: client stays attached for the whole cycle and streams the host's POST checkpoints as 12V returns - PASS - systemctl show obmc-console@ttyS6.service -p Conflicts reports "slot-unplug@6.service shutdown.target", and systemctl show chassis-poweroff@6.service -p ConflictedBy is empty Change-Id: Iff7f00ae7fb08772ec4b394ec5415c3d2760bafa Signed-off-by: Pete O_o <pmb@meta.com>
2026-08-19meta-facebook: santabarbara: update blacklistHenry Wu1-1/+13
Update the blacklist for buses behind the I3C hub, as their bus numbers are dynamically assigned. Change-Id: I215546c67cffda696bd45586d7908d62f1a26473 Signed-off-by: Henry Wu <Henry_Wu@quantatw.com>
2026-08-17meta-facebook: santabarbara: enable ISL28022 driverFred Chen1-0/+1
Enable ISL28022 to support sensor reading. Change-Id: Ie70dd03b71e191606c50b7aaf91154e9a81afa32 Signed-off-by: Fred Chen <Fred.Chen@quantatw.com>
2026-08-13meta-sanmiguel: default drive host boot SSD reset pin high in early initPotin Lai2-9/+6
The host boot drive reset pin (BMC_SSD0_RST_L-O) does not require dynamic toggling by the BMC during host power state transitions. Move the configuration of BMC_SSD0_RST_L-O from power-cmd to platform-early-sys-init, setting the pin to HIGH (deasserting reset) by default during early BMC system initialization, and remove redundant reset pin control routines from host power operations. Change-Id: Ica4b7328c28566c593aaf9fde0aad23320ee087a Signed-off-by: Potin Lai <potin.lai@quantatw.com>
2026-08-13meta-sanmiguel: update Clover NIC MCTP EID to 72Potin Lai2-2/+2
Based on NVIDIA's 0.6.0 release, change the downstream Clover NIC MCTP Endpoint ID (EID) from 71 to 72 (2nd offset in the bridge pool). Update both the MCTP EID configuration script and the NIC sensor monitor script to align with this offset mapping. Detailed changes: - sma-mctp-eid-config: Update learn_clover_downstream_eid() to learn EID 72 (MCTP_EID + 2). - nic-sensor-read: Update the NS_NIC mapping entry from EID 71 to 72. Change-Id: I5e67551f5f22a3aba6009b7b5527c384fe8b85cc Signed-off-by: Potin Lai <potin.lai@quantatw.com>
2026-08-13fb-ipmi-oem: srcrev bump 2f24e3690e..4579db69ecAndrew Geissler1-1/+1
Elton Wang (1): selcommands: Add drive unifiedDriveErr Unified SEL Change-Id: Ie6f09c3ca78d6645a98ad58b3eb6ca0fbffcc0ed Signed-off-by: Andrew Geissler <openbmcbump-github@yahoo.com>
2026-08-13meta-facebook: yosemite5: update FruDevice blocklist for T22Elton Wang1-2/+49
Update the FruDevice blocklist to cover T22, adding entries for the new non-FRU devices on T22. - Bus 8: block non-FRU devices (0x21, 0x23, 0x26) on T22. - Bus 15: FRU EEPROM of the T22 storage expansion board (Rio Grande) is at 0x50. - Bus 38-71: block entire bus, as these T22-exclusive buses expose no FRU EEPROM. Change-Id: Icbe6dc701e54296da1d42869dd2aa28b6a8d18a5 Signed-off-by: Elton Wang <elton.wang.wiwynn@gmail.com>
2026-08-13meta-facebook: yosemite5a7: Add platform initialization for T22Jim Tsui1-1/+180
Description: - Add an early init service and script to configure yosemite5a7 GPIOs, set the IO expander interrupt mask on the Rio Grande board and configure HSCs at boot. - Use MB CPLD SKU to distinguish T22 and other yosemite5a7 platforms. Motivation: - Ensure GPIOs, IO expander interrupt settings and HSC settings are properly initialized for T22. Test: root@bmc:/usr/libexec# mfg-tool version-display <7> Finding software version objects. <7> Iterating over entries. <7> Examining xyz.openbmc_project.Software.Version at /xyz/openbmc_project/software/32415ef1. <7> Examining xyz.openbmc_project.Software.Version at /xyz/openbmc_project/software/OCP_CX7_NIC_0_NIC_7885. <7> Examining xyz.openbmc_project.Software.Version at /xyz/openbmc_project/software/OCP_CX7_NIC_0_NIC_Component_1_1680. <7> Examining xyz.openbmc_project.Software.Version at /xyz/openbmc_project/software/Yosemite5_BIOS_2496. <7> Examining xyz.openbmc_project.Software.Version at /xyz/openbmc_project/software/Yosemite5_MB_CPLD_1371. <7> Examining xyz.openbmc_project.Software.Version at /xyz/openbmc_project/software/Yosemite5_MB_VR_CPU0_MEM_6222. <7> Examining xyz.openbmc_project.Software.Version at /xyz/openbmc_project/software/Yosemite5_MB_VR_CPU1_6461. <7> Examining xyz.openbmc_project.Software.Version at /xyz/openbmc_project/software/Yosemite5_MB_VR_SOC_VDDIO_719. <7> Examining xyz.openbmc_project.Software.Version at /xyz/openbmc_project/software/Yosemite5_MB_VR_VDD18_S5_1034. <7> Examining xyz.openbmc_project.Software.Version at /xyz/openbmc_project/software/Yosemite5_PDB_CPLD_5124. <7> Examining xyz.openbmc_project.Software.Version at /xyz/openbmc_project/software/Yosemite5_Paddle_HSC1_P12V_AUX_1126. <7> Examining xyz.openbmc_project.Software.Version at /xyz/openbmc_project/software/Yosemite5_Paddle_HSC2_P12V_AUX_2440. <7> Examining xyz.openbmc_project.Software.Version at /xyz/openbmc_project/software/Yosemite5_Paddle_HSC3_P12V_AUX_3507. <7> Examining xyz.openbmc_project.Software.Version at /xyz/openbmc_project/software/Yosemite5_Paddle_HSC4_P12V_AUX_76. <7> Examining xyz.openbmc_project.Software.Version at /xyz/openbmc_project/software/Yosemite5_Paddle_HSC5_P12V_AUX_9790. <7> Examining xyz.openbmc_project.Software.Version at /xyz/openbmc_project/software/Yosemite5_Paddle_HSC7_P12V_AUX_9174. <7> Examining xyz.openbmc_project.Software.Version at /xyz/openbmc_project/software/Yosemite5_SCM_CPLD_5232. <7> Examining xyz.openbmc_project.Software.Version at /xyz/openbmc_project/software/Yosemite5_TPM_5776. { "OCP_CX7_NIC_0_NIC_7885": { "OCP_CX7_NIC_0_NIC_7885": "28.34.4000" }, "OCP_CX7_NIC_0_NIC_Component_1_1680": { "OCP_CX7_NIC_0_NIC_Component_1_1680": "28.34.4000" }, "Yosemite5_BIOS_2496": { "Yosemite5_BIOS_2496": "Unknown" }, "Yosemite5_MB_CPLD_1371": { "Yosemite5_MB_CPLD_1371": "F0210A02" }, "Yosemite5_MB_VR_CPU0_MEM_6222": { "Yosemite5_MB_VR_CPU0_MEM_6222": "4880" }, "Yosemite5_MB_VR_CPU1_6461": { "Yosemite5_MB_VR_CPU1_6461": "9215" }, "Yosemite5_MB_VR_SOC_VDDIO_719": { "Yosemite5_MB_VR_SOC_VDDIO_719": "7A0F" }, "Yosemite5_MB_VR_VDD18_S5_1034": { "Yosemite5_MB_VR_VDD18_S5_1034": "61A509E5" }, "Yosemite5_PDB_CPLD_5124": { "Yosemite5_PDB_CPLD_5124": "00030D09" }, "Yosemite5_Paddle_HSC1_P12V_AUX_1126": { "Yosemite5_Paddle_HSC1_P12V_AUX_1126": "51" }, "Yosemite5_Paddle_HSC2_P12V_AUX_2440": { "Yosemite5_Paddle_HSC2_P12V_AUX_2440": "51" }, "Yosemite5_Paddle_HSC3_P12V_AUX_3507": { "Yosemite5_Paddle_HSC3_P12V_AUX_3507": "51" }, "Yosemite5_Paddle_HSC4_P12V_AUX_76": { "Yosemite5_Paddle_HSC4_P12V_AUX_76": "51" }, "Yosemite5_Paddle_HSC5_P12V_AUX_9790": { "Yosemite5_Paddle_HSC5_P12V_AUX_9790": "51" }, "Yosemite5_Paddle_HSC7_P12V_AUX_9174": { "Yosemite5_Paddle_HSC7_P12V_AUX_9174": "51" }, "Yosemite5_SCM_CPLD_5232": { "Yosemite5_SCM_CPLD_5232": "00040D04" }, "Yosemite5_TPM_5776": { "Yosemite5_TPM_5776": "15.23" }, "bmc": "yosemite5a7-T22-plat-svc-test" } root@bmc:/usr/libexec# journalctl -u yosemite5-sys-init Mar 13 08:35:21 bmc systemd[1]: Starting Yosemite5 Early System Init... Mar 13 08:35:21 bmc Yosemite5 Early Init[1061]: Setting board product version to MB CPLD Mar 13 08:35:22 bmc Yosemite5 Early Init[1062]: find_fru_name: no FRU found for E1_S Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: Found SCM_board_2700 version: EVT Mar 13 08:35:22 bmc Yosemite5 Early Init[1097]: find_fru_name: no FRU found for Victoria_Falls Mar 13 08:35:22 bmc Yosemite5 Early Init[1115]: find_fru_name: no FRU found for Maple_Falls Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: MB CPLD Reg 0x18: Updated to 0x88 Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: MB CPLD Reg 0x17: Updated to 0x80 Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: initial value for GPIO output pins of T22 Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set HSC_OC_GPIO0 = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set HSC_OC_GPIO1 = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set HSC_OC_GPIO2 = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set HSC_OC_GPIO3 = 1 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_SMB_MUX = 1 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_SLOT_FLASH_R1 = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_1_R = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_1 = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_2_R = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_2 = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_3 = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_4 = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_5 = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_6 = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_7 = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_8 = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_9 = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_10 = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_3A_IOEXP5_AND3_R_N = 1 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_3A_IOEXP5_AND5_R_N = 1 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_3A_IOEXP5_AND7_R_N = 1 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_3A_IOEXP5_AND9_R_N = 1 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_3A_IOEXP5_AND10_R_N = 1 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_3A_IOEXP5_AND8_R_N = 1 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_3A_IOEXP5_AND6_R_N = 1 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_3A_IOEXP5_AND4_R_N = 1 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_3A_IOEXP5_AND2_R_N = 1 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_3A_IOEXP5_AND1_R_N = 1 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_3_R1 = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_4_R1 = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_5_R1 = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_6_R1 = 0 success Mar 13 08:35:22 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_7_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_8_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_9_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_10_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_11 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_12 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_13 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_14 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_15 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_16 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_17 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_18 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_2A_IOEXP4_AND12_R_N = 1 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_2A_IOEXP4_AND14_R_N = 1 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_2A_IOEXP4_AND16_R_N = 1 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_2A_IOEXP4_AND18_R_N = 1 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_2A_IOEXP4_AND17_R_N = 1 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_2A_IOEXP4_AND15_R_N = 1 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_2A_IOEXP4_AND13_R_N = 1 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_2A_IOEXP4_AND11_R_N = 1 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_11_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_12_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_13_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_14_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_15_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_16_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_17_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_18_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_19 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_20 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_21 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_22 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_23 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_24 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_25 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set PWRDIS_U2_26 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_1A_IOEXP4_AND20_R_N = 1 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_1A_IOEXP4_AND22_R_N = 1 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_1A_IOEXP4_AND24_R_N = 1 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_1A_IOEXP4_AND26_R_N = 1 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_1A_IOEXP4_AND25_R_N = 1 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_1A_IOEXP4_AND23_R_N = 1 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_1A_IOEXP4_AND21_R_N = 1 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_1A_IOEXP4_AND19_R_N = 1 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_19_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_20_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_21_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_22_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_23_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_24_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_25_R1 = 0 success Mar 13 08:35:23 bmc Yosemite5 Early Init[1061]: set_gpio: set EN_P12V_U2_26_R1 = 0 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: initial value for GPIO output pins Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set BMC_READY = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_DBP_CPU_PREQ_GF_N = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set JTAG_1_BMC_TRST = 0 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_CLKMUX_0_SEL = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_CLKMUX_1_SEL = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_CLKMUX_2_SEL = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_CLKMUX_3_SEL = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_CLKGEN_GPIO2 = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_CLKGEN_GPIO4 = 0 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_USB_HUB_0_N = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set SGPIO_RSTBTN_OUT = 0 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set IBB_BMC_SRST = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_I3C_SPD_AH_SEL_R = 0 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_I3C_SPD_IP_SEL_R = 0 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_JTAG_BMC_MUX_S0_R = 0 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_JTAG_BMC_MUX_S1_R = 0 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_JTAG_BMC_OE_1_R_N = 0 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_JTAG_BMC_OE_R_N = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_REMOTEJTAG_EN_R_N = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_CPU_FORCE_SELFREFRESH_R = 0 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_CPU_NMI_SYNC_FLOOD_R_N = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_CPU_TRIGGERTSC_OE_R_N = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_PASSWORD_CLEAR_R_N = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_BIOS_USB_RECOVERY_N = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_USB_MUX_OE_R_N = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_USB_MUX_SEL_R = 0 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_SMB_BOOT_R_N = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_SMB_MCIO0A_R_N = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set RST_SMB_NIC_R_N = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_PPS_NIC_IN_BUF_OE_R_N = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_PPS_NIC_IN_EN_R = 0 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_PPS_NIC_IN_OE_R_N = 1 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_PPS_NIC_IN_S0_R = 0 success Mar 13 08:35:24 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_PPS_NIC_IN_S1_R = 0 success Mar 13 08:35:25 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_PPS_NIC_OUT_BUF_OE_R_N = 1 success Mar 13 08:35:25 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_PPS_NIC_OUT_CPU_OE_R_N = 1 success Mar 13 08:35:25 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_PPS_NIC_OUT_EN_R = 0 success Mar 13 08:35:25 bmc Yosemite5 Early Init[1061]: set_gpio: set JTAG_CPLD_DBREQ_R_N = 1 success Mar 13 08:35:25 bmc Yosemite5 Early Init[1061]: set_gpio: set HDT_HDR_RESET_R_N = 1 success Mar 13 08:35:25 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_SMB_AUTH_MUX_OE_R_N = 1 success Mar 13 08:35:25 bmc Yosemite5 Early Init[1061]: set_gpio: set FM_SCM_LED_R_N = 1 success Mar 13 08:35:25 bmc Yosemite5 Early Init[1061]: set_gpio: set SGPIO_BMC_READY = 1 success Mar 13 08:35:25 bmc systemd[1]: yosemite5-sys-init.service: Deactivated successfully. Mar 13 08:35:25 bmc systemd[1]: Finished Yosemite5 Early System Init. Mar 13 08:35:25 bmc systemd[1]: yosemite5-sys-init.service: Consumed 2.800s CPU time over 3.243s wall clock time, 5.1M memory peak. root@bmc:~# i2cget -yf 69 0x2d 0x00 0x00 root@bmc:~# i2cget -yf 69 0x2d 0x0b 0x02 root@bmc:~# i2cget -yf 69 0x2e 0x00 0x00 root@bmc:~# i2cget -yf 69 0x2e 0x0b 0x02 root@bmc:~# i2cget -yf 70 0x2f 0x00 0x00 root@bmc:~# i2cget -yf 70 0x2f 0x0b 0x02 root@bmc:~# i2cget -yf 70 0x35 0x00 0x00 root@bmc:~# i2cget -yf 70 0x35 0x0b 0x02 root@bmc:~# i2cget -yf 15 0x26 0x20 0x00 root@bmc:~# i2cget -yf 15 0x26 0x22 0x00 root@bmc:~# i2cget -yf 15 0x26 0x23 0x00 root@bmc:~# i2cget -yf 15 0x26 0x24 0x00 root@bmc:~# i2cget -yf 12 0x26 0x20 0x00 root@bmc:~# i2cget -yf 12 0x26 0x22 0x00 root@bmc:~# i2cget -yf 12 0x26 0x23 0x00 root@bmc:~# i2cget -yf 12 0x26 0x24 0x80 root@bmc:~# i2cget -yf 2 0x26 0x20 0x00 root@bmc:~# i2cget -yf 2 0x26 0x22 0x00 root@bmc:~# i2cget -yf 2 0x26 0x23 0x00 root@bmc:~# i2cget -yf 2 0x26 0x24 0x00 Change-Id: I8095c511c311e7da19de0b899126d33b8f8ddb10 Signed-off-by: Jim Tsui <jim.tsui.wiwynn@gmail.com>
2026-08-12meta-facebook: ventura2: add power modbus devicesJagpal Singh Gill1-1/+115
Add the PSU, BBU, and CBU device instances (units, shelves, and power monitor modules) to the phosphor-modbus allowed devices list so they are probed on ventura2. Change-Id: I07d327ea773601df2887abe97a5d6d17563aba51 Signed-off-by: Jagpal Singh Gill <paligill@gmail.com>
2026-08-12meta-facebook: ventura2: u-boot: configure SPI2 CE1 AHB windowKyle Hsieh1-0/+1
By default on the ASPEED AST2600, the SPI2 CE1 memory segment window is closed (size set to 0). Consequently, when the Linux kernel SPI driver attempts to probe the secondary flash device (flash@1, used for the E810 NIC), it fails with a "CE1 window invalid" error and returns -EINVAL (-22) because no AHB memory space is allocated. To resolve this, update `CONFIG_BOOTCOMMAND` to manually configure the SPI2 CE1 segment register (0x1E631034) before executing the standard `bootspi` command. Writing `0x0FF00800` to this register allocates the upper 128MB of the SPI2 AHB mapping window (from 128MB to 256MB offset) to CE1. This provides the Linux kernel with a valid memory segment, allowing it to successfully probe and expose the secondary SPI flash. Change-Id: I21784432120363c18f82d7c32b02a0127025b95b Signed-off-by: Kyle Hsieh <Kyle.Hsieh@quantatw.com>
2026-08-12meta: ventura2: add RS485 rack shutdown support on leak detectionEldin Lee1-24/+72
Refactor rack power-off handling into separate Redfish and RS485-based implementations. Automatically select the power-off method at runtime. Use Redfish to request the Wedge400 RackSwitch to perform rack power-off when Redfish is deployed; otherwise use the existing RS485 control path. Change-Id: I53c235b778d9e04b40e6c9dcde549e7cbe5653aa Signed-off-by: Eldin Lee <eldin.lee@quantatw.com>
2026-08-12meta-facebook: yosemite5: add T22 drive fault LED groupsElton Wang1-0/+260
Define LED group configurations for each drive fault LED on the T22 storage expansion board (Rio Grande). This allows the drive fault LEDs to be controlled over D-Bus through the `xyz.openbmc_project.Led.Group` interface. Change-Id: I2a18cfef3713b3ac6fd2cbe8675301796e3a984d Signed-off-by: Elton Wang <elton.wang.wiwynn@gmail.com>
2026-08-07meta-facebook: yosemite5: add button press event loggingKevin Tung5-4/+103
Create a structured log entry when a button press is detected. The log records the button name and press duration to improve event visibility and debugging. Change-Id: If06b42369f7ad4fa5be285f04eee4c03d4694b94 Signed-off-by: Kevin Tung <kevin.tung.openbmc@gmail.com>
2026-08-07meta-facebook: yosemite5: init remote JTAG GPIOsCosmo Chou1-1/+3
- FM_JTAG_BMC_OE_1_R_N=0: Enable JTAG MUX routing to CPU. The actual signal output remains safely disabled by FM_REMOTEJTAG_EN_R_N=1. - JTAG_1_BMC_TRST=0: Hold JTAG TAP in reset by default. - FM_DBP_CPU_PREQ_GF_N=1: Deassert CPU PREQ by default. Change-Id: If90100af5211ccbe457565398a9d8b3ed46b8ccd Signed-off-by: Cosmo Chou <cosmo.chou@quantatw.com>
2026-08-07meta-facebook: yosemite5: remove redundant GPIO functionsCosmo Chou2-42/+5
Remove the duplicated `set_gpio` and `get_gpio` implementations from `yosemite5-common-functions` and source `fb-common-functions` instead. This standardizes GPIO handling and provides built-in retries. Change-Id: Id7382b26106e2c780842d63f7b744426f34f7d53 Signed-off-by: Cosmo Chou <cosmo.chou@quantatw.com>
2026-08-07meta-facebook: yosemite5: refactor power-good-drop handlersCosmo Chou3-69/+66
- Centralize HOST_STATE_* constants, get_host_prop() and set_host_prop() into power-cmd to eliminate duplicated inline busctl calls. - Replace systemctl-based is_service_busy() with variadic busctl loop; short-circuits on first busy unit, guards empty/failed ActiveState. - Check RequestedHostTransition=Off to skip power-good-drop handling during a BMC-commanded shutdown. - Directly set CurrentHostState to Running in deassert when physical power is ON but CurrentHostState is stuck at Off. Change-Id: I02b99148525eeb8389d9b01763dd59a76ebccfb8 Signed-off-by: Cosmo Chou <cosmo.chou@quantatw.com>
2026-08-07meta-facebook: rainiera7: Change the JSON file pathRQ Lai1-1/+1
Summary: Since Rainier does not inherit from YV5, it does not support multiple platforms. Therefore, we need to change the path to phosphor-multi-gpio-monitor.json for phosphor-multi-gpio-monitor. Tested: Aug 05 18:58:42 bmc systemd[1]: Started Phosphor Multi GPIO monitor. Aug 05 18:58:42 bmc phosphor-multi-gpio-monitor[981]: GPIO Line SOC_PORQ monitoring started Aug 05 18:58:42 bmc phosphor-multi-gpio-monitor[981]: GPIO Line SOC_RESETREQ monitoring started Aug 05 18:58:42 bmc phosphor-multi-gpio-monitor[981]: GPIO Line SOC_POST_COMPLETE_CPLD monitoring started Aug 05 18:58:42 bmc phosphor-multi-gpio-monitor[981]: GPIO Line SOC_SYS_PWRDN_CPLD monitoring started Aug 05 18:58:42 bmc phosphor-multi-gpio-monitor[981]: GPIO Line SOC_THRMTRIP_N_CPLD monitoring started Aug 05 18:58:42 bmc phosphor-multi-gpio-monitor[981]: GPIO Line wALL_POWER_OK_1 monitoring started Aug 05 18:58:42 bmc phosphor-multi-gpio-monitor[981]: GPIO Line ID_RST_BTN_BMC_R_N monitoring started Change-Id: I10680ca7153e886709998b244f7858a0aa67f9fd Signed-off-by: RQ Lai <r.q.lai@quantatw.com>
2026-08-07meta-facebook: ventura: Prevent IPv6 loss and extra IPv4 afterSue Wang1-5/+12
factory reset Run factory reset command with AC or reboot, BMC will lose IPv6 address. Move DUIDType setting to a separate drop-in config file, /run/systemd/network/00-bmc-${INTF_NAME}.networki.d/duid-ll.conf, to avoid being overwritten by phospher-network-mamger. Use "networkctl reload" instead of "systemctl restart systemd-networkd.service" to avoid a link-local IPv4 address being assigned by the kernel during service restart and not bein removed after DHCPv4 address is obtained. Change-Id: I152763950dd540fe8dd07d3b85078cb9000be7c1 Signed-off-by: Sue Wang <sue.wang@quantatw.com>
2026-08-06meta-facebook: rsyslog: delete imfile state on file movePete O_o1-0/+4
imfile keys its state files by inode, so every rotation of a console log leaves a stale state file behind in $WorkDirectory. Nothing reaps them, so on a long-lived BMC with chatty consoles they accumulate without bound and can eventually exhaust the filesystem they live on. Set deleteStateOnFileMove so imfile drops a state file when its log is rotated away. This bounds the state directory at one file per monitored input by construction, wherever $WorkDirectory happens to point. The rsyslog logrotate config already carries a workaround for this: an hourly logrotate-trigger.log rotation whose postrotate script trims the state directory down to 20 files. That workaround is tied to a hardcoded path, and so silently stops protecting anything if $WorkDirectory is ever pointed elsewhere. It can be removed once this change has propagated to deployed images. Tested: config validation (rsyslogd -N1) passes with the option applied to the generated per-console conf, on an AST2600 BMC running rsyslog 8.2512.0. Runtime reaping behaviour across rotations has not been observed yet. Change-Id: I8ec8998fe65696ba1afecab5859a2fa063cce5a9 Signed-off-by: Pete O_o <pmb@meta.com>
2026-08-05meta-facebook: ventura2: Add MaxValue/MinValue to RMC_AIR_FLOWKyle Hsieh7-7/+21
Add `MaxValue` and `MinValue` properties to the `RMC_AIR_FLOW` virtual sensor across all Ventura2 SKU configurations. Change-Id: I4e6606c2b1953e1028f2132bf9ba1a2e423b27e8 Signed-off-by: Kyle Hsieh <Kyle.Hsieh@quantatw.com>
generated by cgit v1.2.3 (git 2.39.0) at 2026-09-08 17:12:31 +0300