STRUCT AMDXDNA_DRM_QUERY_SENSOR(9)
π NAME
struct amdxdna_drm_query_sensor β literally the data for one single sensor. that's it. that's the whole vibe β¨
π SYNOPSIS
struct amdxdna_drm_query_sensor {
__u8 label[64];
__u32 input;
__u32 max;
__u32 average;
__u32 highest;
__u8 status[64];
__u8 units[16];
__s8 unitm;
__u8 type;
__u8 pad[6];
};
okay so bestie, this is a struct, and it's giving "little info card for exactly one sensor" π«Ά
πΈ Members
labelβ the name for a sensor. like its little nametag π (it's__u8 label[64], so 64 bytes of name, keep it cute and keep it short)inputβ the current value of the sensor. the right now number, the main character reading πmaxβ the maximum value possible for the sensor. the ceiling, the limit, the "it cannot go higher than this" β¨averageβ the average value of the sensor. the chill middle-ground number πhighestβ the highest recorded sensor value for this driver load for the sensor. ngl this one's a brag β it's the peak, but only for this driver load specifically, so don't go quoting it like it's an all-time record πstatusβ the sensor status. how it's doing, emotionally and electrically π (__u8 status[64])unitsβ the sensor units. the "what are we even measuring here" field π¦ (__u8 units[16])unitmβ translates value member variables into the correct unit via(pow(10, unitm) * value). yes bestie, it's a power-of-ten multiplier, the math is literally right there in the manual, i'm not making it up π§ (it's signed,__s8, so it can go negative, slay)typeβ the sensor type fromenum amdxdna_sensor_type. it's an enum, iykyk πΈpadβ structure padding. it's__u8 pad[6], it does nothing, it's just there for the alignment vibe check π
π₯ SEE ALSO
the whole squad, fr fr β kernel file ./include/uapi/drm/amdxdna_accel.h plus all these iconic structs:
struct amdxdna_drm_create_hwctx(9)struct amdxdna_drm_destroy_hwctx(9)struct amdxdna_cu_config(9)struct amdxdna_hwctx_param_config_cu(9)struct amdxdna_drm_config_hwctx(9)struct amdxdna_drm_va_entry(9)struct amdxdna_drm_va_tbl(9)struct amdxdna_drm_create_bo(9)struct amdxdna_drm_get_bo_info(9)struct amdxdna_drm_sync_bo(9)struct amdxdna_drm_exec_cmd(9)struct amdxdna_drm_wait_cmd(9)struct amdxdna_drm_query_aie_status(9)struct amdxdna_drm_query_aie_version(9)struct amdxdna_drm_query_aie_tile_metadata(9)struct amdxdna_drm_query_aie_metadata(9)struct amdxdna_drm_query_clock(9)struct amdxdna_drm_query_clock_metadata(9)struct amdxdna_drm_query_hwctx(9)struct amdxdna_drm_get_power_mode(9)struct amdxdna_drm_query_firmware_version(9)struct amdxdna_drm_get_resource_info(9)struct amdxdna_drm_attribute_state(9)struct amdxdna_drm_query_telemetry_header(9)struct amdxdna_drm_get_info(9)struct amdxdna_drm_hwctx_entry(9)struct amdxdna_async_error(9)struct amdxdna_drm_bo_usage(9)struct amdxdna_drm_get_array(9)struct amdxdna_drm_set_state(9)struct amdxdna_drm_set_power_mode(9)
lowkey reminder bestie:input,max,averageandhighestare all in the sensor's own units β if you're staring at a number and it looks unhinged, checkunitmandunitsbefore you @ anyone π
anyway that's the whole page, mwah π β this came from ./include/uapi/drm, dated October 2026, and yes it's filed under struct amdx...query_sensor(9) because the kernel truncated the name and honestly? iconic. periodt. π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms