From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Hans de Goede <jwrdegoede@fedoraproject.org>,
intel-gfx@lists.freedesktop.org,
Basil Eric Rabi <ericbasil.rabi@gmail.com>,
Tolga Cakir <cevelnet@gmail.com>
Subject: Re: [PATCH] drm/i915/backlight: Fix backlight takeover on LPT
Date: Tue, 20 Nov 2018 20:51:21 +0200 [thread overview]
Message-ID: <20181120185121.GV9144@intel.com> (raw)
In-Reply-To: <20181120103926.10117-1-maarten.lankhorst@linux.intel.com>
On Tue, Nov 20, 2018 at 11:39:26AM +0100, Maarten Lankhorst wrote:
> On lynxpoint the bios sometimes sets up the backlight using the CPU
> display, but the driver expects using the PWM PCH override register.
>
> Read the value from the CPU register, then convert it to the other
> units by converting from the old duty cycle, to freq, to the new units.
>
> This value is then programmed in the override register, after which
> we set the override and disable the CPU display control. This allows
> us to switch the source without flickering, and make the backlight
> controls work in the driver.
>
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108225
> Cc: Basil Eric Rabi <ericbasil.rabi@gmail.com>
> Cc: Hans de Goede <jwrdegoede@fedoraproject.org>
> Cc: Tolga Cakir <cevelnet@gmail.com>
> Tested-by: Tolga Cakir <cevelnet@gmail.com>
> ---
> drivers/gpu/drm/i915/intel_panel.c | 34 +++++++++++++++++++++++++++---
> 1 file changed, 31 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_panel.c b/drivers/gpu/drm/i915/intel_panel.c
> index e6cd7b55c018..3357232f1b0e 100644
> --- a/drivers/gpu/drm/i915/intel_panel.c
> +++ b/drivers/gpu/drm/i915/intel_panel.c
> @@ -1485,7 +1485,7 @@ static int lpt_setup_backlight(struct intel_connector *connector, enum pipe unus
> struct drm_i915_private *dev_priv = to_i915(connector->base.dev);
> struct intel_panel *panel = &connector->panel;
> u32 pch_ctl1, pch_ctl2, val;
> - bool alt;
> + bool alt, cpu_mode = false;
>
> if (HAS_PCH_LPT(dev_priv))
> alt = I915_READ(SOUTH_CHICKEN2) & LPT_PWM_GRANULARITY;
> @@ -1507,12 +1507,40 @@ static int lpt_setup_backlight(struct intel_connector *connector, enum pipe unus
>
> panel->backlight.min = get_backlight_min_vbt(connector);
>
> - val = lpt_get_backlight(connector);
> + panel->backlight.enabled = pch_ctl1 & BLM_PCH_PWM_ENABLE;
> + if (panel->backlight.enabled && HAS_PCH_LPT(dev_priv) &&
> + (I915_READ(BLC_PWM_CPU_CTL2) & BLM_PWM_ENABLE) &&
> + !WARN_ON(pch_ctl1 & BLM_PCH_OVERRIDE_ENABLE)) {
> + u32 freq;
> +
> + cpu_mode = true;
> + /*
> + * We're in cpu mode, convert to PCH units.
> + *
> + * Convert CPU pwm tick back to hz, back to new PCH units again.
> + * this is the same formula as pch_hz_to_pwm, but the other way
> + * around..
> + */
> + val = pch_get_backlight(connector);
> + freq = DIV_ROUND_CLOSEST(KHz(dev_priv->rawclk_freq), val * 128);
The docs are telling me that HSW/BDW use cdclk for the CPU backlight,
and the increment is configurable as well.
Also what about S4 resume? Don't we need this trick there as well?
> +
> + val = lpt_hz_to_pwm(connector, freq);
> + } else
> + val = lpt_get_backlight(connector);
> val = intel_panel_compute_brightness(connector, val);
> panel->backlight.level = clamp(val, panel->backlight.min,
> panel->backlight.max);
>
> - panel->backlight.enabled = pch_ctl1 & BLM_PCH_PWM_ENABLE;
> + if (cpu_mode) {
> + u32 tmp;
> +
> + /* Use PWM mode, instead of cpu clock */
> + lpt_set_backlight(connector->base.state, panel->backlight.level);
> + I915_WRITE(BLC_PWM_PCH_CTL1, pch_ctl1 | BLM_PCH_OVERRIDE_ENABLE);
> +
> + tmp = I915_READ(BLC_PWM_CPU_CTL2);
> + I915_WRITE(BLC_PWM_CPU_CTL2, tmp & ~BLM_PWM_ENABLE);
> + }
>
> return 0;
> }
> --
> 2.19.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-11-20 18:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 10:39 [PATCH] drm/i915/backlight: Fix backlight takeover on LPT Maarten Lankhorst
2018-11-20 11:04 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-11-20 11:04 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-11-20 11:34 ` ✓ Fi.CI.BAT: success " Patchwork
2018-11-20 14:49 ` ✓ Fi.CI.IGT: " Patchwork
2018-11-20 18:51 ` Ville Syrjälä [this message]
2018-11-21 7:16 ` [PATCH] " Tolga Cakir
2018-11-21 10:45 ` Ville Syrjälä
2018-11-21 12:37 ` Tolga Cakir
2018-11-23 12:33 ` Jani Nikula
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=20181120185121.GV9144@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=cevelnet@gmail.com \
--cc=ericbasil.rabi@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jwrdegoede@fedoraproject.org \
--cc=maarten.lankhorst@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.