Hexagon: Bump HMX Frequency to Max Corner

[trivikram-reddy1]

Overview

HMX is currently running at the lowest frequency corner, this PR bumps HMX Frequency to max corner.

Additional information

Should give a nice boost to prefill TPS

Results from Snapdragon Gen 5

Llama-3.1-8B-Instruct-Q4_0

Before:
common_perf_print: prompt eval time =    2193.53 ms /   256 tokens (    8.57 ms per token,   116.71 tokens per second)
common_perf_print:        eval time =    2314.84 ms /    31 runs   (   74.67 ms per token,    13.39 tokens per second)

After:
common_perf_print: prompt eval time =    1721.29 ms /   256 tokens (    6.72 ms per token,   148.73 tokens per second)
common_perf_print:        eval time =    2327.55 ms /    31 runs   (   75.08 ms per token,    13.32 tokens per second)

Llama-3.2-1B-Instruct-Q4_0

Before:
common_perf_print: prompt eval time =     383.28 ms /   256 tokens (    1.50 ms per token,   667.93 tokens per second)
common_perf_print:        eval time =     489.70 ms /    31 runs   (   15.80 ms per token,    63.30 tokens per second)

After:
common_perf_print: prompt eval time =     287.79 ms /   256 tokens (    1.12 ms per token,   889.54 tokens per second)
common_perf_print:        eval time =     480.15 ms /    31 runs   (   15.49 ms per token,    64.56 tokens per second)

Requirements

• I have read and agree with the contributing guidelines
• AI usage disclosure: NO

[trivikram-reddy1]

@max-krasnyansky @lhez could you please review/approve this

[mediouni-m]

Documentation says:

HAP_power_hmx_payload_v2 is supported starting with v75. On chipsets (v75 onwards) without separate HMX clock plan, requests made for target corner or frequency will return AEE_EBADPARM (invalid parameter) error.

How does this apply to this case? Especially for v73 platforms

[trivikram-reddy1]

@mediouni-m, thanks for catching the bug, this does not apply for v73 platforms, I will submit a patch shortly

[max-krasnyansky]

@mediouni-m, thanks for catching the bug, this does not apply for v73 platforms, I will submit a patch shortly

Yep, I missed this during review. Then ran into this issue on my MS Surface with X-Elite (Hexagon v73).