From: Sam Ravnborg <sam@ravnborg.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Jani Nikula <jani.nikula@intel.com>,
Joe Perches <joe@perches.com>, Sean Paul <sean@poorly.run>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 2/2] drm/print: document DRM_ logging functions
Date: Tue, 7 Jan 2020 19:17:52 +0100 [thread overview]
Message-ID: <20200107181752.GA20555@ravnborg.org> (raw)
In-Reply-To: <20200107160852.GD43062@phenom.ffwll.local>
Hi Daniel.
> > + * Logging when a &device * is available, but no &drm_device *
> > + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > + *
> > + * DRM/Drivers can use the following functions for logging when there is a
> > + * struct device * available.
> > + * The logging functions share the same prototype:
>
> I'd replace the entire block with a "This stuff is deprecated" warning. We
> have at least a corresponding todo.rst entry.
We have many situations where no drm_device is available.
At least when you a buried in drm_panel patches.
So it is either DRM_DEV_ERROR() or drv_err().
Which is why I have pushed for nicer drm_ variants of these...
The todo entry only covers the nice new macros that Jani added
where we have a drm_device.
Sam
> -Daniel
>
> > + *
> > + * .. code-block:: c
> > + *
> > + * void DRM_xxx(struct device *, char * fmt, ...)
> > + *
> > + * .. code-block:: none
> > + *
> > + * # Plain logging
> > + * DRM_DEV_INFO(dev, fmt, ...)
> > + * DRM_DEV_ERROR(dev, fmt, ...)
> > + *
> > + * # Log only once
> > + * DRM_DEV_INFO_ONCE(dev, fmt, ...)
> > + *
> > + * # Ratelimited - do not flood the logs
> > + * DRM_DEV_DEBUG_RATELIMITED(dev, fmt, ...)
> > + * DRM_DEV_DEBUG_DRIVER_RATELIMITED(dev, fmt, ...)
> > + * DRM_DEV_DEBUG_KMS_RATELIMITED(dev, fmt, ...)
> > + * DRM_DEV_DEBUG_PRIME_RATELIMITED(dev, fmt, ...)
> > + * DRM_DEV_ERROR_RATELIMITED(dev, fmt, ...)
> > + *
> > + * # Logging with a specific category
> > + * DRM_DEV_DEBUG(dev, fmt, ...) # Logged as CORE
> > + * DRM_DEV_DEBUG_DRIVER(dev, fmt, ...)
> > + * DRM_DEV_DEBUG_KMS(dev, fmt, ...)
> > + * DRM_DEV_DEBUG_PRIME(dev, fmt, ...)
> > + * DRM_DEV_DEBUG_ATOMIC(dev, fmt, ...)
> > + * DRM_DEV_DEBUG_VBL(dev, fmt, ...)
> > + * DRM_DEV_DEBUG_DP(dev, fmt, ...)
> > + *
> > + * Logging when no &device * nor &drm_device * is available
> > + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > + *
> > + * DRM/Drivers can use the following functions for logging when there is no
> > + * extra info associated to the logging.
> > + * The logging functions share the same prototype:
> > + *
> > + * .. code-block:: c
> > + *
> > + * void DRM_xxx(char * fmt, ...)
> > + *
> > + * .. code-block:: none
> > + *
> > + * # Plain logging
> > + * DRM_INFO(fmt, ...)
> > + * DRM_NOTE(fmt, ...)
> > + * DRM_WARN(fmt, ...)
> > + * DRM_ERROR(fmt, ...)
> > + *
> > + * # Log only once
> > + * DRM_INFO_ONCE(fmt, ...)
> > + * DRM_NOTE_ONCE(fmt, ...)
> > + * DRM_WARN_ONCE(fmt, ...)
> > + *
> > + * # Ratelimited - do not flood the logs
> > + * DRM_DEBUG_RATELIMITED(fmt, ...)
> > + * DRM_DEBUG_DRIVER_RATELIMITED(fmt, ...)
> > + * DRM_DEBUG_KMS_RATELIMITED(fmt, ...)
> > + * DRM_DEBUG_PRIME_RATELIMITED(fmt, ...)
> > + * DRM_ERROR_RATELIMITED(fmt, ...)
> > + *
> > + * # Logging with a specific category
> > + * DRM_DEBUG(fmt, ...) # Logged as CORE
> > + * DRM_DEBUG_DRIVER(fmt, ...)
> > + * DRM_DEBUG_KMS(fmt, ...)
> > + * DRM_DEBUG_PRIME(fmt, ...)
> > + * DRM_DEBUG_ATOMIC(fmt, ...)
> > + * DRM_DEBUG_VBL(fmt, ...)
> > + * DRM_DEBUG_LEASE(fmt, ...)
> > + * DRM_DEBUG_DP(fmt, ...)
> > */
> >
> > /**
> > @@ -399,7 +475,7 @@ __printf(3, 4)
> > void drm_dev_dbg(const struct device *dev, enum drm_debug_category category,
> > const char *format, ...);
> >
> > -/**
> > +/*
> > * Error output.
> > *
> > * @dev: device pointer
> > @@ -408,7 +484,7 @@ void drm_dev_dbg(const struct device *dev, enum drm_debug_category category,
> > #define DRM_DEV_ERROR(dev, fmt, ...) \
> > drm_dev_printk(dev, KERN_ERR, "*ERROR* " fmt, ##__VA_ARGS__)
> >
> > -/**
> > +/*
> > * Rate limited error output. Like DRM_ERROR() but won't flood the log.
> > *
> > * @dev: device pointer
> > @@ -436,7 +512,7 @@ void drm_dev_dbg(const struct device *dev, enum drm_debug_category category,
> > } \
> > })
> >
> > -/**
> > +/*
> > * Debug output.
> > *
> > * @dev: device pointer
> > @@ -466,7 +542,7 @@ void drm_dev_dbg(const struct device *dev, enum drm_debug_category category,
> > drm_dev_dbg(dev, category, fmt, ##__VA_ARGS__); \
> > })
> >
> > -/**
> > +/*
> > * Rate limited debug output. Like DRM_DEBUG() but won't flood the log.
> > *
> > * @dev: device pointer
> > --
> > 2.20.1
> >
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-01-07 18:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 22:15 [PATCH v2 0/2] drm: document logging functions Sam Ravnborg
2020-01-02 22:15 ` [PATCH v2 1/2] drm/print: document drm_ " Sam Ravnborg
2020-01-07 16:12 ` Daniel Vetter
2020-01-02 22:15 ` [PATCH v2 2/2] drm/print: document DRM_ " Sam Ravnborg
2020-01-07 16:08 ` Daniel Vetter
2020-01-07 18:17 ` Sam Ravnborg [this message]
2020-01-08 18:49 ` Daniel Vetter
2020-01-08 20:04 ` Sam Ravnborg
2020-01-08 20:50 ` Joe Perches
2020-01-12 22:48 ` Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200107181752.GA20555@ravnborg.org \
--to=sam@ravnborg.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=joe@perches.com \
--cc=sean@poorly.run \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.