Hi Jani. > > + * > > + * Each of the debug logging macros use a specific category, and the logging > > + * is filtered by the drm.debug module parameter. The &drm_debug_category enum > > + * specifies the values for the interface. > > + * > > + * Each drm_dbg_<category> macro logs to a DRM_UT_<category> category, > > + * except drm_dbg() that logs to DRM_UT_DRIVER. > > * > > * Enabling verbose debug messages is done through the drm.debug parameter, each > > * category being enabled by a bit: > > * > > * - drm.debug=0x1 will enable CORE messages > > * - drm.debug=0x2 will enable DRIVER messages > > + * - drm.debug=0x4 will enable KMS messages > > + * - drm.debug=0x8 will enable PRIME messages > > + * - drm.debug=0x10 will enable ATOMIC messages > > + * - drm.debug=0x20 will enable VBL messages > > + * - drm.debug=0x40 will enable STATE messages > > + * - drm.debug=0x80 will enable LEASE messages > > + * - drm.debug=0x100 will enable DP messages > > Maybe document this stuff in enum drm_debug_category where they're > defined instead? For the logging user it is much more convinient to have the logging filtering explained in one place. The enum already tell part of the story but then the reader needs to hunt for the information. Sam _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
