From: Daniel Vetter <daniel@ffwll.ch>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Eliminate lots of WARNs when there's no backlight present
Date: Fri, 17 Jan 2014 14:32:00 +0100 [thread overview]
Message-ID: <20140117133200.GG4770@phenom.ffwll.local> (raw)
In-Reply-To: <87zjmu7slo.fsf@intel.com>
On Fri, Jan 17, 2014 at 01:30:59PM +0200, Jani Nikula wrote:
> On Thu, 16 Jan 2014, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > My 855gm doesn't register the intel backlight but it still ends up
> > calling the backlight code to enable/disable the backlight via the
> > LVDS code. This leads to some WARNs due to backlight.max being 0.
> >
> > Let's have intel_panel_enable_backlight() and intel_panel_disable_backlight()
> > check whether there's a backlight present or not.
> >
> > Also move the backlight.present check from asle_set_backlight() into
> > intel_panel_set_backlight() for some extra symmetry.
>
> I have an identical patch in my local repo dated Dec 13... should've
> sent it out weeks ago. Damn.
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Queued for -next, thanks for the patch.
-Daniel
>
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_opregion.c | 10 ++--------
> > drivers/gpu/drm/i915/intel_panel.c | 6 +++---
> > 2 files changed, 5 insertions(+), 11 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_opregion.c b/drivers/gpu/drm/i915/intel_opregion.c
> > index 3da259e..37e9a96 100644
> > --- a/drivers/gpu/drm/i915/intel_opregion.c
> > +++ b/drivers/gpu/drm/i915/intel_opregion.c
> > @@ -396,9 +396,7 @@ int intel_opregion_notify_adapter(struct drm_device *dev, pci_power_t state)
> > static u32 asle_set_backlight(struct drm_device *dev, u32 bclp)
> > {
> > struct drm_i915_private *dev_priv = dev->dev_private;
> > - struct drm_connector *connector;
> > struct intel_connector *intel_connector;
> > - struct intel_panel *panel;
> > struct opregion_asle __iomem *asle = dev_priv->opregion.asle;
> >
> > DRM_DEBUG_DRIVER("bclp = 0x%08x\n", bclp);
> > @@ -417,12 +415,8 @@ static u32 asle_set_backlight(struct drm_device *dev, u32 bclp)
> > * only one).
> > */
> > DRM_DEBUG_KMS("updating opregion backlight %d/255\n", bclp);
> > - list_for_each_entry(connector, &dev->mode_config.connector_list, head) {
> > - intel_connector = to_intel_connector(connector);
> > - panel = &intel_connector->panel;
> > - if (panel->backlight.present)
> > - intel_panel_set_backlight(intel_connector, bclp, 255);
> > - }
> > + list_for_each_entry(intel_connector, &dev->mode_config.connector_list, base.head)
> > + intel_panel_set_backlight(intel_connector, bclp, 255);
> > iowrite32(DIV_ROUND_UP(bclp * 100, 255) | ASLE_CBLV_VALID, &asle->cblv);
> >
> > mutex_unlock(&dev->mode_config.mutex);
> > diff --git a/drivers/gpu/drm/i915/intel_panel.c b/drivers/gpu/drm/i915/intel_panel.c
> > index 20ebc3e..350de35 100644
> > --- a/drivers/gpu/drm/i915/intel_panel.c
> > +++ b/drivers/gpu/drm/i915/intel_panel.c
> > @@ -502,7 +502,7 @@ void intel_panel_set_backlight(struct intel_connector *connector, u32 level,
> > u32 freq;
> > unsigned long flags;
> >
> > - if (pipe == INVALID_PIPE)
> > + if (!panel->backlight.present || pipe == INVALID_PIPE)
> > return;
> >
> > spin_lock_irqsave(&dev_priv->backlight_lock, flags);
> > @@ -579,7 +579,7 @@ void intel_panel_disable_backlight(struct intel_connector *connector)
> > enum pipe pipe = intel_get_pipe_from_connector(connector);
> > unsigned long flags;
> >
> > - if (pipe == INVALID_PIPE)
> > + if (!panel->backlight.present || pipe == INVALID_PIPE)
> > return;
> >
> > /*
> > @@ -782,7 +782,7 @@ void intel_panel_enable_backlight(struct intel_connector *connector)
> > enum pipe pipe = intel_get_pipe_from_connector(connector);
> > unsigned long flags;
> >
> > - if (pipe == INVALID_PIPE)
> > + if (!panel->backlight.present || pipe == INVALID_PIPE)
> > return;
> >
> > DRM_DEBUG_KMS("pipe %c\n", pipe_name(pipe));
> > --
> > 1.8.3.2
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> --
> Jani Nikula, Intel Open Source Technology Center
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2014-01-17 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 16:27 [PATCH] drm/i915: Eliminate lots of WARNs when there's no backlight present ville.syrjala
2014-01-16 16:55 ` Daniel Vetter
2014-01-16 17:09 ` Ville Syrjälä
2014-01-17 11:30 ` Jani Nikula
2014-01-17 13:32 ` Daniel Vetter [this message]
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=20140117133200.GG4770@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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