Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions rootfs/usr/share/powerstation/platform/amd_apu_database.toml
Original file line number Diff line number Diff line change
Expand Up @@ -561,3 +561,9 @@ model_name = "AMD Ryzen 3 8540U w/ Radeon 740M Graphics"
min_tdp = 5.0
max_tdp = 30.0
max_boost = 0.0

[[models]]
model_name = "AMD Ryzen AI MAX+ 395"
min_tdp = 5.0
max_tdp = 90.0

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently we don't have a way to detect if a device is attached to a fast charger or external cooling. To ensure safe operation until we can do that I'd prefer to limit this to the safe DC with native cooling max TDP for now.

TBS, this chip has a much higher TDP in some desktop like applications we don't want to throttle. This value should instead be set to the silicon max TDP per AMD, then device specific overrides should populate from the vendor database to keep the known handhelds under safe levels.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dtibragimov@hercules:/var/home/dtibragimov$ lscpu | grep 'Model name'
Model name:                              AMD RYZEN AI MAX+ 395 w/ Radeon 8060S

hence: model_name = "AMD RYZEN AI MAX+ 395 w/ Radeon 8060S"

in order to not break the devices for usual users: max_tdp should be equal 55w or 80w, 90 could overheat the device

as soon as the TDP becomes avialable in SteamOS QAM, it would be possible to change TDP manually above, say, 55w?

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

dtibragimov@hercules:/var/home/dtibragimov$ udevadm info -a /sys/class/dmi/id

Udevadm info starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/devices/virtual/dmi/id':
    KERNEL=="id"
    SUBSYSTEM=="dmi"
    DRIVER==""
    ATTR{bios_date}=="01/29/2026"
    ATTR{bios_release}=="0.14"
    ATTR{bios_vendor}=="American Megatrends International, LLC."
    ATTR{bios_version}=="0.14"
    ATTR{board_asset_tag}=="Default string"
    ATTR{board_name}=="ONEXPLAYER APEX"
    ATTR{board_serial}=="(not readable)"
    ATTR{board_vendor}=="ONE-NETBOOK"
    ATTR{board_version}=="Standard"
    ATTR{chassis_asset_tag}=="Default string"
    ATTR{chassis_serial}=="(not readable)"
    ATTR{chassis_type}=="37"
    ATTR{chassis_vendor}=="Default string"
    ATTR{chassis_version}=="Default string"
    ATTR{ec_firmware_release}=="0.12"
    ATTR{power/control}=="auto"
    ATTR{power/runtime_active_time}=="0"
    ATTR{power/runtime_status}=="unsupported"
    ATTR{power/runtime_suspended_time}=="0"
    ATTR{product_family}=="ONEXPLAYER"
    ATTR{product_name}=="ONEXPLAYER APEX"
    ATTR{product_serial}=="2603020301851"
    ATTR{product_sku}=="1"
    ATTR{product_uuid}=="(not readable)"
    ATTR{product_version}=="Standard"
    ATTR{sys_vendor}=="ONE-NETBOOK"

max_boost = 5.1