提交 bd1fbef7 编写于 作者: D Daniel Vetter

drm/atomic: Make the kerneldoc a bit clearer

Crank up the warning a notch and point at the right set of locking
functions for atomic drivers.
Acked-by: NMaxime Ripard <mripard@kernel.org>
Signed-off-by: NDaniel Vetter <daniel.vetter@intel.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Maxime Ripard <mripard@kernel.org>
Cc: Thomas Zimmermann <tzimmermann@suse.de>
Cc: David Airlie <airlied@linux.ie>
Cc: Daniel Vetter <daniel@ffwll.ch>
Link: https://patchwork.freedesktop.org/patch/msgid/20201002075620.4157591-1-daniel.vetter@ffwll.ch
上级 0c503659
...@@ -1613,11 +1613,11 @@ static void __drm_state_dump(struct drm_device *dev, struct drm_printer *p, ...@@ -1613,11 +1613,11 @@ static void __drm_state_dump(struct drm_device *dev, struct drm_printer *p,
* to dmesg in case of error irq's. (Hint, you probably want to * to dmesg in case of error irq's. (Hint, you probably want to
* ratelimit this!) * ratelimit this!)
* *
* The caller must drm_modeset_lock_all(), or if this is called * The caller must wrap this drm_modeset_lock_all_ctx() and
* from error irq handler, it should not be enabled by default. * drm_modeset_drop_locks(). If this is called from error irq handler, it should
* (Ie. if you are debugging errors you might not care that this * not be enabled by default - if you are debugging errors you might
* is racey. But calling this without all modeset locks held is * not care that this is racey, but calling this without all modeset locks held
* not inherently safe.) * is inherently unsafe.
*/ */
void drm_state_dump(struct drm_device *dev, struct drm_printer *p) void drm_state_dump(struct drm_device *dev, struct drm_printer *p)
{ {
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册