From: Damien Lespiau <damien.lespiau@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Dump some DPLL fields in pipe config debug
Date: Wed, 13 May 2015 17:41:40 +0100 [thread overview]
Message-ID: <20150513164140.GD10669@strange.amr.corp.intel.com> (raw)
In-Reply-To: <1431532268-4363-1-git-send-email-tvrtko.ursulin@linux.intel.com>
On Wed, May 13, 2015 at 04:51:07PM +0100, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Tried to get the platform split right, please shout if I failed.
>
> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
So, previously, we used to dump the whole list of states, even when the
platform didn't care about all of them. I do like a platform-aware dump
of the state better and this looks right to me (surely we can break the
strings at a ','!).
You probably also want to add pipe_config->ddi_pll_sel on DDI platforms
as it encodes the actual PLL selection (at least) and maybe look at the
other DPLL-related states in there (I can give a r-b tag without those
:p)
A small typo below.
--
Damien
> ---
> drivers/gpu/drm/i915/intel_display.c | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 52f9cbc..b3ed8a0 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -11418,6 +11418,32 @@ static void intel_dump_pipe_config(struct intel_crtc *crtc,
> DRM_DEBUG_KMS("ips: %i\n", pipe_config->ips_enabled);
> DRM_DEBUG_KMS("double wide: %i\n", pipe_config->double_wide);
>
> + if (IS_BROXTON(dev)) {
> + DRM_DEBUG_KMS("dpll_hw_state: ebb0: 0x%x, pll0: 0x%x, pll1: 0x%x, pll2: 0x%x, pll3: 0x%x, pll6: 0x%x, pll8: 0x%x, pcsdw12: 0x%x\n",
> + pipe_config->dpll_hw_state.ebb0,
> + pipe_config->dpll_hw_state.pll0,
> + pipe_config->dpll_hw_state.pll1,
> + pipe_config->dpll_hw_state.pll2,
> + pipe_config->dpll_hw_state.pll3,
> + pipe_config->dpll_hw_state.pll6,
> + pipe_config->dpll_hw_state.pll8,
> + pipe_config->dpll_hw_state.pcsdw12);
> + } else if (IS_SKYLAKE(dev)) {
> + DRM_DEBUG_KMS("dpll_hw_state: ctrl1: 0x%x, cfgcr1: 0x%x, cfgcr2: 0x%x\n",
> + pipe_config->dpll_hw_state.ctrl1,
> + pipe_config->dpll_hw_state.cfgcr1,
> + pipe_config->dpll_hw_state.cfgcr2);
> + } else if (HAS_DDI(dev)) {
> + DRM_DEBUG_KMS("dpll_hw_state: wrpll: 0x%x\n",
> + pipe_config->dpll_hw_state.wrpll);
> + } else {
> + DRM_DEBUG_KMS("dpll_hw_state: dpll: 0x%x, dpll_md: 0x%x, fp0: 0x%x, dp1: 0x%x\n",
fp1
> + pipe_config->dpll_hw_state.dpll,
> + pipe_config->dpll_hw_state.dpll_md,
> + pipe_config->dpll_hw_state.fp0,
> + pipe_config->dpll_hw_state.fp1);
> + }
> +
> DRM_DEBUG_KMS("planes on this crtc\n");
> list_for_each_entry(plane, &dev->mode_config.plane_list, head) {
> intel_plane = to_intel_plane(plane);
> --
> 2.4.0
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
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-13 16:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 15:51 [PATCH 1/2] drm/i915: Dump some DPLL fields in pipe config debug Tvrtko Ursulin
2015-05-13 15:51 ` [PATCH 2/2] drm/i915: Output scaler related pipe config debug in a single line Tvrtko Ursulin
2015-05-13 16:26 ` Damien Lespiau
2015-05-15 13:48 ` shuang.he
2015-05-18 5:27 ` Konduru, Chandra
2015-05-18 7:58 ` Daniel Vetter
2015-05-13 16:41 ` Damien Lespiau [this message]
2015-05-18 7:57 ` [PATCH 1/2] drm/i915: Dump some DPLL fields in pipe config debug Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2015-05-14 12:38 Tvrtko Ursulin
2015-05-14 12:58 ` Damien Lespiau
2015-05-18 8:06 ` Daniel Vetter
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=20150513164140.GD10669@strange.amr.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@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