Skip to content

[Accton][m6060actl] Initial Configuration for M6060ACTL Data Corral Service - #1863

Open
brandonchuang wants to merge 1 commit into
meta:mainfrom
brandonchuang:m6060actl_led_mgr
Open

brandonchuang wants to merge 1 commit into
meta:mainfrom
brandonchuang:m6060actl_led_mgr

Conversation

@brandonchuang

Copy link
Copy Markdown
Contributor

Pre-submission checklist

  • I've ran the linters locally and fixed lint errors related to the files I modified in this PR. You can install the linters by running pip install -r requirements-dev.txt && pre-commit install
  • pre-commit run
    clang-format.........................................(no files to check)Skipped
    shellcheck...........................................(no files to check)Skipped
    shfmt................................................(no files to check)Skipped
    trim trailing whitespace.................................................Passed
    fix end of files.........................................................Passed
    check yaml...........................................(no files to check)Skipped
    check json...............................................................Passed
    check for merge conflicts................................................Passed
    ruff check...........................................(no files to check)Skipped
    ruff format..........................................(no files to check)Skipped
    Check copyright headers in new FBOSS C/C++ files.....(no files to check)Skipped
    Prevent sai_impl in fboss manifest.......................................Passed

Summary

Add the initial led_manager.json configuration for the M6060ACTL platform, which drives data_corral_service. It defines the system status LED, the per-FRU-type LEDs, and the FRU presence detection used to set those LEDs. The configuration was validated on actual M6060ACTL hardware.

Description

Included all LED and FRU presence definitions in led_manager.json for M6060ACTL:

  • System LED: blue when present / amber when absent, driven through the sys_led sysfs brightness paths.
  • Per-FRU-type LEDs: present (blue) / absent (amber) LED paths for the FAN, PSU, and SMB FRU types.
  • FRU presence detection: the four fans via the fan CPLD presence bits, and the power brick (PSU) and SMB via the MCB CPLD power-good bits, so each FRU's LED reflects its actual presence.

Test Plan

  • data_corral_service — started data_corral_service with this config on M6060ACTL and confirmed FRU presence and LED state are reported correctly.
    data_corral_service.txt
  • data_corral_service_hw_test — all test items passed on M6060ACTL hardware.
    data_corral_service_hw_test.txt

…ervice

### Summary
Add the initial `led_manager.json` configuration for the M6060ACTL platform, which
drives `data_corral_service`. It defines the system status LED, the per-FRU-type
LEDs, and the FRU presence detection used to set those LEDs. The configuration was
validated on actual M6060ACTL hardware.

### Description
Included all LED and FRU presence definitions in `led_manager.json` for M6060ACTL:

- **System LED**: blue when present / amber when absent, driven through the
  `sys_led` sysfs brightness paths.
- **Per-FRU-type LEDs**: present (blue) / absent (amber) LED paths for the `FAN`,
  `PSU`, and `SMB` FRU types.
- **FRU presence detection**: the four fans via the fan CPLD presence bits, and the
  power brick (`PSU`) and `SMB` via the MCB CPLD power-good bits, so each FRU's LED
  reflects its actual presence.

### Test Plan
- **data_corral_service** — started `data_corral_service` with this config on
  M6060ACTL and confirmed FRU presence and LED state are reported correctly.
- **data_corral_service_hw_test** — all test items passed on M6060ACTL hardware.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant