From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: "Florent Flament" <contact@florentflament.com>,
"Pavel Petrovic" <ppetrovic@acm.org>,
intel-gfx@lists.freedesktop.org,
"Sérgio M . Basto" <sergio@serjux.com>
Subject: Re: [PATCH v2] drm/i915: Fix drm:intel_enable_lvds ERROR message in kernel log
Date: Fri, 4 May 2018 22:33:40 +0300 [thread overview]
Message-ID: <20180504193339.GB23723@intel.com> (raw)
In-Reply-To: <87in8mdv0n.fsf@intel.com>
On Fri, Apr 20, 2018 at 01:36:40PM +0300, Jani Nikula wrote:
> On Thu, 19 Apr 2018, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> > From: Florent Flament <contact@florentflament.com>
> >
> > Fix `[drm:intel_enable_lvds] *ERROR* timed out waiting for panel to
> > power on` in kernel log at boot time.
> >
> > Toshiba Satellite Z930 laptops needs between 1 and 2 seconds to power
> > on its screen during Intel i915 DRM initialization. This currently
> > results in a `[drm:intel_enable_lvds] *ERROR* timed out waiting for
> > panel to power on` message appearing in the kernel log during boot
> > time and when stopping the machine.
> >
> > This change increases the timeout of the `intel_enable_lvds` function
> > from 1 to 2 seconds, letting enough time for the Satellite 930 LCD
> > screen to power on, and suppressing the error message from the kernel
> > log.
>
> Please update the commit message to match what the patch actually does
> now, instead of hiding it in braces below. With that (and can be done
> while pushing),
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Pushed to dinq with a slightly amended commit message. Also added
cc:stable.
Thanks for the original patch, and review.
>
>
> >
> > This patch has been successfully tested on Linux 4.14 running on a
> > Toshiba Satellite Z930.
> >
> > Signed-off-by: Florent Flament <contact@florentflament.com>
> > [vsyrjala: bump the timeout from 2 to 5 seconds to match the DP
> > code and properly cover the max hw timeout of ~4 seconds, and
> > drop the comment about the specific machine since this is not
> > a particulary surprising issue, nor specific to that one machine]
> > Cc: Pavel Petrovic <ppetrovic@acm.org>
> > Cc: Sérgio M. Basto <sergio@serjux.com>
> > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=103414
> > References: https://bugzilla.kernel.org/show_bug.cgi?id=57591
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_lvds.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_lvds.c b/drivers/gpu/drm/i915/intel_lvds.c
> > index d35d2d50f595..8691c86f579c 100644
> > --- a/drivers/gpu/drm/i915/intel_lvds.c
> > +++ b/drivers/gpu/drm/i915/intel_lvds.c
> > @@ -326,7 +326,8 @@ static void intel_enable_lvds(struct intel_encoder *encoder,
> >
> > I915_WRITE(PP_CONTROL(0), I915_READ(PP_CONTROL(0)) | PANEL_POWER_ON);
> > POSTING_READ(lvds_encoder->reg);
> > - if (intel_wait_for_register(dev_priv, PP_STATUS(0), PP_ON, PP_ON, 1000))
> > +
> > + if (intel_wait_for_register(dev_priv, PP_STATUS(0), PP_ON, PP_ON, 5000))
> > DRM_ERROR("timed out waiting for panel to power on\n");
> >
> > intel_panel_enable_backlight(pipe_config, conn_state);
>
> --
> Jani Nikula, Intel Open Source Technology Center
--
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-05-04 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 22:28 [PATCH] drm/i915: Fix drm:intel_enable_lvds ERROR message in kernel log Florent Flament
2017-11-21 0:23 ` ✗ Fi.CI.BAT: warning for " Patchwork
2018-04-19 16:07 ` [PATCH v2] " Ville Syrjala
2018-04-20 10:36 ` Jani Nikula
2018-05-04 19:33 ` Ville Syrjälä [this message]
2018-04-19 16:45 ` ✓ Fi.CI.BAT: success for drm/i915: Fix drm:intel_enable_lvds ERROR message in kernel log (rev2) Patchwork
2018-04-19 23:44 ` ✓ 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=20180504193339.GB23723@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=contact@florentflament.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=ppetrovic@acm.org \
--cc=sergio@serjux.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