summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-sql.py
diff options
context:
space:
mode:
authorVille Syrjälä <ville.syrjala@linux.intel.com>2018-10-03 21:42:10 +0300
committerVille Syrjälä <ville.syrjala@linux.intel.com>2018-10-04 20:21:40 +0300
commit9dbf5a4efd8afa2b831b0f76b4f9cab9480af817 (patch)
treeb55ec1da021de117ffa5b06b01e8bea30daa9d9e /tools/perf/scripts/python/call-graph-from-sql.py
parent0fc645f338e3e1a4ee05e5529d86ac596c5921b6 (diff)
downloadkernel-9dbf5a4efd8afa2b831b0f76b4f9cab9480af817.tar.gz
drm/i915: Provide more clues as to why MST is/is not used
Always print out the information whether the port and sink can each do MST. And let's include the modparam in the debug output as well. Makes life a little less confusing when you don't have to wonder why MST isn't kicking in. This does cause a slight change in our behaviour towards the sink. Previously we only read the MSTM_CAP register after passing all the other checks. Now we will read that register regardless. Hopefully some crazy sink doesn't get confused by a simple register read. Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20181003184210.1306-1-ville.syrjala@linux.intel.com Reviewed-by: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-sql.py')
0 files changed, 0 insertions, 0 deletions