Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/i915: Make backlight setup debugs consistent
Date: Wed, 15 Feb 2023 12:14:59 +0200	[thread overview]
Message-ID: <873577s09o.fsf@intel.com> (raw)
In-Reply-To: <20230214134739.25077-1-ville.syrjala@linux.intel.com>

On Tue, 14 Feb 2023, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> It's confusing to debug backlight issues when one can't
> easily even tell what kind of backlight control was
> selected. Sprinkle uniform debug messages to all the
> backlight setup functions.
>
> Also the one that was already there (ext_pwm) was
> using drm_info() for some reason. I don't think that's
> warranted so switch it to drm_dbg_kms() as well.

Maybe add similar in intel_dp_aux_backlight.c to the two setup functions
there? Also the message in intel_backlight_setup() could use some
tweaking.

> @@ -1392,6 +1408,10 @@ static int vlv_setup_backlight(struct intel_connector *connector, enum pipe pipe
>  
>  	panel->backlight.pwm_enabled = ctl2 & BLM_PWM_ENABLE;
>  
> +	drm_dbg_kms(&i915->drm,
> +		    "[CONNECTOR:%d:%s] Using native PWM for backlight control\n",
> +		    connector->base.base.id, connector->base.name);

Maybe log the pipe here similar to controller in bxt/cnp?

Otherwise, LGTM.


BR,
Jani.


-- 
Jani Nikula, Intel Open Source Graphics Center

  parent reply	other threads:[~2023-02-15 10:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 13:47 [Intel-gfx] [PATCH 1/3] drm/i915: Make backlight setup debugs consistent Ville Syrjala
2023-02-14 13:47 ` [Intel-gfx] [PATCH 2/3] drm/i915: Don't hide function calls with side effects Ville Syrjala
2023-02-15 10:15   ` Jani Nikula
2023-02-14 13:47 ` [Intel-gfx] [PATCH 3/3] drm/i915: Clean up g4x+ sprite TILEOFF programming Ville Syrjala
2023-02-15 10:16   ` Jani Nikula
2023-02-14 16:25 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/3] drm/i915: Make backlight setup debugs consistent Patchwork
2023-02-15  3:28 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-02-15 10:14 ` Jani Nikula [this message]
2023-02-15 10:41   ` [Intel-gfx] [PATCH 1/3] " Ville Syrjälä
2023-02-15 13:56 ` [Intel-gfx] [PATCH v2 " Ville Syrjala
2023-02-15 14:11   ` Jani Nikula
2023-02-15 14:58 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v2,1/3] drm/i915: Make backlight setup debugs consistent (rev2) Patchwork
2023-02-16  6:54 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=873577s09o.fsf@intel.com \
    --to=jani.nikula@linux.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