All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: "Thulasimani, Sivakumar" <sivakumar.thulasimani@intel.com>,
	Mika Kahola <mika.kahola@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Skip DDI PLL selection for DSI
Date: Tue, 09 Feb 2016 08:32:09 +0200	[thread overview]
Message-ID: <87twliv1g6.fsf@intel.com> (raw)
In-Reply-To: <56B9546B.6070107@intel.com>

On Tue, 09 Feb 2016, "Thulasimani, Sivakumar" <sivakumar.thulasimani@intel.com> wrote:
> On 2/5/2016 4:59 PM, Mika Kahola wrote:
>> Skip DDI PLL selection if display type is DSI/MIPI.
>>
>> Signed-off-by: Mika Kahola <mika.kahola@intel.com>
>> ---
>>   drivers/gpu/drm/i915/intel_display.c | 9 +++++++--
>>   1 file changed, 7 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
>> index d7de2a5..5da98b2 100644
>> --- a/drivers/gpu/drm/i915/intel_display.c
>> +++ b/drivers/gpu/drm/i915/intel_display.c
>> @@ -9902,8 +9902,13 @@ static void broadwell_modeset_commit_cdclk(struct drm_atomic_state *old_state)
>>   static int haswell_crtc_compute_clock(struct intel_crtc *crtc,
>>   				      struct intel_crtc_state *crtc_state)
>>   {
>> -	if (!intel_ddi_pll_select(crtc, crtc_state))
>> -		return -EINVAL;
>> +	struct intel_encoder *intel_encoder =
>> +		intel_ddi_get_crtc_new_encoder(crtc_state);
>> +
>> +	if (intel_encoder->type != INTEL_OUTPUT_DSI) {
>> +		if (!intel_ddi_pll_select(crtc, crtc_state))
>> +			return -EINVAL;
>> +	}
>>   
> can this be moved inside bxt_ddi_pll_select ? we can avoid this check for
> other platforms that also execute this function.

I asked Mika to do it this way, but if you feel strongly about it I
guess I could be persuaded otherwise too.

My main point is, if we pass on DSI encoders to DDI functions in some
cases but mostly not, it will muddy the waters and eventually people end
up checking for "is dsi" all around DDI just because they can't be
bothered to check if the functions are really called for DDI only or
not. It's more of a maintainability concern than anything else.

BR,
Jani.



>
> regards,
> Sivakumar
>>   	crtc->lowfreq_avail = false;
>>   
>

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-02-09  6:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-05 11:29 [PATCH] drm/i915: Skip DDI PLL selection for DSI Mika Kahola
2016-02-05 11:47 ` ✗ Fi.CI.BAT: failure for " Patchwork
2016-02-09  2:52 ` [PATCH] " Thulasimani, Sivakumar
2016-02-09  6:32   ` Jani Nikula [this message]
2016-02-09  7:46     ` Thulasimani, Sivakumar
2016-02-09  9:52       ` Ville Syrjälä
2016-02-09 15:43         ` 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=87twliv1g6.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kahola@intel.com \
    --cc=sivakumar.thulasimani@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 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.