From: Daniel Vetter <daniel@ffwll.ch>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH 3/3] drm/i915: add i915_ips_status debugfs entry
Date: Fri, 31 May 2013 21:42:03 +0200 [thread overview]
Message-ID: <20130531194203.GF15743@phenom.ffwll.local> (raw)
In-Reply-To: <1370028804-3074-3-git-send-email-przanoni@gmail.com>
On Fri, May 31, 2013 at 04:33:24PM -0300, Paulo Zanoni wrote:
> From: Paulo Zanoni <paulo.r.zanoni@intel.com>
>
> It just prints whether it's supported/enabled/disabled. Feature
> requested by the power management team.
>
> v2: Checkpatch started complaining about seq_printf with 1 argument.
>
> Requested-by: Kristen Accardi <kristen.c.accardi@intel.com>
> Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
All three merged into dinq, thanks.
-Daniel
> ---
> drivers/gpu/drm/i915/i915_debugfs.c | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> index 2eb572a..f5c6917 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -1434,6 +1434,25 @@ static int i915_fbc_status(struct seq_file *m, void *unused)
> return 0;
> }
>
> +static int i915_ips_status(struct seq_file *m, void *unused)
> +{
> + struct drm_info_node *node = (struct drm_info_node *) m->private;
> + struct drm_device *dev = node->minor->dev;
> + struct drm_i915_private *dev_priv = dev->dev_private;
> +
> + if (!IS_ULT(dev)) {
> + seq_puts(m, "not supported\n");
> + return 0;
> + }
> +
> + if (I915_READ(IPS_CTL) & IPS_ENABLE)
> + seq_puts(m, "enabled\n");
> + else
> + seq_puts(m, "disabled\n");
> +
> + return 0;
> +}
> +
> static int i915_sr_status(struct seq_file *m, void *unused)
> {
> struct drm_info_node *node = (struct drm_info_node *) m->private;
> @@ -2231,6 +2250,7 @@ static struct drm_info_list i915_debugfs_list[] = {
> {"i915_ring_freq_table", i915_ring_freq_table, 0},
> {"i915_gfxec", i915_gfxec, 0},
> {"i915_fbc_status", i915_fbc_status, 0},
> + {"i915_ips_status", i915_ips_status, 0},
> {"i915_sr_status", i915_sr_status, 0},
> {"i915_opregion", i915_opregion, 0},
> {"i915_gem_framebuffer", i915_gem_framebuffer_info, 0},
> --
> 1.8.1.2
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-05-31 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 19:33 [PATCH 1/3] drm/i915: implement IPS feature Paulo Zanoni
2013-05-31 19:33 ` [PATCH 2/3] drm/i915: add enable_ips module option Paulo Zanoni
2013-05-31 19:33 ` [PATCH 3/3] drm/i915: add i915_ips_status debugfs entry Paulo Zanoni
2013-05-31 19:42 ` Daniel Vetter [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-13 19:00 [PATCH 1/3] drm/i915: implement IPS feature Paulo Zanoni
2013-05-13 19:00 ` [PATCH 3/3] drm/i915: add i915_ips_status debugfs entry Paulo Zanoni
2013-05-14 17:59 ` Rodrigo Vivi
2013-05-14 17:59 ` Rodrigo Vivi
2013-05-31 16:08 ` Rodrigo Vivi
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=20130531194203.GF15743@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=przanoni@gmail.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