From: Daniel Vetter <daniel@ffwll.ch>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/i915: handle sdvo input pixel multiplier correctly again
Date: Tue, 3 Sep 2013 21:15:27 +0200 [thread overview]
Message-ID: <20130903191527.GA28675@phenom.ffwll.local> (raw)
In-Reply-To: <20130903185315.GJ11428@intel.com>
On Tue, Sep 03, 2013 at 09:53:15PM +0300, Ville Syrjälä wrote:
> On Tue, Sep 03, 2013 at 08:40:36PM +0200, Daniel Vetter wrote:
> > The sdvo input timing needs to be the actual mode, the sdvo
> > encoder automatically adjusts for the need of pixel doubling or
> > quadrupling. This was lost in pipe config conversion of the
> > pixel multiplier in
> >
> > commit 6cc5f341b5830541a1b6945435ca90c69b1b8b21
> > Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Date: Wed Mar 27 00:44:53 2013 +0100
> >
> > drm/i915: add pipe_config->pixel_multiplier
> >
> > While at it ditch the intel_ prefix from the crtc in
> > intel_sdvo_mode_set.
> >
> > Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> For both patches:
> Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Picked up for -fixes, thanks for the review. I'll also rebase dinq so that
we can slurp in your patches on top of this.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2013-09-03 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 18:40 [PATCH 1/2] drm/i915: handle sdvo input pixel multiplier correctly again Daniel Vetter
2013-09-03 18:40 ` [PATCH 2/2] drm/i915: fix i9xx_crtc_clock_get for multiplied pixels Daniel Vetter
2013-09-03 18:53 ` [PATCH 1/2] drm/i915: handle sdvo input pixel multiplier correctly again Ville Syrjälä
2013-09-03 19:15 ` Daniel Vetter [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=20130903191527.GA28675@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--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 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.