From: Daniel Vetter <daniel@ffwll.ch>
To: Mika Kahola <mika.kahola@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: CD clock frequency to debugfs
Date: Mon, 4 May 2015 16:18:17 +0200 [thread overview]
Message-ID: <20150504141817.GH30184@phenom.ffwll.local> (raw)
In-Reply-To: <1429862770-4242-2-git-send-email-mika.kahola@intel.com>
On Fri, Apr 24, 2015 at 11:06:10AM +0300, Mika Kahola wrote:
> This patch adds information on current CD clock
> frequency to debugfs i915_frequency_info
>
> Signed-off-by: Mika Kahola <mika.kahola@intel.com>
> ---
> drivers/gpu/drm/i915/i915_debugfs.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> index 9c2b9e4..18c7531 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -1266,6 +1266,9 @@ static int i915_frequency_info(struct seq_file *m, void *unused)
> seq_puts(m, "no P-state info available\n");
> }
>
> + seq_printf(m, "CD clock freq: %dkHz\n",
> + dev_priv->display.get_display_clock_speed(dev));
Shouldn't we also dump the computed/requested cdclk in
dev_priv->cdclk_freq while at it? Seems useful enough otherwise.
-Daniel
> +
> out:
> intel_runtime_pm_put(dev_priv);
> return ret;
> --
> 1.9.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
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
next prev parent reply other threads:[~2015-05-04 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 8:06 [PATCH] drm/i915: CD clock frequency to debugfs Mika Kahola
2015-04-24 8:06 ` Mika Kahola
2015-04-24 11:07 ` shuang.he
2015-05-04 14:18 ` Daniel Vetter [this message]
2015-05-05 10:37 ` Mika Kahola
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=20150504141817.GH30184@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kahola@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