intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/dp: remove static variable for aux last status
Date: Wed, 2 Oct 2019 17:47:16 +0300	[thread overview]
Message-ID: <20191002144716.GV1208@intel.com> (raw)
In-Reply-To: <20191002144138.7917-1-jani.nikula@intel.com>

On Wed, Oct 02, 2019 at 05:41:38PM +0300, Jani Nikula wrote:
> Add aux_busy_last_status to intel_dp. Don't bother with initializing to
> all ones; the only difference is potentially missing logging for one
> error case if the readout is all zeros.
> 
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>a

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

> ---
>  drivers/gpu/drm/i915/display/intel_display_types.h | 1 +
>  drivers/gpu/drm/i915/display/intel_dp.c            | 5 ++---
>  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_display_types.h b/drivers/gpu/drm/i915/display/intel_display_types.h
> index 976669f01a8c..1602aac7ca0f 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_types.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_types.h
> @@ -1185,6 +1185,7 @@ struct intel_dp {
>  	/* sink or branch descriptor */
>  	struct drm_dp_desc desc;
>  	struct drm_dp_aux aux;
> +	u32 aux_busy_last_status;
>  	u8 train_set[4];
>  	int panel_power_up_delay;
>  	int panel_power_down_delay;
> diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
> index f9fc9a1383e3..c697f551a1b0 100644
> --- a/drivers/gpu/drm/i915/display/intel_dp.c
> +++ b/drivers/gpu/drm/i915/display/intel_dp.c
> @@ -1347,13 +1347,12 @@ intel_dp_aux_xfer(struct intel_dp *intel_dp,
>  	trace_i915_reg_rw(false, ch_ctl, status, sizeof(status), true);
>  
>  	if (try == 3) {
> -		static u32 last_status = -1;
>  		const u32 status = intel_uncore_read(uncore, ch_ctl);
>  
> -		if (status != last_status) {
> +		if (status != intel_dp->aux_busy_last_status) {
>  			WARN(1, "dp_aux_ch not started status 0x%08x\n",
>  			     status);
> -			last_status = status;
> +			intel_dp->aux_busy_last_status = status;
>  		}
>  
>  		ret = -EBUSY;
> -- 
> 2.20.1
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
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-10-02 14:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-02 14:41 [PATCH] drm/i915/dp: remove static variable for aux last status Jani Nikula
2019-10-02 14:47 ` Ville Syrjälä [this message]
2019-10-02 21:08 ` ✗ Fi.CI.BAT: failure for " Patchwork
2019-10-03 10:17 ` ✗ Fi.CI.BAT: failure for drm/i915/dp: remove static variable for aux last status (rev2) Patchwork
2019-10-03 10:25   ` Jani Nikula
2019-10-03 12:35 ` ✓ Fi.CI.BAT: success for drm/i915/dp: remove static variable for aux last status (rev3) Patchwork
2019-10-03 19:22 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-10-04 12:11   ` 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=20191002144716.GV1208@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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;
as well as URLs for NNTP newsgroup(s).