From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 3/4] drm/i915: Stop printing pipe name as hex
Date: Thu, 23 Nov 2023 07:16:32 +0000 [thread overview]
Message-ID: <3c10f571ecf7db386ee83220596b800c956454fc.camel@intel.com> (raw)
In-Reply-To: <20231122093137.1509-3-ville.syrjala@linux.intel.com>
On Wed, 2023-11-22 at 11:31 +0200, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Print the pipe name in ascii rather than hex.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Jouni Högander <jouni.hogander@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_dpll_mgr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_dpll_mgr.c
> b/drivers/gpu/drm/i915/display/intel_dpll_mgr.c
> index 7958d0bd851e..ef57dad1a9cb 100644
> --- a/drivers/gpu/drm/i915/display/intel_dpll_mgr.c
> +++ b/drivers/gpu/drm/i915/display/intel_dpll_mgr.c
> @@ -4537,7 +4537,7 @@ void intel_shared_dpll_state_verify(struct
> intel_atomic_state *state,
> "pll active mismatch (didn't expect
> pipe %c in active mask (0x%x))\n",
> pipe_name(crtc->pipe), pll-
> >active_mask);
> I915_STATE_WARN(i915, pll->state.pipe_mask &
> pipe_mask,
> - "pll enabled crtcs mismatch (found %x
> in enabled mask (0x%x))\n",
> + "pll enabled crtcs mismatch (found
> pipe %c in enabled mask (0x%x))\n",
> pipe_name(crtc->pipe), pll-
> >state.pipe_mask);
> }
> }
next prev parent reply other threads:[~2023-11-23 7:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 9:31 [Intel-gfx] [PATCH 1/4] drm/i915/psr: Don't send a NULL VSC SDP Ville Syrjala
2023-11-22 9:31 ` [Intel-gfx] [PATCH 2/4] drm/i915/psr: Include some basic PSR information in the state dump Ville Syrjala
2023-11-23 7:15 ` Hogander, Jouni
2023-11-22 9:31 ` [Intel-gfx] [PATCH 3/4] drm/i915: Stop printing pipe name as hex Ville Syrjala
2023-11-23 7:16 ` Hogander, Jouni [this message]
2023-11-22 9:31 ` [Intel-gfx] [PATCH 4/4] drm/i915: Move the SDP split debug spew to the correct place Ville Syrjala
2023-11-23 7:18 ` Hogander, Jouni
2023-11-23 0:43 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [1/4] drm/i915/psr: Don't send a NULL VSC SDP Patchwork
2023-11-23 0:57 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-11-23 7:14 ` [Intel-gfx] [PATCH 1/4] " Hogander, Jouni
2023-11-24 8:32 ` Ville Syrjälä
2023-11-24 0:35 ` [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/4] " 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=3c10f571ecf7db386ee83220596b800c956454fc.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@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