All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shankar, Uma" <uma.shankar@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Cc: "Khor, Swee Aun" <swee.aun.khor@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/display: Fix mode private_flags comparison at atomic_check
Date: Thu, 26 Mar 2020 11:59:49 +0000	[thread overview]
Message-ID: <E7C9878FBA1C6D42A1CA3F62AEB6945F8243C8DF@BGSMSX104.gar.corp.intel.com> (raw)
In-Reply-To: <1ba94cef-ea8a-2271-2915-2837f8eabf21@linux.intel.com>



> -----Original Message-----
> From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Sent: Thursday, March 26, 2020 4:18 PM
> To: Shankar, Uma <uma.shankar@intel.com>; intel-gfx@lists.freedesktop.org
> Cc: Ville Syrjä <ville.syrjala@linux.intel.com>; Kai Vehmanen
> <kai.vehmanen@linux.intel.com>; Souza, Jose <jose.souza@intel.com>; Khor, Swee
> Aun <swee.aun.khor@intel.com>
> Subject: Re: [PATCH] drm/i915/display: Fix mode private_flags comparison at
> atomic_check
> 
> Op 26-03-2020 om 08:49 schreef Uma Shankar:
> > This patch fixes the private_flags of mode to be checked and compared
> > against uapi.mode and not from hw.mode. This helps properly trigger
> > modeset at boot if desired by driver.
> >
> > It helps resolve audio_codec initialization issues if display is
> > connected at boot. Initial discussion on this issue has happened on
> > below thread:
> > https://patchwork.freedesktop.org/series/74828/
> >
> > Fixes: https://gitlab.freedesktop.org/drm/intel/issues/1363
> 
> Wrong use of fixes. :)
> 
> Use dim fixes original-commit-id to reference the commit. And for this use the
> Closes: tag.
> 
> Other than that looks good. :)
> 
> So with headers fixed:

Thanks for the feedback Maarten. Floated v2 with this updated.

Regards,
Uma Shankar

> Reviewed-By: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> 
> > Cc: Ville Syrjä <ville.syrjala@linux.intel.com>
> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> > Cc: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> > Cc: Souza, Jose <jose.souza@intel.com>
> > Suggested-by: Ville Syrjä <ville.syrjala@linux.intel.com>
> > Signed-off-by: Uma Shankar <uma.shankar@intel.com>
> > Signed-off-by: SweeAun Khor <swee.aun.khor@intel.com>
> > ---
> >  drivers/gpu/drm/i915/display/intel_display.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_display.c
> > b/drivers/gpu/drm/i915/display/intel_display.c
> > index fe55c7c713f1..e630429af2c0 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display.c
> > +++ b/drivers/gpu/drm/i915/display/intel_display.c
> > @@ -14747,8 +14747,8 @@ static int intel_atomic_check(struct drm_device *dev,
> >  	/* Catch I915_MODE_FLAG_INHERITED */
> >  	for_each_oldnew_intel_crtc_in_state(state, crtc, old_crtc_state,
> >  					    new_crtc_state, i) {
> > -		if (new_crtc_state->hw.mode.private_flags !=
> > -		    old_crtc_state->hw.mode.private_flags)
> > +		if (new_crtc_state->uapi.mode.private_flags !=
> > +		    old_crtc_state->uapi.mode.private_flags)
> >  			new_crtc_state->uapi.mode_changed = true;
> >  	}
> >
> 

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-03-26 11:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26  7:49 [Intel-gfx] [PATCH] drm/i915/display: Fix mode private_flags comparison at atomic_check Uma Shankar
2020-03-26  8:22 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-03-26  9:49 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-03-26 10:47 ` [Intel-gfx] [PATCH] " Maarten Lankhorst
2020-03-26 11:59   ` Shankar, Uma [this message]
2020-03-26 16:17 ` Ville Syrjälä
2020-03-26 17:45   ` Shankar, Uma

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=E7C9878FBA1C6D42A1CA3F62AEB6945F8243C8DF@BGSMSX104.gar.corp.intel.com \
    --to=uma.shankar@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=swee.aun.khor@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.