All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v5 7/7] drm/i915/display: Add comment to a function that probably can be removed
Date: Fri, 20 Dec 2019 17:48:49 +0200	[thread overview]
Message-ID: <20191220154849.GP1208@intel.com> (raw)
In-Reply-To: <20191220152954.83276-7-jose.souza@intel.com>

On Fri, Dec 20, 2019 at 07:29:54AM -0800, José Roberto de Souza wrote:
> This function is only called from port sync and it is identical to
> what will be executed again in intel_update_crtc() over port sync
> pipes.
> If it is really necessary it at least deserves a better name and a
> comment, leaving it to people working on port sync.

IMO if we need special cases for port sync we should refactor
the current code to accomodate that instead of copypasting
the whole current implementation, as was done when port sync
went it. But yeah, future work.

Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

> 
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Manasi Navare <manasi.d.navare@intel.com>
> Signed-off-by: José Roberto de Souza <jose.souza@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 11f2c13ec23e..592c843f2f3b 100644
> --- a/drivers/gpu/drm/i915/display/intel_display.c
> +++ b/drivers/gpu/drm/i915/display/intel_display.c
> @@ -14479,6 +14479,10 @@ static void intel_set_dp_tp_ctl_normal(struct intel_crtc *crtc,
>  	intel_dp_stop_link_train(intel_dp);
>  }
>  
> +/*
> + * TODO: This is only called from port sync and it is identical to what will be
> + * executed again in intel_update_crtc() over port sync pipes
> + */
>  static void intel_post_crtc_enable_updates(struct intel_crtc *crtc,
>  					   struct intel_atomic_state *state)
>  {
> -- 
> 2.24.1

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

  reply	other threads:[~2019-12-20 15:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20 15:29 [Intel-gfx] [PATCH v5 1/7] drm/i915: Introduce intel_crtc_state_alloc() José Roberto de Souza
2019-12-20 15:29 ` [Intel-gfx] [PATCH v5 2/7] drm/i915/display: Share intel_connector_needs_modeset() José Roberto de Souza
2019-12-20 15:38   ` Ville Syrjälä
2019-12-20 15:29 ` [Intel-gfx] [PATCH v5 3/7] drm/i915/tgl: Select master transcoder for MST stream José Roberto de Souza
2019-12-20 15:47   ` Ville Syrjälä
2019-12-20 16:53     ` Souza, Jose
2019-12-20 17:03       ` Ville Syrjälä
2019-12-20 18:43         ` Ville Syrjälä
2019-12-20 15:29 ` [Intel-gfx] [PATCH v5 4/7] drm/i915/display: Always enables MST master pipe first José Roberto de Souza
2019-12-20 15:29 ` [Intel-gfx] [PATCH v5 5/7] drm/i915/dp: Fix MST disable sequence José Roberto de Souza
2019-12-20 15:29 ` [Intel-gfx] [PATCH v5 6/7] drm/i915/display: Check if pipe fastset is allowed by external dependencies José Roberto de Souza
2019-12-20 16:04   ` Ville Syrjälä
2019-12-20 18:27     ` Souza, Jose
2019-12-20 15:29 ` [Intel-gfx] [PATCH v5 7/7] drm/i915/display: Add comment to a function that probably can be removed José Roberto de Souza
2019-12-20 15:48   ` Ville Syrjälä [this message]
2019-12-20 19:57 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v5,1/7] drm/i915: Introduce intel_crtc_state_alloc() Patchwork
2019-12-20 22:32 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2019-12-22 13:41 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork

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=20191220154849.GP1208@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jose.souza@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.