Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/8] drm/i915: Make the intel_device_info structure kept in dev_priv writable
Date: Mon, 10 Feb 2014 10:09:11 +0100	[thread overview]
Message-ID: <20140210090911.GL17001@phenom.ffwll.local> (raw)
In-Reply-To: <1391800374-24904-3-git-send-email-damien.lespiau@intel.com>

On Fri, Feb 07, 2014 at 07:12:48PM +0000, Damien Lespiau wrote:
> Turns out it'd be nice to change some device information at run-time or simply
> have some code to fill in the info struct instead of having to declare the
> values in 30+ structures.
> 
> What prompted this change is handling fused out display/pipe and tweaking
> num_pipes at run-time, but I'm quite sure we'll find other flags/limits to
> stick into dev_priv->info.
> 
> Most of the changes were done with a sed:
> sed -i -e 's/dev_priv->info->/dev_priv->info./g' drivers/gpu/drm/i915/*[ch]
> 
> with a few tweaks to make it all work:
> - Change the field definition in struct drm_i915_private
> - adjust i915_dump_device_info()
> - adjust i915_driver_load()
> - adjust the INTEL_INFO() macro
> 
> v2: cast the info pointer returned by INTEL_INFO() to be const to catch
>     uses that would modify the structure post-initialization.
>     (Ville Syrjälä)
> 
> v3: Redo the patch onto latest drm-nightly,
>     Keep the info field const to catch post initialization writes
>     instead of the v2 solution,
>     Use a direct structure copy for the initial info initialization to
>     use the compiler type safety (Ville Syrjälä)
> 
> Reviewed-by: Mika Kuoppala <mika.kuoppala@intel.com> (for v2)
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com> (for v2)
> Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>

[snip]

> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> index 728b9c3..f66699f 100644
> --- a/drivers/gpu/drm/i915/i915_drv.h
> +++ b/drivers/gpu/drm/i915/i915_drv.h
> @@ -1390,7 +1390,7 @@ typedef struct drm_i915_private {
>  	struct drm_device *dev;
>  	struct kmem_cache *slab;
>  
> -	const struct intel_device_info *info;
> +	const struct intel_device_info info;

Since every access should now go through the macro I think it'd be good to
give this a __ prefix to make it clear that users better think twice
before using it. Maybe as a patch on top of all this?
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-02-10  9:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-07 19:12 Supporting fused display configurations v5 Damien Lespiau
2014-02-07 19:12 ` [PATCH 1/8] drm/i915: Always use INTEL_INFO() to access the device_info structure Damien Lespiau
2014-02-07 19:12 ` [PATCH 2/8] drm/i915: Make the intel_device_info structure kept in dev_priv writable Damien Lespiau
2014-02-10  9:09   ` Daniel Vetter [this message]
2014-02-10 12:49     ` Jani Nikula
2014-02-10 12:53     ` Ville Syrjälä
2014-02-10 14:06       ` Damien Lespiau
2014-02-10 14:17         ` Ville Syrjälä
2014-02-10 16:54           ` Daniel Vetter
2014-02-10 16:55       ` Daniel Vetter
2014-02-07 19:12 ` [PATCH 3/8] drm/i915: Move num_plane to the intel_device_info structure Damien Lespiau
2014-02-07 19:12 ` [PATCH 4/8] drm/i915: Consolidate FUSE_STRAP in one set of defines Damien Lespiau
2014-02-07 19:12 ` [PATCH 5/8] drm/i915: Disable display when fused off Damien Lespiau
2014-02-10  9:12   ` Daniel Vetter
2014-02-10 17:19     ` [PATCH 5/8 v5] " Damien Lespiau
2014-02-07 19:12 ` [PATCH 6/8] drm/i915: Use I915_MAX_PIPES in the pipe/plane_to_crtc_mapping definitions Damien Lespiau
2014-02-07 19:12 ` [PATCH 7/8] drm/i915: Reorder i915_params fields to not create holes Damien Lespiau
2014-02-07 19:12 ` [PATCH 8/8] drm/i915: Provide a command line option to disable display Damien Lespiau
2014-02-10  9:13   ` Daniel Vetter
2014-02-10 17:20     ` [PATCH 8/8 v2] " Damien Lespiau
2014-02-10 18:24       ` 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=20140210090911.GL17001@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=damien.lespiau@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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