From: Takashi Iwai <tiwai@suse.de>
To: Adam Jackson <ajax@redhat.com>
Cc: intel-gfx@lists.freedesktop.org, hcb@chaoticmind.net
Subject: Re: Thinkpad T420 and single/dual channel lvds
Date: Fri, 16 Mar 2012 21:29:24 +0100 [thread overview]
Message-ID: <s5hehssi923.wl%tiwai@suse.de> (raw)
In-Reply-To: <4F639AC8.907@redhat.com>
At Fri, 16 Mar 2012 15:55:52 -0400,
Adam Jackson wrote:
>
> On 3/15/12 10:42 AM, Takashi Iwai wrote:
>
> > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> > index f851db7..314af26 100644
> > --- a/drivers/gpu/drm/i915/intel_display.c
> > +++ b/drivers/gpu/drm/i915/intel_display.c
> > @@ -356,6 +356,23 @@ static const intel_limit_t intel_limits_ironlake_display_port = {
> > .find_pll = intel_find_pll_ironlake_dp,
> > };
> >
> > +static bool is_dual_link_lvds(struct drm_i915_private *dev_priv,
> > + unsigned int reg)
> > +{
> > + /* 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;
>
> Would slightly prefer if this was more like:
>
> if (dev_priv->bios_lvds_val)
> return !!(dev_priv->bios_lvds_val & LVDS_CLKB_POWER_MASK);
>
> Since that way it eliminates some useless register reads in the normal
> case even for single-link. Not going to insist on it though.
Sounds reasonable, yes.
Also, it'd be good to have a module option to override the lvds
channel setup, e.g. lvds_channel=0 for probing BIOS like this,
lvds_channel=1 and 2 are to set the single and dual-channel mode
forcibly, respectively. If you guys think it's worth, I'll write an
additional patch after fixing this as suggested.
> Looks really good otherwise, thanks!
>
> Reviewed-by: Adam Jackson <ajax@redhat.com>
Thanks!
Takashi
next prev parent reply other threads:[~2012-03-16 20:29 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
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 [this message]
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=s5hehssi923.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=ajax@redhat.com \
--cc=hcb@chaoticmind.net \
--cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox