From: "Kannan, Vandana" <vandana.kannan@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [RFC 4/7] drm/i915: Program PPS registers
Date: Mon, 27 Oct 2014 14:55:40 +0530 [thread overview]
Message-ID: <544E0F94.6020006@intel.com> (raw)
In-Reply-To: <20141020160848.GT26941@phenom.ffwll.local>
On 20-Oct-14 9:38 PM, Daniel Vetter wrote:
> On Mon, Oct 20, 2014 at 06:20:06PM +0530, Vandana Kannan wrote:
>> Actually set values into PPS related registers. This implementation is
>> equivalent to intel_dp_panel_power_sequencer_registers where the values
>> saved intially are written into registers.
>>
>> Signed-off-by: Vandana Kannan <vandana.kannan@intel.com>
>> ---
>> drivers/gpu/drm/i915/intel_dp.c | 80 ++------------------------------------
>> drivers/gpu/drm/i915/intel_drv.h | 3 ++
>> drivers/gpu/drm/i915/intel_panel.c | 70 +++++++++++++++++++++++++++++++++
>> 3 files changed, 76 insertions(+), 77 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
>> index a433c5f..ca11eb1 100644
>> --- a/drivers/gpu/drm/i915/intel_dp.c
>> +++ b/drivers/gpu/drm/i915/intel_dp.c
>> @@ -248,7 +248,7 @@ unpack_aux(uint32_t src, uint8_t *dst, int dst_bytes)
>> }
>>
>> /* hrawclock is 1/4 the FSB frequency */
>> -static int
>> +int
>> intel_hrawclk(struct drm_device *dev)
>> {
>> struct drm_i915_private *dev_priv = dev->dev_private;
>> @@ -281,11 +281,6 @@ intel_hrawclk(struct drm_device *dev)
>> }
>> }
>>
>> -static void
>> -intel_dp_init_panel_power_sequencer_registers(struct drm_device *dev,
>> - struct intel_dp *intel_dp,
>> - struct edp_power_seq *out);
>> -
>> static void pps_lock(struct intel_dp *intel_dp)
>> {
>> struct intel_digital_port *intel_dig_port = dp_to_dig_port(intel_dp);
>> @@ -4716,76 +4711,6 @@ static void intel_dp_init_panel_power_timestamps(struct intel_dp *intel_dp)
>> intel_dp->last_backlight_off = jiffies;
>> }
>>
>> -static void
>> -intel_dp_init_panel_power_sequencer_registers(struct drm_device *dev,
>> - struct intel_dp *intel_dp,
>> - struct edp_power_seq *seq)
>
> Hm, moving this function looks like it would be clearer as part of patch
> 1?
>
> Otherwise I've done a (very) quick read-through of your series and on a
> high level it looks sane I think. So please sign someone up for the
> detailed review (and make sure that person is aware of that AR) so I can
> merge this.
>
> Thanks, Daniel
>
Thanks Daniel..
I went through the LVDS and DSI parts. If software delays are used for
both, would it really add more value to have the delays in a function in
intel_panel.c and call whenever required ?
I'm thinking directly calling a msleep would be simpler but that would
mean the PPS part wont be in one place in intel_panel.c.
Let me know what you think about this..
- Vandana
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-10-27 9:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 12:50 [RFC v2 0/7] Rearranging PPS related code Vandana Kannan
2014-10-20 12:50 ` [RFC 1/7] drm/i915: Move around funcs related to eDP PPS Vandana Kannan
2014-10-20 12:50 ` [RFC 2/7] drm/i915: Setup PPS in intel_panel Vandana Kannan
2014-10-20 12:50 ` [RFC 3/7] drm/i915: Split PPS setup code based on platform Vandana Kannan
2014-10-20 12:50 ` [RFC 4/7] drm/i915: Program PPS registers Vandana Kannan
2014-10-20 16:08 ` Daniel Vetter
2014-10-20 16:10 ` Daniel Vetter
2014-10-20 16:28 ` Ville Syrjälä
2014-10-27 9:25 ` Kannan, Vandana [this message]
2014-10-27 14:23 ` Daniel Vetter
2014-10-20 12:50 ` [RFC 5/7] drm/i915: Split PPS reg write func based on platform Vandana Kannan
2014-10-20 12:50 ` [RFC 6/7] drm/i915: Replace all refs to intel_dp delays Vandana Kannan
2014-10-20 12:50 ` [RFC 7/7] drm/i915: Modify refs to intel dp timestamps Vandana Kannan
2014-10-20 16:14 ` Daniel Vetter
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=544E0F94.6020006@intel.com \
--to=vandana.kannan@intel.com \
--cc=daniel@ffwll.ch \
--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