From: "Kannan, Vandana" <vandana.kannan@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 0/3] Rearranging eDP PPS code
Date: Fri, 12 Dec 2014 15:05:06 +0530 [thread overview]
Message-ID: <548AB6CA.6090903@intel.com> (raw)
In-Reply-To: <1415618923-24110-1-git-send-email-vandana.kannan@intel.com>
Gentle reminder for review..
- Vandana
On 10-Nov-14 4:58 PM, Kannan, Vandana wrote:
> In the earlier RFC patch series, PPS related code was moved to intel_panel.c
> to make it usable for all internal panels. In this patch series, the PPS
> related functions are split based on platform in intel_dp.c itself.
> This avoids having code split across intel_dp.c and intel_panel.c w.r.t
> pps_lock/unlock, other pps delay functions.
> Also, the code rearrangement is for eDP alone.
>
> Vandana Kannan (3):
> drm/i915: Move PPS calls to edp_init
> drm/i915: Use vlv_power_sequencer_pipe() only to get pipe
> drm/i915: Splitting PPS functions based on platform
>
> drivers/gpu/drm/i915/intel_dp.c | 226 +++++++++++++++++++++++++--------------
> drivers/gpu/drm/i915/intel_drv.h | 3 +
> 2 files changed, 147 insertions(+), 82 deletions(-)
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2014-12-12 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 11:28 [PATCH 0/3] Rearranging eDP PPS code Vandana Kannan
2014-11-10 11:28 ` [PATCH 1/3] drm/i915: Move PPS calls to edp_init Vandana Kannan
2014-12-12 10:35 ` Jani Nikula
2014-11-10 11:28 ` [PATCH 2/3] drm/i915: Use vlv_power_sequencer_pipe() only to get pipe Vandana Kannan
2014-12-12 10:39 ` Jani Nikula
2014-11-10 11:28 ` [PATCH 3/3] drm/i915: Splitting PPS functions based on platform Vandana Kannan
2014-11-10 21:03 ` [PATCH 3/3] drm/i915: Splitting PPS functions based on shuang.he
2014-12-12 9:35 ` Kannan, Vandana [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=548AB6CA.6090903@intel.com \
--to=vandana.kannan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox