summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/task-analyzer.py
diff options
context:
space:
mode:
authorAradhya Bhatia <a-bhatia1@ti.com>2025-03-29 14:39:20 +0300
committerDmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>2025-03-30 19:47:12 +0300
commita53d987756eab40678f241d7cd0eb7e1ca42bba7 (patch)
treed596d7e7f943c356caeea677306744130900b3f6 /tools/perf/scripts/python/task-analyzer.py
parentbc36ee983fb34962a407c06196cc7874bf408146 (diff)
downloadlinux-a53d987756eab40678f241d7cd0eb7e1ca42bba7.tar.xz
drm/bridge: cdns-dsi: Move DSI mode check to _atomic_check()
At present, the DSI mode configuration check happens during the _atomic_enable() phase, which is not really the best place for this. Moreover, if the mode is not valid, the driver gives a warning and continues the hardware configuration. Move the DSI mode configuration check to _atomic_check() instead, which can properly report back any invalid mode, before the _enable phase even begins. Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org> Reviewed-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> Tested-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> Signed-off-by: Aradhya Bhatia <a-bhatia1@ti.com> Signed-off-by: Aradhya Bhatia <aradhya.bhatia@linux.dev> Link: https://lore.kernel.org/r/20250329113925.68204-10-aradhya.bhatia@linux.dev Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions