Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Das, Nirmoy" <nirmoy.das@linux.intel.com>
To: Alan Previn <alan.previn.teres.alexis@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/1] drm/i915/pxp: Add firmware status when ARB session fails
Date: Mon, 26 Sep 2022 10:22:01 +0200	[thread overview]
Message-ID: <2b5906f6-cdf7-fe25-0aaf-c19434987fda@linux.intel.com> (raw)
In-Reply-To: <20220922233112.243677-2-alan.previn.teres.alexis@intel.com>

LGTM Acked-by: Nirmoy Das <nirmoy.das@intel.com>

On 9/23/2022 1:31 AM, Alan Previn wrote:
> Add firmware status using a drm_warn when ARB session fails
> or else a drm_dbg when the ARB session register slot bit did
> get set.
>
> Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com>
> ---
>   drivers/gpu/drm/i915/pxp/intel_pxp_session.c | 1 +
>   drivers/gpu/drm/i915/pxp/intel_pxp_tee.c     | 2 ++
>   2 files changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/pxp/intel_pxp_session.c b/drivers/gpu/drm/i915/pxp/intel_pxp_session.c
> index 1bb5b5249157..c4f5c994ca51 100644
> --- a/drivers/gpu/drm/i915/pxp/intel_pxp_session.c
> +++ b/drivers/gpu/drm/i915/pxp/intel_pxp_session.c
> @@ -77,6 +77,7 @@ static int pxp_create_arb_session(struct intel_pxp *pxp)
>   		drm_err(&gt->i915->drm, "arb session failed to go in play\n");
>   		return ret;
>   	}
> +	drm_dbg(&gt->i915->drm, "PXP ARB session is alive\n");
>   
>   	if (!++pxp->key_instance)
>   		++pxp->key_instance;
> diff --git a/drivers/gpu/drm/i915/pxp/intel_pxp_tee.c b/drivers/gpu/drm/i915/pxp/intel_pxp_tee.c
> index 4b6f5655fab5..b388c9e77b59 100644
> --- a/drivers/gpu/drm/i915/pxp/intel_pxp_tee.c
> +++ b/drivers/gpu/drm/i915/pxp/intel_pxp_tee.c
> @@ -174,6 +174,8 @@ int intel_pxp_tee_cmd_create_arb_session(struct intel_pxp *pxp,
>   
>   	if (ret)
>   		drm_err(&i915->drm, "Failed to send tee msg ret=[%d]\n", ret);
> +	else if (msg_out.header.status != 0x0)
> +		drm_warn(&i915->drm, "PXP firmware failed arb session init request ret=[0x%08x]\n", msg_out.header.status);
>   
>   	return ret;
>   }

  reply	other threads:[~2022-09-26  8:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-22 23:31 [Intel-gfx] (no subject) Alan Previn
2022-09-22 23:31 ` [Intel-gfx] [PATCH 1/1] drm/i915/pxp: Add firmware status when ARB session fails Alan Previn
2022-09-26  8:22   ` Das, Nirmoy [this message]
2022-09-23  3:05 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/1] " Patchwork
2022-09-23 11:46 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-09-27 17:58   ` Matt Roper
  -- strict thread matches above, loose matches on Subject: below --
2022-09-23  0:22 [Intel-gfx] [PATCH 0/1] Add PXP firmware respose on ARB failure Alan Previn
2022-09-23  0:22 ` [Intel-gfx] [PATCH 1/1] drm/i915/pxp: Add firmware status when ARB session fails Alan Previn

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=2b5906f6-cdf7-fe25-0aaf-c19434987fda@linux.intel.com \
    --to=nirmoy.das@linux.intel.com \
    --cc=alan.previn.teres.alexis@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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