Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Takashi Iwai <tiwai@suse.de>, Adam Jackson <ajax@redhat.com>
Cc: intel-gfx@lists.freedesktop.org, hcb@chaoticmind.net
Subject: Re: Thinkpad T420 and single/dual channel lvds
Date: Thu, 15 Mar 2012 13:25:08 +0000	[thread overview]
Message-ID: <d08817$3homf2@azsmga001.ch.intel.com> (raw)
In-Reply-To: <s5hvcm6vwc5.wl%tiwai@suse.de>

On Thu, 15 Mar 2012 14:15:54 +0100, Takashi Iwai <tiwai@suse.de> wrote:
> +static bool is_dual_link_lvds(struct drm_i915_private *dev_priv)
> +{
> +	/* BIOS should set the proper LVDS register value at boot, but
> +	 * in reality, it doesn't set the value when the lid is closed;
> +	 * thus when a machine is booted with the lid closed, the LVDS
> +	 * reg value can't be trusted.  So we need to check "the value
> +	 * to be set" in VBT at first.
> +	 */
> +	if ((dev_priv->bios_lvds_val & LVDS_CLKB_POWER_MASK) ==
> +	    LVDS_CLKB_POWER_UP)
> +		return true;
> +	if ((I915_READ(PCH_LVDS) & LVDS_CLKB_POWER_MASK) ==

This is either PCH_LVDS or LVDS depending on the generation.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2012-03-15 13:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 12:37 Thinkpad T420 and single/dual channel lvds Helge Bahmann
2012-03-14 14:45 ` Adam Jackson
2012-03-14 16:44   ` Takashi Iwai
2012-03-14 18:09     ` Adam Jackson
2012-03-15 13:15       ` Takashi Iwai
2012-03-15 13:25         ` Chris Wilson [this message]
2012-03-15 13:30           ` Takashi Iwai
2012-03-15 14:42             ` Takashi Iwai
2012-03-16 15:33               ` Rodrigo Vivi
2012-03-16 19:55               ` Adam Jackson
2012-03-16 20:29                 ` Takashi Iwai
2012-03-18 17:50                   ` Daniel Vetter
2012-03-18 18:01                     ` Andreas Heider
2012-03-18 20:26                       ` Takashi Iwai
2012-03-18 20:24                     ` Takashi Iwai

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='d08817$3homf2@azsmga001.ch.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=ajax@redhat.com \
    --cc=hcb@chaoticmind.net \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tiwai@suse.de \
    /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