Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

drm/bridge: adapt drm_bridge_add/remove() docs, mention the lingering list

The role of drm_bridge_add/remove() is more complex now after having added
the lingering list. Update the kdoc accordingly.

Also stop mentioning the global list(s) in the first line of the docs: the
most important thing to mention here is that bridges are registered and
deregistered, lists are just the type of container used to implement such
(de)registration.

Reviewed-by: Maxime Ripard <mripard@kernel.org>
Link: https://lore.kernel.org/r/20250915-drm-bridge-debugfs-removed-v9-3-6e5c0aff5de9@bootlin.com
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>

+10 -2
+10 -2
drivers/gpu/drm/drm_bridge.c
··· 294 294 EXPORT_SYMBOL(__devm_drm_bridge_alloc); 295 295 296 296 /** 297 - * drm_bridge_add - add the given bridge to the global bridge list 297 + * drm_bridge_add - register a bridge 298 298 * 299 299 * @bridge: bridge control structure 300 + * 301 + * Add the given bridge to the global list of bridges, where they can be 302 + * found by users via of_drm_find_bridge(). 300 303 * 301 304 * The bridge to be added must have been allocated by 302 305 * devm_drm_bridge_alloc(). ··· 355 352 EXPORT_SYMBOL(devm_drm_bridge_add); 356 353 357 354 /** 358 - * drm_bridge_remove - remove the given bridge from the global bridge list 355 + * drm_bridge_remove - unregister a bridge 359 356 * 360 357 * @bridge: bridge control structure 358 + * 359 + * Remove the given bridge from the global list of registered bridges, so 360 + * it won't be found by users via of_drm_find_bridge(), and add it to the 361 + * lingering bridge list, to keep track of it until its allocated memory is 362 + * eventually freed. 361 363 */ 362 364 void drm_bridge_remove(struct drm_bridge *bridge) 363 365 {