public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Clint Taylor <clinton.a.taylor@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/hdmi: Compute port_clock for 27.027 pixel replicated modes
Date: Fri, 26 Sep 2014 09:40:55 -0700	[thread overview]
Message-ID: <54259717.8070904@intel.com> (raw)
In-Reply-To: <20140926155838.GA32511@intel.com>

On 09/26/2014 08:58 AM, Ville Syrjälä wrote:
> On Wed, Sep 24, 2014 at 03:49:39PM -0700, clinton.a.taylor@intel.com wrote:
>> From: Clint Taylor <clinton.a.taylor@intel.com>
>>
>> port_clock was being incorrectly computed and WRPLL was incorrectly
>> programmed for pixel doubled modes using a 27.027MHz pixel clock.
>> port_clock was set to 27.026 resulting in an output pixel clock
>> matching 27.000MHz.
>
> I don't understand how this 27.000MHz clock would come about. Can you
> explain further?
>
>> Since there is no way to correctly half the 27.027
>> frequency as an integer just set port_clock to 27027 for these modes.
>>
>> Signed-off-by: Clint Taylor <clinton.a.taylor@intel.com>
>> ---
>>   drivers/gpu/drm/i915/intel_hdmi.c |    5 +++++
>>   1 file changed, 5 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_hdmi.c b/drivers/gpu/drm/i915/intel_hdmi.c
>> index 29ec153..a0786d6 100644
>> --- a/drivers/gpu/drm/i915/intel_hdmi.c
>> +++ b/drivers/gpu/drm/i915/intel_hdmi.c
>> @@ -933,6 +933,11 @@ bool intel_hdmi_compute_config(struct intel_encoder *encoder,
>>
>>   	if (adjusted_mode->flags & DRM_MODE_FLAG_DBLCLK) {
>>   		pipe_config->pixel_multiplier = 2;
>> +
>> +		/* Fix up port_clock since 27027 is not divisible by 2 */
>> +		if (pipe_config->adjusted_mode.crtc_clock == 13513) {
>> +			pipe_config->port_clock = 27027;
>> +		}
>
> Ugh. Oh well I suppose we'll want to be as accurate as possible. Would
> be nice if would could someone do this fixup already in drm core, but
> that would probably require changing to smaller clock units all over
> the place which doesn't sound fun at all. So I guess we get to leave
> the kludge in the driver :(
>
> This also got me thinking about the 12bpc case as well. It's clearly
> busted with double clocked modes now. Care to fix that up as well?
>
> PS. did you ever send that separate patch to fix up the interlace
> flags in some of the double clocked modes? I don't remember seeing
> such a patch at least.

Actually I just checked again and it was the 576i@100Hz modes and they 
are still incorrect. Let me send out the patch.

>
>>   	}
>>
>>   	if (intel_hdmi->color_range)
>> --
>> 1.7.9.5
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>

      parent reply	other threads:[~2014-09-26 16:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24 22:49 [PATCH] drm/i915/hdmi: Compute port_clock for 27.027 pixel replicated modes clinton.a.taylor
2014-09-26 15:58 ` Ville Syrjälä
2014-09-26 16:28   ` Clint Taylor
2014-09-30 12:46     ` Ville Syrjälä
2014-10-06 23:17       ` Clint Taylor
2014-10-07  8:29         ` Ville Syrjälä
2014-10-08  9:36           ` Daniel Vetter
2014-09-26 16:40   ` Clint Taylor [this message]

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=54259717.8070904@intel.com \
    --to=clinton.a.taylor@intel.com \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.intel.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