All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: bfreed@chromium.org, jbarnes@virtuousgeek.org,
	intel-gfx@lists.freedesktop.org
Cc: Mark Hayter <mdhayter@chromium.org>
Subject: Re: [PATCH] i915: Modify for pineview clock source
Date: Wed, 15 Dec 2010 14:52:35 +0000	[thread overview]
Message-ID: <b9dded$hctele@orsmga002.jf.intel.com> (raw)
In-Reply-To: <1292355630-17527-1-git-send-email-bfreed@chromium.org>

On Tue, 14 Dec 2010 11:40:30 -0800, bfreed@chromium.org wrote:
> The i915 driver normally assumes the video bios has configured several 
> of the LVDS panel registers, and it just inherits the values. If the 
> vbios has not run, several of these will need to be setup. 

I'm having problems applying these using git-am. Notably your base objects
are not in my tree.

I'm dubious about flipping the SSC bit just for PineView. On recent
platforms, I think using an SSC reference is prevalent.

Instead of hardcoding 100Mhz as the clock, I'd prefer to see those SSC
frequencies split out of the general definitions and shared with this
initialiser. Something like:
int intel_bios_ssc_frequency(struct drm_device *dev, bool high_speed)
{
   switch(INTEL_INFO(dev)->gen) {
   case 2: return high_speed ? 66 : 48;
   case 3:
   case 4: return high_speed ? 100 : 96;
   default: return high_speed ? 120 : 100;
   }
}
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2010-12-15 14:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-14 19:40 [PATCH] i915: Modify for pineview clock source bfreed
2010-12-15 14:52 ` Chris Wilson [this message]
     [not found]   ` <AANLkTimun2KkCAu0-L1zZ2qNLx1wr56+RWoodoHB=yVo@mail.gmail.com>
2010-12-16  5:11     ` Mark Hayter
2010-12-16  5:59       ` Dave Airlie

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='b9dded$hctele@orsmga002.jf.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=bfreed@chromium.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=mdhayter@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.