public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 5/5] drm/i915: Add SPLL sharing support for DDI
Date: Mon, 3 Mar 2014 11:56:08 +0200	[thread overview]
Message-ID: <20140303095608.GV3852@intel.com> (raw)
In-Reply-To: <CA+gsUGRCcRrmaE3OuePatcXp9aFHgRVzQ1Qf_s=ak+3b2+WRDA@mail.gmail.com>

On Fri, Feb 28, 2014 at 06:40:22PM -0300, Paulo Zanoni wrote:
> Hi
> 
> 2014-02-27 9:23 GMT-03:00  <ville.syrjala@linux.intel.com>:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > Write some theoretical SPLL sharing support for DDI. Currently that will
> > never happens since we never use SPLL for anything but FDI. But having
> > the code there makes it easier if we ever want to do it, and it might
> > excercise the PLL sharing code a bit more.
> 
> One thing is that if we ever want to use SSC on eDP/DP/HDMI, we will
> want to use either SPLL or WRPLL instead of LCPLL. I always wanted to
> implement this, and recently I saw a bug that made me think about it
> again.
> 
> So instead of this patch, why don't you write support to use SSC when
> requested? We could do this through some i915.use_ssc command line
> option that would just try to force SSC on everything, or maybe a
> "debug connector property", or debugfs, or anything you might want.
> With this, you would be able to actually test your patches, and we'd
> have a useful feature.
> 
> If you disagree, please just say "no" and then I'll go back to review
> this patch :)

I think improving the PLL selection code should be a separate patch.
IIRC I even said as much in the cover letter.

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2014-03-03  9:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 12:23 [PATCH 0/5] drm/i915: FDI port_clock fix for DDI and other FDI changes ville.syrjala
2014-02-27 12:23 ` [PATCH 1/5] drm/i915: Fix DDI port_clock for VGA output ville.syrjala
2014-02-28 22:09   ` Paulo Zanoni
2014-03-03 10:09     ` Ville Syrjälä
2014-02-27 12:23 ` [PATCH 2/5] drm/i915: Change intel_fdi_link_freq() to 10kHz ville.syrjala
2014-02-28 22:28   ` Paulo Zanoni
2014-03-01  7:34     ` Chris Wilson
2014-03-05 15:04       ` Daniel Vetter
2014-03-06 21:01         ` Daniel Vetter
2014-02-27 12:23 ` [PATCH 3/5] drm/i915: Use DIV_ROUND_UP() when calculating number of required FDI lanes ville.syrjala
2014-02-28 22:35   ` Paulo Zanoni
2014-02-27 12:23 ` [PATCH 4/5] drm/i915: Use port_clock for FDI frequency on DDI ville.syrjala
2014-02-27 12:23 ` [PATCH 5/5] drm/i915: Add SPLL sharing support for DDI ville.syrjala
2014-02-28 21:40   ` Paulo Zanoni
2014-03-03  9:56     ` Ville Syrjälä [this message]
2014-03-05 15:09       ` Daniel Vetter

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=20140303095608.GV3852@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=przanoni@gmail.com \
    /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