[DRAFT]: add support for some Tegra NVDEC/NVENC/VIC monitoring, generic GPU usage, and EMC usage #1322
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I am opening this as a draft as it is not mergeable in its current state.
This PR adds support for some of the Nvidia Tegra system of chips that have NVDEC/NVENC/VIC stats available via
/sys/kernel/debug
interfaces. These are the same stats as used in tegrastats. They require that the current user be able to read from this directory (not the default) so I am looking for advise on implementing some sort of functionality that would allow for mangohud to read these files without needing to modify permissions on every reboot of that directory.This PR also adds generic support for reading the
CPU-therm
temperature sensors (also as used on the Tegra chips and potentially other SOCs)Finally, this PR also adds support for reading the GPU load from
/sys/devices/gpu.0/load
and a hardware specific frequency from/sys/devices/gpu.0/devfreq/57000000.gpu/cur_freq
(a loop could be added to find the required folder, similar to https://github.com/hakandundar34coding/system-monitoring-center/blob/e0c6246d38af487a378adf486eed61485eea7566/src/Gpu.py#L657-L663).As previously explained, this PR is not mergeable in its current state and I am looking for feedback on its contents and where each of these functionality can be best placed. I can split up the PR into separate PRs if desired based on feedback.
closes #864