@@ -511,14 +511,12 @@ There's a bunch of issues with it:
- Convert drivers to support the drm_debugfs_add_files() function instead of
the drm_debugfs_create_files() function.
-- Improve late-register debugfs by rolling out the same debugfs pre-register
- infrastructure for connector and crtc too. That way, the drivers won't need to
- split their setup code into init and register anymore.
-
-- We probably want to have some support for debugfs files on crtc/connectors and
- maybe other kms objects directly in core. There's even drm_print support in
- the funcs for these objects to dump kms state, so it's all there. And then the
- ->show() functions should obviously give you a pointer to the right object.
+- Convert drivers to use the kms object debugfs helpers, such as
+ drm_debugfs_connector_add_files(), instead of the drm_debugfs_create_files()
+ function on late register hooks.
+
+- We probably want to have some support for debugfs files on planes, like we
+ have for crtc, connectors, and encoders.
- The drm_driver->debugfs_init hooks we have is just an artifact of the old
midlayered load sequence. DRM debugfs should work more like sysfs, where you
The structs drm_debugfs_connector_entry, drm_debugfs_encoder_entry, and drm_debugfs_crtc_entry introduced a debugfs infrastruture that made it possible to remove late-register debugfs. So, update the debugfs clean up task to include the advances for the kms objects and point out possible improvements to be done. Signed-off-by: Maíra Canal <mcanal@igalia.com> --- Documentation/gpu/todo.rst | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-)