diff options
| author | Maxime Ripard <[email protected]> | 2022-07-11 19:38:36 +0200 |
|---|---|---|
| committer | Maxime Ripard <[email protected]> | 2022-07-13 10:46:05 +0200 |
| commit | d87fbea50b819b76f180bc8420c5f9efa0670deb (patch) | |
| tree | 0ef829547c3f239d1244d01aac3978b997809ad1 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | 00ec947c144b374ceb3fe1b4bd2e9ea7454dd630 (diff) | |
drm/connector: Clarify when drm_connector_unregister is needed
The current documentation for drm_connector_unregister() mentions that
it's needed for connectors that have been registered through
drm_dev_register().
However, this was a typo and was meant to be drm_connector_register(),
which only applies to connectors registered after drm_dev_register() has
been called.
In addition, it was also mentioning that connectors are unregistered
automatically when drm_dev_unregister() is called. This part is a bit
misleading, since it might make it appear that
drm_connector_unregister() applies either to all connectors, or none of
them.
After discussing it with Daniel, it appears that we always need to call
drm_connector_unregister() on connectors that have been registered with
drm_connector_register(), but only those.
drm_connector_init() already mentions that it only needs
drm_connector_cleanup(), so let's clarify the drm_connector_register()
and drm_connector_unregister() documentation to point at each other, and
remove the misleading part about drm_dev_unregister().
Acked-by: Sam Ravnborg <[email protected]>
Acked-by: Thomas Zimmermann <[email protected]>
Signed-off-by: Maxime Ripard <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions