From: Daniel Vetter <daniel@ffwll.ch>
To: Peter Ross <pross@xvid.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: specify vertical timings in frame units for interlaced modes (gen4+)
Date: Mon, 16 Jan 2012 21:04:08 +0100 [thread overview]
Message-ID: <20120116200408.GD3627@phenom.ffwll.local> (raw)
In-Reply-To: <b829f29d7e6f8132c19493229d095648f663d787.1326550234.git.pross@xvid.org>
On Sun, Jan 15, 2012 at 01:52:11AM +1100, Peter Ross wrote:
> The G35/G45/SandyBridge chipsets expect vertical timings in frame units,
> whereas the DRM subsystem uses field units internally for interlaced modes.
>
> Signed-off-by: Peter Ross <pross@xvid.org>
On a quick look at the patch it have a confusion about chipset
generations. We generally call g35 i965 to avoid confusion with the gen3
device g33. Also i9xx_crtc_mode_set is only used on pre-ironlake (=gen5)
and hence does not include snb. You might want to fix up
ironlake_crtc_mode_set, too.
When quickly discussing this with Jesse on irc we concluded that this is
fine if it comes with a tested-by (for both patches) attached, preferrably
with quick details on which machines this was tested on.
-Daniel
> ---
> drivers/gpu/drm/i915/intel_display.c | 8 ++++++++
> 1 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 2a3f707..ae62f5f 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -5316,6 +5316,14 @@ static int i9xx_crtc_mode_set(struct drm_crtc *crtc,
> adjusted_mode->crtc_vblank_end -= 1;
> adjusted_mode->crtc_vsync_end -= 1;
> adjusted_mode->crtc_vsync_start -= 1;
> + if (INTEL_INFO(dev)->gen >= 4) {
> + adjusted_mode->crtc_vdisplay *= 2;
> + adjusted_mode->crtc_vtotal *= 2;
> + adjusted_mode->crtc_vblank_start *= 2;
> + adjusted_mode->crtc_vblank_end *= 2;
> + adjusted_mode->crtc_vsync_end *= 2;
> + adjusted_mode->crtc_vsync_start *= 2;
> + }
> } else
> pipeconf &= ~PIPECONF_INTERLACE_MASK; /* progressive */
>
> --
> 1.7.5.4
>
> -- Peter
> (A907 E02F A6E5 0CD2 34CD 20D2 6760 79C5 AC40 DD6B)
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-01-16 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 14:52 [PATCH 0/2] drm/i915: interlaced mode support (G35 VGA/SDVO) Peter Ross
2012-01-14 14:52 ` [PATCH 1/2] drm/i915: specify vertical timings in frame units for interlaced modes (gen4+) Peter Ross
2012-01-16 19:50 ` Jesse Barnes
2012-01-16 20:02 ` Eugeni Dodonov
2012-01-16 20:04 ` Daniel Vetter [this message]
2012-01-14 14:52 ` [PATCH 2/2] drm/i915: allow interlaced mode output on the SDVO connector Peter Ross
2012-01-16 14:23 ` [PATCH 0/2] drm/i915: interlaced mode support (G35 VGA/SDVO) Eugeni Dodonov
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=20120116200408.GD3627@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=pross@xvid.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.