From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH 0/3] drm/i915: vlv pre_enable/enable callback refactoring
Date: Tue, 30 Jul 2013 11:08:27 +0300 [thread overview]
Message-ID: <cover.1375171206.git.jani.nikula@intel.com> (raw)
Address Daniel's old complaints about ->pre_enable and ->enable called
in the same spot in valleyview_crtc_enable [1].
Rebased on top of Chris' yet-to-be-merged locking patch [2].
Cheers,
Jani.
[1] http://mid.gmane.org/CAKMK7uFs9EMvMW8BnS24e5UNm1D7JrfVg3SD5SDFtVEamGfOOg@mail.gmail.com
[2] http://mid.gmane.org/1374865055-17919-1-git-send-email-chris@chris-wilson.co.uk
Jani Nikula (3):
drm/i915: rearrange vlv dp enable and pre_enable callbacks
drm/i915: rearrange vlv hdmi enable and pre_enable callbacks
drm/i915: move encoder->enable callback later in VLV crtc enable
drivers/gpu/drm/i915/intel_display.c | 7 ++--
drivers/gpu/drm/i915/intel_dp.c | 73 ++++++++++++++++++----------------
drivers/gpu/drm/i915/intel_hdmi.c | 20 +++++-----
3 files changed, 53 insertions(+), 47 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-07-30 8:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 8:08 Jani Nikula [this message]
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
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ä
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=cover.1375171206.git.jani.nikula@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.