From: Jani Nikula <jani.nikula@linux.intel.com>
To: Vandana Kannan <vandana.kannan@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/i915: Use vlv_power_sequencer_pipe() only to get pipe
Date: Fri, 12 Dec 2014 12:39:32 +0200 [thread overview]
Message-ID: <87mw6t6tjv.fsf@intel.com> (raw)
In-Reply-To: <1415618923-24110-3-git-send-email-vandana.kannan@intel.com>
On Mon, 10 Nov 2014, Vandana Kannan <vandana.kannan@intel.com> wrote:
> vlv_power_sequencer_pipe() calls into init PPS functions. Changing this
> function to make it only return pipe and not call PPS init.
> This is because PPS init calls into this function to get a pipe ID and all
> other callers just need the pipe ID.
>
> Signed-off-by: Vandana Kannan <vandana.kannan@intel.com>
> ---
> drivers/gpu/drm/i915/intel_dp.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_dp.c b/drivers/gpu/drm/i915/intel_dp.c
> index 34d8105..1d4bf78 100644
> --- a/drivers/gpu/drm/i915/intel_dp.c
> +++ b/drivers/gpu/drm/i915/intel_dp.c
> @@ -434,10 +434,6 @@ vlv_power_sequencer_pipe(struct intel_dp *intel_dp)
> pipe_name(intel_dp->pps_pipe),
> port_name(intel_dig_port->port));
>
> - /* init power sequencer on this pipe and port */
> - intel_dp_init_panel_power_sequencer(dev, intel_dp);
> - intel_dp_init_panel_power_sequencer_registers(dev, intel_dp);
IIUC if you end up this far in the function it's a special case, in most
cases it'll return with intel_dp->pps_pipe. And the special case
probably means you'll need to setup the registers and everything.
Ville?
BR,
Jani.
> -
> /*
> * Even vdd force doesn't work until we've made
> * the power sequencer lock in on the port.
> --
> 2.0.1
>
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-12-12 10:39 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 [this message]
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 ` [PATCH 0/3] Rearranging eDP PPS code Kannan, Vandana
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=87mw6t6tjv.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=vandana.kannan@intel.com \
/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