All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: rearrange vlv dp enable and pre_enable callbacks
Date: Tue, 30 Jul 2013 12:05:34 +0300	[thread overview]
Message-ID: <877gg8to2p.fsf@intel.com> (raw)
In-Reply-To: <20130730083201.GE27041@cantiga.alporthouse.com>

On Tue, 30 Jul 2013, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Tue, Jul 30, 2013 at 11:08:28AM +0300, Jani Nikula wrote:
>> Currently ->pre_enable and ->enable are called back to back. Rearrange
>> the DP callbacks to make it possible to move ->enable call later.
>
> A one sentence explanation why we want ->enable later would be perfect.
> If you can concisely explain why the code was originally written as is,
> and why we want to do it differently in the near future, that would be
> ideal.

Good point. How about,

for patches 1&2:

"""
VLV wants encoder enabling before the pipe is up. This is currently
achieved through calling the ->enable callback early, right after the
->pre_enable callback, in valleyview_crtc_enable(). This loses both the
distinction between ->pre_enable and ->enable on VLV and the possibility
to use a hook at the end of the modeset sequence.

Rearrange the DP callbacks to make it possible to move ->enable call
later. Basically do everything in ->pre_enable on VLV, and make ->enable
a NOP.

There should be no functional changes.
"""

for patch 3:

"""
VLV wants encoder enabling before the pipe is up. With the previously
rearranged VLV DP and HDMI ->pre_enable and ->enable callbacks in place,
this no longer depends on the early ->enable hook call. Move the
->enable call at the end of the sequence, similar to the crtc enable on
other platforms. This will be needed e.g. for moving the eDP backlight
enabling to the right place in the sequence, currently done too early on
VLV.

There should be no functional changes.
"""

I'll send the revised patches once we agree on the wording.

Thanks,
Jani.

  reply	other threads:[~2013-07-30  9:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30  8:08 [PATCH 0/3] drm/i915: vlv pre_enable/enable callback refactoring Jani Nikula
2013-07-30  8:08 ` [PATCH 1/3] drm/i915: rearrange vlv dp enable and pre_enable callbacks Jani Nikula
2013-07-30  8:32   ` Chris Wilson
2013-07-30  9:05     ` Jani Nikula [this message]
2013-07-30  9:11       ` Chris Wilson
2013-07-30  8:08 ` [PATCH 2/3] drm/i915: rearrange vlv hdmi " Jani Nikula
2013-07-30  8:08 ` [PATCH 3/3] drm/i915: move encoder->enable callback later in VLV crtc enable Jani Nikula
2013-07-30  9:20 ` [PATCH v3 1/3] drm/i915: rearrange vlv dp enable and pre_enable callbacks Jani Nikula
2013-07-30  9:20   ` [PATCH v3 2/3] drm/i915: rearrange vlv hdmi " Jani Nikula
2013-07-30  9:20   ` [PATCH v3 3/3] drm/i915: move encoder->enable callback later in VLV crtc enable Jani Nikula
2013-07-30 10:58     ` Chris Wilson
2013-08-05  6:14       ` Daniel Vetter
2013-07-30 14:24     ` Ville Syrjälä
  -- strict thread matches above, loose matches on Subject: below --
2013-06-04 10:26 [PATCH 1/3] drm/i915: rearrange vlv dp enable and pre_enable callbacks 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=877gg8to2p.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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.