public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: ville.syrjala@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/6] drm: Give crtcs and planes actual names
Date: Tue, 17 Nov 2015 11:11:01 +0100	[thread overview]
Message-ID: <20151117101101.GP16848@phenom.ffwll.local> (raw)
In-Reply-To: <1447347146-31505-1-git-send-email-ville.syrjala@linux.intel.com>

On Thu, Nov 12, 2015 at 06:52:20PM +0200, ville.syrjala@linux.intel.com wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> I got sick and tired of staring at the line noise produced by drm.debug=0x1e,
> so I decided to give the crtcs and planes human readable names. Each driver
> can give whatever names it wants, and for i915 I gave something that makes
> some sense w.r.t. to the spec.
> 
> The only magic gotcha here is that if the driver dynamically allocates the
> name, it must be careful around drm_{crtc,plane}_cleanup() cause those
> guys just memset the entire structure to 0. I didn't want to put the kfree()
> into the cleanup functions to avoid having to kstrdup("") in the fallback
> case or forcing drivers to always use a dynamic allocation.

I avoiding the kstrdup("") is a bit a hack, especially since we could put
somethinig useful in there like "idx-%i", drm_plane_index(). The index is
used by a bunch of things (both internally and in ioctl structs), so
pretty handy.
-Daniel

> 
> Ville Syrjälä (6):
>   drm: Add crtc->name and use it in debug messages
>   drm: Add plane->name and use it in debug prints
>   drm/i915: Use crtc->name in debug messages
>   drm/i915: Use plane->name in debug prints
>   drm/i915: Set crtc->name to "pipe A", "pipe B", etc.
>   drm/i915: Give meaningful names to all the planes
> 
>  drivers/gpu/drm/drm_atomic.c         |  53 ++++++++-------
>  drivers/gpu/drm/drm_atomic_helper.c  |  60 +++++++++--------
>  drivers/gpu/drm/drm_crtc.c           |  11 ++-
>  drivers/gpu/drm/drm_crtc_helper.c    |  24 ++++---
>  drivers/gpu/drm/i915/intel_display.c | 127 +++++++++++++++++++++++------------
>  drivers/gpu/drm/i915/intel_fbdev.c   |   5 +-
>  drivers/gpu/drm/i915/intel_sprite.c  |  14 ++++
>  include/drm/drm_crtc.h               |   4 ++
>  8 files changed, 185 insertions(+), 113 deletions(-)
> 
> -- 
> 2.4.10
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2015-11-17 10:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 16:52 [PATCH 0/6] drm: Give crtcs and planes actual names ville.syrjala
2015-11-12 16:52 ` [PATCH 1/6] drm: Add crtc->name and use it in debug messages ville.syrjala
2015-11-12 16:52 ` [PATCH 2/6] drm: Add plane->name and use it in debug prints ville.syrjala
2015-11-12 16:52 ` [PATCH 3/6] drm/i915: Use crtc->name in debug messages ville.syrjala
2015-11-12 16:52 ` [PATCH 4/6] drm/i915: Use plane->name in debug prints ville.syrjala
2015-11-12 16:52 ` [PATCH 5/6] drm/i915: Set crtc->name to "pipe A", "pipe B", etc ville.syrjala
2015-11-12 16:52 ` [PATCH 6/6] drm/i915: Give meaningful names to all the planes ville.syrjala
2015-11-12 17:38   ` Emil Velikov
2015-11-12 17:49     ` Ville Syrjälä
2015-11-12 18:32       ` Ville Syrjälä
2015-11-17 10:11 ` Daniel Vetter [this message]
2015-11-17 10:20   ` [Intel-gfx] [PATCH 0/6] drm: Give crtcs and planes actual names Jani Nikula

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=20151117101101.GP16848@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox