From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Use anonymous union/struct to save space taken by latency values
Date: Wed, 10 Sep 2014 20:33:28 +0300 [thread overview]
Message-ID: <20140910173328.GA4193@intel.com> (raw)
In-Reply-To: <1409921592-23754-2-git-send-email-damien.lespiau@intel.com>
On Fri, Sep 05, 2014 at 01:53:11PM +0100, Damien Lespiau wrote:
> Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Damien Lespiau <damien.lespiau@intel.com>
I think I'll punt on reviewing this for now. I need to go through
the other skl wm stuff first, and then I probaly need to stare at the
result a bit before I can think about unification.
> ---
> drivers/gpu/drm/i915/i915_drv.h | 38 +++++++++++++++++++++-----------------
> 1 file changed, 21 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> index 0baf7f3..8471d12 100644
> --- a/drivers/gpu/drm/i915/i915_drv.h
> +++ b/drivers/gpu/drm/i915/i915_drv.h
> @@ -1730,23 +1730,27 @@ struct drm_i915_private {
> struct vlv_s0ix_state vlv_s0ix_state;
>
> struct {
> - /*
> - * Raw watermark latency values:
> - * in 0.1us units for WM0,
> - * in 0.5us units for WM1+.
> - */
> - /* primary */
> - uint16_t pri_latency[5];
> - /* sprite */
> - uint16_t spr_latency[5];
> - /* cursor */
> - uint16_t cur_latency[5];
> - /*
> - * Raw watermark memory latency values
> - * for SKL for all 8 levels
> - * in 1us units.
> - */
> - uint16_t skl_latency[8];
> + union {
> + /*
> + * Raw watermark latency values:
> + * in 0.1us units for WM0,
> + * in 0.5us units for WM1+.
> + */
> + struct {
> + /* primary */
> + uint16_t pri_latency[5];
> + /* sprite */
> + uint16_t spr_latency[5];
> + /* cursor */
> + uint16_t cur_latency[5];
> + };
> +
> + /*
> + * Raw watermark memory latency values for SKL for all
> + * 8 levels. In 1us units.
> + */
> + uint16_t skl_latency[8];
> + };
>
> /*
> * The skl_wm_values structure is a bit too big for stack
> --
> 1.8.3.1
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-09-10 17:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 12:53 [PATCH 0/2] Couple of patches on top of the SKL latency retrieval Damien Lespiau
2014-09-05 12:53 ` [PATCH 1/2] drm/i915: Use anonymous union/struct to save space taken by latency values Damien Lespiau
2014-09-10 17:33 ` Ville Syrjälä [this message]
2014-09-05 12:53 ` [PATCH 2/2] drm/i915: Clear PCODE_DATA1 on SNB+ Damien Lespiau
2014-09-10 17:32 ` Ville Syrjälä
2014-11-04 19:00 ` [PATCH 0/2] Couple of patches on top of the SKL latency retrieval Rodrigo Vivi
2014-11-05 16:49 ` Damien Lespiau
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=20140910173328.GA4193@intel.com \
--to=ville.syrjala@linux.intel.com \
--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