From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915: move encoder->enable callback later in VLV crtc enable
Date: Tue, 04 Jun 2013 13:49:39 +0300 [thread overview]
Message-ID: <87ehcif8vw.fsf@intel.com> (raw)
In-Reply-To: <1370341566-13203-3-git-send-email-jani.nikula@intel.com>
Failed to mention that this should address Daniel's complaints about the
->pre_enable and ->enable calls being in the same spot [1]. And while I
needed this for something else, it should be easy to do the eDP
backlight fix Daniel mentions on top.
Cheers,
Jani.
[1] http://mid.gmane.org/CAKMK7uFs9EMvMW8BnS24e5UNm1D7JrfVg3SD5SDFtVEamGfOOg@mail.gmail.com
On Tue, 04 Jun 2013, Jani Nikula <jani.nikula@intel.com> wrote:
> Encoder ->pre_enable and ->enable callbacks were moved back to back in
> VLV crtc enable sequence, which is not very useful. Move ->enable call
> at the end of the sequence.
>
> With the previously rearranged VLV DP and HDMI ->pre_enable and ->enable
> callbacks in place, this should not cause any functional changes.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/intel_display.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index c112466..4250beb 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -3607,10 +3607,6 @@ static void valleyview_crtc_enable(struct drm_crtc *crtc)
> if (encoder->pre_enable)
> encoder->pre_enable(encoder);
>
> - /* VLV wants encoder enabling _before_ the pipe is up. */
> - for_each_encoder_on_crtc(dev, crtc, encoder)
> - encoder->enable(encoder);
> -
> /* Enable panel fitting for eDP */
> i9xx_pfit_enable(intel_crtc);
>
> @@ -3624,6 +3620,9 @@ static void valleyview_crtc_enable(struct drm_crtc *crtc)
> intel_crtc_dpms_overlay(intel_crtc, true);
> intel_crtc_update_cursor(crtc, true);
>
> + for_each_encoder_on_crtc(dev, crtc, encoder)
> + encoder->enable(encoder);
> +
> mutex_unlock(&dev_priv->dpio_lock);
> }
>
> --
> 1.7.9.5
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2013-06-04 10:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 10:26 [PATCH 1/3] drm/i915: rearrange vlv dp enable and pre_enable callbacks Jani Nikula
2013-06-04 10:26 ` [PATCH 2/3] drm/i915: rearrange vlv hdmi " Jani Nikula
2013-06-04 10:26 ` [PATCH 3/3] drm/i915: move encoder->enable callback later in VLV crtc enable Jani Nikula
2013-06-04 10:49 ` Jani Nikula [this message]
2013-06-04 11:49 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2013-07-30 8:08 [PATCH 0/3] drm/i915: vlv pre_enable/enable callback refactoring Jani Nikula
2013-07-30 8:08 ` [PATCH 3/3] drm/i915: move encoder->enable callback later in VLV crtc enable Jani Nikula
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=87ehcif8vw.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.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.