diff options
| author | Jani Nikula <jani.nikula@intel.com> | 2025-03-21 15:51:14 +0300 |
|---|---|---|
| committer | Jani Nikula <jani.nikula@intel.com> | 2025-04-01 11:57:47 +0300 |
| commit | da1d515eb1692e87422caefb80799bd716070bbc (patch) | |
| tree | efe93154939141c182d465962db2fcaee8dc96ac /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 513c1a2ec4c6e520798f17b6d8af7a9881fdd69a (diff) | |
| download | linux-da1d515eb1692e87422caefb80799bd716070bbc.tar.xz | |
drm/i915/gvt: use hardcoded reference clocks
Usually I'd argue hardcoding values is the wrong thing to do, but in
this case, GVT looking deep into the guts of the DPLL manager for the
reference clocks is worse. This is done for BDW and BXT only, and there
shouldn't be any reason to try to be so dynamic about it.
This helps reduce the direct pokes at display guts from non-display
code.
Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Zhenyu Wang <zhenyuw.linux@gmail.com>
Link: https://lore.kernel.org/r/20250321125114.750062-1-jani.nikula@intel.com
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions