Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: "Navare, Manasi" <manasi.d.navare@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/display: Fix shared dpll mismatch for bigjoiner slave
Date: Tue, 20 Jul 2021 12:53:23 +0530	[thread overview]
Message-ID: <7e483a82-b997-4eb1-d585-484fc98b3914@intel.com> (raw)
In-Reply-To: <20210719185840.GA30216@labuser-Z97X-UD5H>


On 7/20/2021 12:28 AM, Navare, Manasi wrote:
> On Mon, Jul 19, 2021 at 11:47:51AM +0530, Nautiyal, Ankit K wrote:
>> Patch looks good to me.
>>
>> Please find below some suggestions
>>
>> On 7/15/2021 4:04 AM, Manasi Navare wrote:
>>> Currently when we do the HW state readout, we dont set the shared dpll to NULL
>>> for the bigjoiner slave which should not have a DPLL assigned. So it has
>>> some garbage while the HW state readout is NULL. So explicitly reset
>>> the shared dpll for bigjoiner slave pipe.
>>>
>>> Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/3465
>>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>> Cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>>> Tested-By: Swati Sharma <swati2.sharma@intel.com>
>> checkpatch warning about tested-by tag.
>>> Signed-off-by: Manasi Navare <manasi.d.navare@intel.com>
>>> ---
>>>   drivers/gpu/drm/i915/display/intel_display.c | 4 ++++
>>>   1 file changed, 4 insertions(+)
>>>
>>> diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
>>> index 65ddb6ca16e6..c274bfb8e549 100644
>>> --- a/drivers/gpu/drm/i915/display/intel_display.c
>>> +++ b/drivers/gpu/drm/i915/display/intel_display.c
>>> @@ -9006,6 +9006,10 @@ verify_crtc_state(struct intel_crtc *crtc,
>>>   	if (!new_crtc_state->hw.active)
>>>   		return;
>>> +	if (new_crtc_state->bigjoiner_slave)
>>> +		/* No PLLs set for slave */
>>> +		pipe_config->shared_dpll = NULL;
>>> +
>> there is a check for bigjoiner_slave, couple of lines above this:
>>
>> if (new_crtc_state->bigjoiner_slave)
>>                  master = new_crtc_state->bigjoiner_linked_crtc;
>>
>> Perhaps it will make sense to club the set shared_dpll to NULL, along with
>> these lines.
> Yup, thats where I was resetting in earlier patch but then it actually gets overridden in a function call
> after this point so need to reset it after separately.
>
> Manasi

You are right. I missed that, pipe_config gets overwritten just before 
this point, so the change is at the right place.

Regards,

Ankit


>
>> In any case:
>>
>> Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>>
>>>   	intel_pipe_config_sanity_check(dev_priv, pipe_config);
>>>   	if (!intel_pipe_config_compare(new_crtc_state,
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2021-07-20  7:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 22:34 [Intel-gfx] [PATCH] drm/i915/display: Fix shared dpll mismatch for bigjoiner slave Manasi Navare
2021-07-16 15:44 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display: Fix shared dpll mismatch for bigjoiner slave (rev3) Patchwork
2021-07-16 16:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-07-16 20:26 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-07-19  6:17 ` [Intel-gfx] [PATCH] drm/i915/display: Fix shared dpll mismatch for bigjoiner slave Nautiyal, Ankit K
2021-07-19 18:58   ` Navare, Manasi
2021-07-20  7:23     ` Nautiyal, Ankit K [this message]
2021-07-21 17:42       ` Navare, Manasi
2021-08-10 13:19 ` Jani Nikula
  -- strict thread matches above, loose matches on Subject: below --
2021-06-23 19:04 Manasi Navare

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=7e483a82-b997-4eb1-d585-484fc98b3914@intel.com \
    --to=ankit.k.nautiyal@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=manasi.d.navare@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