Skip to content

[platform_manager] Implement AMD CPU_BUS resolution via ACPI#956

Draft
somasun wants to merge 1 commit into
mainfrom
amd-bus-branch
Draft

[platform_manager] Implement AMD CPU_BUS resolution via ACPI#956
somasun wants to merge 1 commit into
mainfrom
amd-bus-branch

Conversation

@somasun

@somasun somasun commented Feb 24, 2026

Copy link
Copy Markdown
Contributor

Summary:

Implement resolveAmdCpuBusNums() for AMD FireRange CPUs.
DesignWare I2C adapters share identical names, so bus
identification uses ACPI firmware_node/path under
/sys/devices/platform/AMDI0010:*. Maps _SB_.I2CA to
CPU_BUS@0 and _SB_.I2CB to CPU_BUS@1.

Also updates ConfigValidator to allow CPU_BUS@1 (needed
for AMD two-bus configs) and adds duplicate name detection.

Test Plan:

config_validator_test
i2c_explorer_test
tested on a unit

…rmware_node/path

Summary:
Implement resolveAmdCpuBusNums() for AMD FireRange CPUs.
DesignWare I2C adapters share identical names, so bus
identification uses ACPI firmware_node/path under
/sys/devices/platform/AMDI0010:*. Maps \_SB_.I2CA to
CPU_BUS@0 and \_SB_.I2CB to CPU_BUS@1.

Also updates ConfigValidator to allow CPU_BUS@1 (needed
for AMD two-bus configs) and adds duplicate name detection.

Test Plan:
config_validator_test
i2c_explorer_test
tested on a unit
@meta-codesync

meta-codesync Bot commented Feb 24, 2026

Copy link
Copy Markdown
Contributor

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

@somasun somasun marked this pull request as draft February 24, 2026 18:20
@srikrishnagopu

Copy link
Copy Markdown
Contributor

Vendor name on the title please.

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

2 participants