Files
DroidDeck/app
MaxsTechReview cc93ab51c5 Log the GPU ceiling and mid-session clock hold changes (#2893)
* Log the GPU ceiling, steps and mid-session clock hold changes

The clock log now records the GPU frequency steps and floor once in
its header, probes each limit file as readable or refused, and adds
the allowed GPU maximum to every sample in the CPU cur/max(of top)
style, so a vendor or thermal cap on the GPU ceiling shows up and
changes during a session are visible. Samples are unchanged when no
limit file is readable.

The limit reading is shared with the device info GPU clock range.

Turning the GPU clock hold on or off during a session now logs the
same line the session start logs.

* Ignore a zero GPU ceiling and log hold changes in order

A ceiling file that reads zero is no longer printed as a limit and is listed
as refused, matching how the step list is read. The hold state line is logged
under the same lock as the state change, so overlapping toggles cannot log
out of order.

* Find a GPU ceiling that turns readable later and probe step tables as tables

A ceiling file that read zero at session start is looked for again on each
sample until one is found, and the log notes where it came from. Step and
floor sources are probed with the same parser that reads them, so a table
with a leading zero is listed as readable.
2026-11-19 14:31:32 -05:00
..