dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Maxime Ripard" <mripard@kernel.org>
To: "Dmitry Baryshkov" <dmitry.baryshkov@linaro.org>
Cc: freedreno@lists.freedesktop.org,
	Thomas Zimmermann <tzimmermann@suse.de>,
	linux-arm-msm@vger.kernel.org,
	Abhinav Kumar <quic_abhinavk@quicinc.com>,
	dri-devel@lists.freedesktop.org,
	Maxime Ripard <mripard@kernel.org>
Subject: Re: [PATCH 0/5] drm/msm: cleanup private obj handling
Date: Fri, 08 Sep 2023 06:59:55 +0000	[thread overview]
Message-ID: <79decdf3b3d30c90467b6048a5928cf7.mripard@kernel.org> (raw)
In-Reply-To: <20230908030521.236309-1-dmitry.baryshkov@linaro.org>

On Fri, 8 Sep 2023 06:05:16 +0300, Dmitry Baryshkov wrote:
> While debugging one of the features in DRM/MSM I noticed that MSM
> subdrivers still wrap private object access with manual modeset locking.
> Since commit b962a12050a3 ("drm/atomic: integrate modeset lock with
> private objects") this is no longer required, as the DRM framework
> handles private objects internally. Drop these custom locks, while also
> 
> [ ... ]

Reviewed-by: Maxime Ripard <mripard@kernel.org>

Thanks!
Maxime

      parent reply	other threads:[~2023-09-08  7:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08  3:05 [PATCH 0/5] drm/msm: cleanup private obj handling Dmitry Baryshkov
2023-09-08  3:05 ` [PATCH 1/5] drm/atomic: add private obj state to state dump Dmitry Baryshkov
2023-10-05 22:49   ` Rob Clark
2023-09-08  3:05 ` [PATCH 2/5] drm/msm/dpu: finalise global state object Dmitry Baryshkov
2023-09-08  3:05 ` [PATCH 3/5] drm/msm/dpu: drop global_state_lock Dmitry Baryshkov
2023-09-08  3:05 ` [PATCH 4/5] drm/msm/mdp5: migrate SMP dumping to using atomic_print_state Dmitry Baryshkov
2023-09-08  3:05 ` [PATCH 5/5] drm/msm/mdp5: drop global_state_lock Dmitry Baryshkov
2023-09-08  6:59 ` Maxime Ripard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=79decdf3b3d30c90467b6048a5928cf7.mripard@kernel.org \
    --to=mripard@kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=quic_abhinavk@quicinc.com \
    --cc=tzimmermann@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox