Intel Arc Pro B60: power*_crit is reported as max power while power*_cap is 200 W

On an Intel Arc Pro B60 using the xe driver, Mission Center reports 400 W as the maximum power value while the configured hwmon power cap is 200 W.

The card's hwmon device exposes:

power1_label=card
power1_cap=200000000
power1_crit=400000000
power1_max is absent

Linux hwmon documents power*_cap as the limit above which the system should reduce power use. It documents power*_crit as a critical maximum threshold that may trigger drastic action.

The Intel code in NVTOP commit 3d4a953da02bc18886734613bb9f60ff80669de7 falls back from power*_max to power*_crit for Battlemage and stores that value as power_draw_max. Mission Center 1.1.0 embeds this revision and displays the resulting 400 W value as the maximum.

Is power*_crit intended to represent the user-visible maximum in this case, or should NVTOP expose the configured power cap separately when both values differ?

Related change: https://github.com/Syllo/nvtop/pull/393

System details:

GPU: Intel Arc Pro B60 [8086:e211]
Driver: xe
Kernel: 7.1.3-ogc3.4.fc44.x86_64
Mission Center: 1.1.0 Flatpak
Embedded NVTOP commit: 3d4a953da02bc18886734613bb9f60ff80669de7

This was reproduced through Mission Center's embedded NVTOP backend. I have not reproduced it with a standalone nvtop binary.

Kernel hwmon documentation: https://docs.kernel.org/hwmon/sysfs-interface.html