Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Packard <keithp@keithp.com>
To: intel-gfx@lists.freedesktop.org
Cc: Takashi Iwai <tiwai@suse.de>, hcb@chaoticmind.net
Subject: Re: [PATCH 1/2] drm/i915: Check VBIOS value for determining LVDS dual channel mode, too
Date: Fri, 16 Mar 2012 16:18:03 -0700	[thread overview]
Message-ID: <861uosdtjo.fsf@sumi.keithp.com> (raw)
In-Reply-To: <1331934073-24463-2-git-send-email-tiwai@suse.de>

<#part sign=pgpmime>
On Fri, 16 Mar 2012 22:41:12 +0100, Takashi Iwai <tiwai@suse.de> wrote:

> +/* read the initial LVDS register value for the given panel mode */
> +static unsigned int get_lvds_reg_val(const struct bdb_header *bdb,
> +				     const struct bdb_lvds_lfp_data_ptrs *ptrs,
> +				     int index,
> +				     struct drm_display_mode *mode)

To follow the style of intel_bios.c, I think it would make sense to have
the function:

static const struct lvds_dvo_timing *
get_lvds_fp_timing(const struct bdb_lvds_lfp_data *lvds_lfp_data,
        	   const struct bdb_lvds_lfp_data_ptrs *lvds_lfp_data_ptrs,
                   int index)

then use the results of this in parse_lfp_panel_data, instead of putting
the whole computation into this new function.

I'd also like to see this code only use the BDB value when the LVDS is
disabled at startup time; otherwise, we'll be changing the behavior for
all LVDS users, and as BIOS tables are notoriously unreliable, I fear
that we'll cause a lot more problems than we solve.

-- 
keith.packard@intel.com

  reply	other threads:[~2012-03-16 23:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 21:41 [PATCH 0/2 v4] drm/i915: LVDS channel mode fixes Takashi Iwai
2012-03-16 21:41 ` [PATCH 1/2] drm/i915: Check VBIOS value for determining LVDS dual channel mode, too Takashi Iwai
2012-03-16 23:18   ` Keith Packard [this message]
2012-03-17  7:59     ` Takashi Iwai
2012-03-17 19:01       ` Keith Packard
2012-03-18 20:28         ` Takashi Iwai
2012-03-16 21:41 ` [PATCH 2/2] drm/i915: Add lvds_channel module option Takashi Iwai
2012-03-17  1:51   ` Eugeni Dodonov
2012-03-17  8:00     ` Takashi Iwai
2012-03-19 14:21 ` [PATCH 0/2 v4] drm/i915: LVDS channel mode fixes Adam Jackson
  -- strict thread matches above, loose matches on Subject: below --
2012-03-19 11:07 [PATCH 0/2 v5] " Takashi Iwai
2012-03-19 11:07 ` [PATCH 1/2] drm/i915: Check VBIOS value for determining LVDS dual channel mode, too Takashi Iwai
2012-03-20 10:01   ` Daniel Vetter
2012-03-20 12:04     ` Takashi Iwai
2012-03-20 14:57       ` Keith Packard
2012-03-20 18:35         ` Rodrigo Vivi
2012-03-20 12:07 [PATCH 0/2 v6] drm/i915: LVDS channel mode fixes Takashi Iwai
2012-03-20 12:07 ` [PATCH 1/2] drm/i915: Check VBIOS value for determining LVDS dual channel mode, too Takashi Iwai
2012-03-21 22:31   ` Daniel Vetter
2012-03-22 20:57   ` Paulo Zanoni

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=861uosdtjo.fsf@sumi.keithp.com \
    --to=keithp@keithp.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