public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Mika Kahola <mika.kahola@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/i915/cnl: Dump the right pll registers when dumping pipe config.
Date: Thu, 10 Aug 2017 14:44:21 +0300	[thread overview]
Message-ID: <1502365461.16922.84.camel@intel.com> (raw)
In-Reply-To: <1499374475-1305-2-git-send-email-rodrigo.vivi@intel.com>

On Thu, 2017-07-06 at 13:54 -0700, Rodrigo Vivi wrote:
> Different from SKL we don't need ctrl1 and cfgcr2, but
> we need to dump cfgcr0 amd cfgcr1 instead.

With minor typo fixed in commit message, this is

Reviewed-by: Mika Kahola <mika.kahola@intel.com>

> 
> v2: rebase and commit message
> 
> Cc: Clint Taylor <clinton.a.taylor@intel.com>
> Cc: Mika Kahola <mika.kahola@intel.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_dpll_mgr.c | 11 ++++++++++-
>  1 file changed, 10 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_dpll_mgr.c
> b/drivers/gpu/drm/i915/intel_dpll_mgr.c
> index 2f7b0e6..a2a3d93 100644
> --- a/drivers/gpu/drm/i915/intel_dpll_mgr.c
> +++ b/drivers/gpu/drm/i915/intel_dpll_mgr.c
> @@ -2379,6 +2379,15 @@ static bool cnl_ddi_hdmi_pll_dividers(struct
> intel_crtc *crtc,
>  	return pll;
>  }
>  
> +static void cnl_dump_hw_state(struct drm_i915_private *dev_priv,
> +			      struct intel_dpll_hw_state *hw_state)
> +{
> +	DRM_DEBUG_KMS("dpll_hw_state: "
> +		      "cfgcr0: 0x%x, cfgcr1: 0x%x\n",
> +		      hw_state->cfgcr0,
> +		      hw_state->cfgcr1);
> +}
> +
>  static const struct intel_shared_dpll_funcs cnl_ddi_pll_funcs = {
>  	.enable = cnl_ddi_pll_enable,
>  	.disable = cnl_ddi_pll_disable,
> @@ -2395,7 +2404,7 @@ static bool cnl_ddi_hdmi_pll_dividers(struct
> intel_crtc *crtc,
>  static const struct intel_dpll_mgr cnl_pll_mgr = {
>  	.dpll_info = cnl_plls,
>  	.get_dpll = cnl_get_dpll,
> -	.dump_hw_state = skl_dump_hw_state,
> +	.dump_hw_state = cnl_dump_hw_state,
>  };
>  
>  /**
-- 
Mika Kahola - Intel OTC

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-08-10 11:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 20:54 [PATCH 1/3] drm/i915/cnl: Add allowed DP rates for Cannonlake Rodrigo Vivi
2017-07-06 20:54 ` [PATCH 2/3] drm/i915/cnl: Dump the right pll registers when dumping pipe config Rodrigo Vivi
2017-08-10 11:44   ` Mika Kahola [this message]
2017-07-06 20:54 ` [PATCH 3/3] drm/i915/cnl: Avoid old DDI translation functions on Cannonlake Rodrigo Vivi
2017-08-17 12:59   ` Mika Kahola
2017-08-17 18:50     ` Vivi, Rodrigo
2017-07-06 22:34 ` ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915/cnl: Add allowed DP rates for Cannonlake Patchwork
2017-08-09 20:00 ` [PATCH 1/3] " Rodrigo Vivi
2017-08-10  9:55 ` Mika Kahola
2017-08-10 22:40   ` [PATCH] " Rodrigo Vivi
2017-08-11  0:19     ` Manasi Navare
2017-08-11 18:44       ` Rodrigo Vivi
2017-08-11  8:47 ` ✓ Fi.CI.BAT: success for series starting with drm/i915/cnl: Add allowed DP rates for Cannonlake. (rev2) Patchwork

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=1502365461.16922.84.camel@intel.com \
    --to=mika.kahola@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@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