Hi Maxime, On Fri Nov 6, 2026 at 2:14 PM CET, Maxime Ripard wrote: > drm_private_obj does not carry a human-readable name, which makes > debug messages hard to interpret when multiple private objects are > registered on the same device. > > Add a name field to drm_private_obj, passed through > drm_atomic_private_obj_init() and freed in > drm_atomic_private_obj_fini(). Update the existing callers to pass a > name. > > Reviewed-by: Maarten Lankhorst <[email protected]> > Signed-off-by: Maxime Ripard <[email protected]>
[...] > --- a/drivers/gpu/drm/drm_bridge.c > +++ b/drivers/gpu/drm/drm_bridge.c > @@ -319,4 +319,5 @@ static void __drm_bridge_free(struct kref *kref) > drm_bridge_put(bridge->next_bridge); > > + kfree(bridge->name); > kfree(bridge->container); > } > @@ -420,4 +421,11 @@ void *__devm_drm_bridge_alloc(struct device *dev, size_t > size, size_t offset, > > bridge = container + offset; > + > + bridge->name = kasprintf(GFP_KERNEL, "bridge-%s", dev_name(dev)); Ah, nice! I can't wait to use it in debugfs and a few other places! "%ps" bridge->funcs is OK-ish, but not great, and also does not differentiate multiple instances of the same driver. Reviewed-by: Luca Ceresoli <[email protected]> I wish I could test it but cannot apply the series even with all the depepndecies applied. :-/ Luca -- Luca Ceresoli, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
