diff options
| author | Maxime Ripard <mripard@kernel.org> | 2026-08-21 16:39:30 +0200 |
|---|---|---|
| committer | Maxime Ripard <mripard@kernel.org> | 2026-08-31 15:17:53 +0200 |
| commit | f6aa529e3a40bc3f1ab333688fdef1ebf1922d6a (patch) | |
| tree | 95d7e107bff21327bda9ab993caac5ce0679070d /tools/perf/scripts/python/stackcollapse.py | |
| parent | 8cb4dca64006ccdad9188209aaf4ac225a6568a2 (diff) | |
| download | linux-f6aa529e3a40bc3f1ab333688fdef1ebf1922d6a.tar.gz linux-f6aa529e3a40bc3f1ab333688fdef1ebf1922d6a.zip | |
drm/msm: dpu1: Convert to atomic_create_state
The dpu1 crtc implementation provides a custom reset hook. However,
this hook only allocates the state, initializes it with
__drm_atomic_helper_crtc_reset(), and frees the previous state. It
does not perform any hardware reset.
Since this is exactly what the atomic_create_state hook is meant to
do, minus the old state cleanup which the caller handles, convert the
implementation to use atomic_create_state with
__drm_atomic_helper_crtc_state_init() instead.
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
Link: https://patch.msgid.link/20260821-drm-no-more-crtc-reset-v1-54-fb793475c05a@kernel.org
Signed-off-by: Maxime Ripard <mripard@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions
