Dennis HilkLinux diagnosticsDE

Chipsets & PCIe

AMD PMC platform sleep context

A module/platform context for AMD s2idle coordination; it is not an exact PCI product-ID match.

Editorial source review: Share public profileOpen in the identification tool
On this page
  1. Overview & identity
  2. Driver & binding
  3. Firmware
  4. Read-only diagnostics
  5. Limitations & related issues
  6. References

Overview & identity

This generic profile deliberately has no curated PCI match. amd_pmc is a platform driver with ACPI matching and CPU/root-device context in its implementation. A PCI root-device table used internally is not the same thing as a PCI driver binding table for an independent PMC endpoint.

This is an explicit class, transport or driver-context profile. It is not an exact numeric product match.

A numeric match establishes a candidate family within the reviewed evidence. Marketing names, board variants, subsystem conditions and successful operation remain separate questions.

Driver & binding

The driver coordinates s2idle transactions with platform firmware on the SMU. The Kconfig text describes its AMD notebook role and debug support. Distinguish system sleep-mode selection, a device callback that aborts suspend and a successful suspend with poor residency; these are different observations, even if amd_pmc appears in the log.

  • amd_pmc — kernel driver/module candidate

Detected, bound, operational: learn the difference

Firmware

Device/revision dependent

The driver exchanges commands and version information with the platform SMU. The checked sources establish firmware participation but not a universal host-loaded image name. A failed SMU response should retain its exact message and platform context rather than prompting a guessed firmware file download.

Inspect firmware packaging on your distribution

Read-only diagnostics

Run one displayed command at a time. Replace uppercase placeholders with the affected device, interface or module from your own output. Commands are never executed here. Read-only output can still contain private identifiers.

Read the selected system sleep mode

cat /sys/power/mem_sleep

This read-only file normally needs no sudo. The bracketed mode is the current selection; an available s2idle entry does not prove successful low-power residency. Reading does not suspend the machine or change the mode.

Read platform-driver associations

ls -l /sys/bus/platform/drivers/amd_pmc

This read-only listing normally needs no sudo. A bound platform-device link is stronger ownership evidence than a generic PCI product label. An absent directory can reflect the kernel build, ACPI match or initialization state; it is not proof that every AMD system needs this driver.

Read current-boot controller messages

journalctl -k -b --no-pager

Retain amd_pmc/SMU messages with the suspend callback sequence and selected sleep mode. Journal access may require local group membership; failure to read it is not controller failure.

Limitations & related issues

A loaded amd_pmc module does not identify a particular laptop, prove a successful low-power state or measure battery drain. This profile does not trigger suspend, reset SMU logs, change wake sources or prescribe a kernel parameter. Platform-specific failures require their own trace and firmware context.

These guides are linked for relevant observations, not as known defects of every device in this family.

Choose a hardware diagnostic workflow · Inspect a log excerpt in Fix Lab

References

Source review records a checked implementation or document, not a reproduced hardware test. Version-specific tables do not establish a minimum kernel or guaranteed operation.