From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/7] drm/i915/skl: Print the DMC firmware status in debugfs
Date: Thu, 22 Oct 2015 16:47:11 +0300 [thread overview]
Message-ID: <20151022134711.GQ26517@intel.com> (raw)
In-Reply-To: <1445442112-22027-1-git-send-email-mika.kuoppala@intel.com>
On Wed, Oct 21, 2015 at 06:41:46PM +0300, Mika Kuoppala wrote:
> From: Damien Lespiau <damien.lespiau@intel.com>
>
> Create a new debufs file for it, we'll have a few more things to add
> there.
>
> v2: Fix checkpatch warning about static const array
>
> Signed-off-by: Damien Lespiau <damien.lespiau@intel.com> (v1)
> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
> ---
> drivers/gpu/drm/i915/i915_debugfs.c | 22 ++++++++++++++++++++++
> 1 file changed, 22 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c
> index a3b22bd..ceae425 100644
> --- a/drivers/gpu/drm/i915/i915_debugfs.c
> +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> @@ -2777,6 +2777,27 @@ static int i915_power_domain_info(struct seq_file *m, void *unused)
> return 0;
> }
>
> +static int i915_dmc_info(struct seq_file *m, void *unused)
> +{
> + struct drm_info_node *node = m->private;
> + struct drm_device *dev = node->minor->dev;
> + struct drm_i915_private *dev_priv = dev->dev_private;
> + enum csr_state csr_state;
> + static const char * const csr_state_str[] = {
> + "unknown", "loaded", "error"
> + };
I'd use named initializers here. With that
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> +
> + if (!HAS_CSR(dev)) {
> + seq_puts(m, "not supported\n");
> + return 0;
> + }
> +
> + csr_state = intel_csr_load_status_get(dev_priv);
A side note: intel_csr_load_status_get() seems pretty useless. The lock
is protecting a single variable read.
> + seq_printf(m, "status: %s\n", csr_state_str[csr_state]);
> +
> + return 0;
> +}
> +
> static void intel_seq_print_mode(struct seq_file *m, int tabs,
> struct drm_display_mode *mode)
> {
> @@ -5236,6 +5257,7 @@ static const struct drm_info_list i915_debugfs_list[] = {
> {"i915_energy_uJ", i915_energy_uJ, 0},
> {"i915_runtime_pm_status", i915_runtime_pm_status, 0},
> {"i915_power_domain_info", i915_power_domain_info, 0},
> + {"i915_dmc_info", i915_dmc_info, 0},
> {"i915_display_info", i915_display_info, 0},
> {"i915_semaphore_status", i915_semaphore_status, 0},
> {"i915_shared_dplls_info", i915_shared_dplls_info, 0},
> --
> 2.1.4
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-10-22 13:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 15:41 [PATCH 1/7] drm/i915/skl: Print the DMC firmware status in debugfs Mika Kuoppala
2015-10-21 15:41 ` [PATCH 2/7] drm/i915/skl: Store and print the DMC firmware version we load Mika Kuoppala
2015-10-21 15:41 ` [PATCH 3/7] drm/i915/skl: Refuse to load outdated dmc firmware Mika Kuoppala
2015-10-21 15:46 ` Chris Wilson
2015-10-22 13:31 ` Mika Kuoppala
2015-10-22 13:48 ` Chris Wilson
2015-10-22 13:56 ` Chris Wilson
2015-10-21 15:41 ` [PATCH 4/7] drm/i915/skl: Expose DC5/DC6 entry counts Mika Kuoppala
2015-10-21 15:58 ` Rodrigo Vivi
2015-10-21 15:41 ` [PATCH 5/7] drm/i915/bxt: Expose DC5 entry count Mika Kuoppala
2015-10-21 15:41 ` [PATCH 6/7] drm/i915: Add dmc firmware load state and version to error state Mika Kuoppala
2015-10-21 15:47 ` Chris Wilson
2015-10-22 13:32 ` Mika Kuoppala
2015-10-22 13:44 ` Chris Wilson
2015-10-21 15:41 ` [PATCH 7/7] drm/i915: Add csr programming registers to dmc debugfs entry Mika Kuoppala
2015-10-21 15:53 ` Ville Syrjälä
2015-10-22 13:32 ` Mika Kuoppala
2015-10-22 13:47 ` Ville Syrjälä [this message]
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=20151022134711.GQ26517@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@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