From: Maxime Ripard <maxime@cerno.tech>
To: dri-devel@lists.freedesktop.org
Cc: David Airlie <airlied@linux.ie>,
Sean Paul <seanpaul@chromium.org>,
Maxime Ripard <maxime@cerno.tech>,
Thomas Zimmermann <tzimmermann@suse.de>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: [PATCH v2 0/4] drm/atomic: Atomic Private State debugging
Date: Fri, 25 Mar 2022 13:48:18 +0100 [thread overview]
Message-ID: <20220325124822.1785070-1-maxime@cerno.tech> (raw)
Hi,
This series adds an atomic_print_state hook for drm_private_obj to ease the
debugging of driver-specific sub-classes, and adds one for vc4.
It also changes the call site of drm_atomic_print_new_state to make it more
consistent.
Let me know what you think,
Maxime
Changes from v1:
- Added Daniel tags
- Added drm_private_state documentation
- Fixed unused variable warning
- Removed the drm_atomic_nonblocking_commit() logging
Maxime Ripard (4):
drm/atomic: Print the state every commit
drm/atomic: Add atomic_print_state to private objects
drm/vc4: Constify private state accessors
drm/vc4: Implement atomic_print_state for HVS channel state
drivers/gpu/drm/drm_atomic.c | 20 ++++++++++++++++++++
drivers/gpu/drm/drm_atomic_uapi.c | 4 ----
drivers/gpu/drm/vc4/vc4_kms.c | 24 +++++++++++++++++++++---
include/drm/drm_atomic.h | 27 +++++++++++++++++++++++----
4 files changed, 64 insertions(+), 11 deletions(-)
--
2.35.1
next reply other threads:[~2022-03-25 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 12:48 Maxime Ripard [this message]
2022-03-25 12:48 ` [PATCH v2 1/4] drm/atomic: Print the state every commit Maxime Ripard
2022-03-25 19:50 ` Daniel Vetter
2022-03-25 12:48 ` [PATCH v2 2/4] drm/atomic: Add atomic_print_state to private objects Maxime Ripard
2022-03-25 16:14 ` kernel test robot
2022-03-25 12:48 ` [PATCH v2 3/4] drm/vc4: Constify private state accessors Maxime Ripard
2022-03-25 12:48 ` [PATCH v2 4/4] drm/vc4: Implement atomic_print_state for HVS channel state Maxime Ripard
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=20220325124822.1785070-1-maxime@cerno.tech \
--to=maxime@cerno.tech \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=seanpaul@chromium.org \
--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