All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org,
	Mandeep Baines <msb@chromium.org>,
	Olof Johansson <olofj@chromium.org>
Subject: Re: [PATCH] CHROMIUM: i915: Initialize panel timing registers if VBIOS did not.
Date: Thu, 7 Oct 2010 16:06:04 -0700	[thread overview]
Message-ID: <20101007160604.5f2b2f76@jbarnes-desktop> (raw)
In-Reply-To: <8u3s8d$jqd8sk@orsmga001.jf.intel.com>

On Thu, 07 Oct 2010 23:55:38 +0100
Chris Wilson <chris@chris-wilson.co.uk> wrote:

> On Thu, 7 Oct 2010 15:48:14 -0700, Bryan Freed <bfreed@chromium.org> wrote:
> > The time between start of the pixel clock and backlight enable is a basic
> > panel timing constraint.  If no VBIOS Table is found, and the Panel Power
> > On/Off registers are found to be 0, assume we are booting without VBIOS
> > initialization and set these registers to something reasonable.
> 
> IIRC, the panel sequence registers are meant to be stored in the VBIOS. So
> if we add the parsing of those to the driver and add the defaults to
> init_vbt_default() then we can check whether PP_ON_DELAYS is valid upon
> device init (module load and resume) and fixup in case the BIOS does not.

Right, those values should be in the VBT.  Getting them wrong can
actually damage your panel, so we need to take care here.  The whole
point of the power sequencing logic and register lock is to avoid such
damage.

That said, I've abused my panels (both LVDS and eDP) pretty hard and
have yet to damage one in any visible way, so stealing some
conservative (i.e. long) delays from an existing VBT will probably work
ok.

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2010-10-07 23:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTikoPjDs-RNs+nvOJUO5UWHedGjRT1Ee7kuDyVdO@mail.gmail.com>
2010-10-07 22:55 ` [PATCH] CHROMIUM: i915: Initialize panel timing registers if VBIOS did not Chris Wilson
2010-10-07 23:06   ` Jesse Barnes [this message]
2010-10-07 23:48   ` Bryan Freed
2010-10-07 23:52     ` Jesse Barnes

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=20101007160604.5f2b2f76@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=msb@chromium.org \
    --cc=olofj@chromium.org \
    /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.