Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
	<intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 3/5] drm/xe: Use gsc_proxy_init_done to check proxy status
Date: Tue, 13 Feb 2024 15:22:04 -0800	[thread overview]
Message-ID: <863431e0-1897-4d58-8bca-866b8c90cc54@intel.com> (raw)
In-Reply-To: <20240209101412.1326176-4-suraj.kandpal@intel.com>



On 2/9/2024 2:14 AM, Suraj Kandpal wrote:
> Expose gsc_proxy_init_done so that we can check if gsc proxy has
> been initialized or not.
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
>   drivers/gpu/drm/xe/display/xe_hdcp_gsc.c | 25 +++++++++++++++++++++++-
>   drivers/gpu/drm/xe/xe_gsc_proxy.c        |  4 ++--
>   drivers/gpu/drm/xe/xe_gsc_proxy.h        |  1 +
>   3 files changed, 27 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/display/xe_hdcp_gsc.c b/drivers/gpu/drm/xe/display/xe_hdcp_gsc.c
> index 5d1d0054b578..425db3532ce5 100644
> --- a/drivers/gpu/drm/xe/display/xe_hdcp_gsc.c
> +++ b/drivers/gpu/drm/xe/display/xe_hdcp_gsc.c
> @@ -4,8 +4,12 @@
>    */
>   
>   #include <drm/drm_print.h>
> +
>   #include "intel_hdcp_gsc.h"
>   #include "xe_device_types.h"
> +#include "xe_gt.h"
> +#include "xe_gsc_proxy.h"
> +#include "xe_pm.h"
>   
>   bool intel_hdcp_gsc_cs_required(struct xe_device *xe)
>   {
> @@ -14,7 +18,26 @@ bool intel_hdcp_gsc_cs_required(struct xe_device *xe)
>   
>   bool intel_hdcp_gsc_check_status(struct xe_device *xe)
>   {
> -	return false;
> +	struct xe_tile *tile = xe_device_get_root_tile(xe);
> +	struct xe_gt *gt = tile->media_gt;
> +	bool ret = true;
> +

Sorry for missing this in the previous rev, but I just remembered that 
if the GSC FW is not enabled then the forcewake domain is not 
initialized, which would lead to the forcewake_get throwing an error, so 
we need a check here first:

         if (!xe_uc_fw_is_enabled(&gt->uc.gsc.fw))
                 return false;

With this change:
Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>

Daniele

> +	xe_pm_runtime_get(xe);
> +	ret = xe_force_wake_get(gt_to_fw(gt), XE_FW_GSC);
> +	if (ret) {
> +		drm_dbg_kms(&xe->drm,
> +			    "failed to get forcewake to check proxy status\n");
> +		ret = false;
> +		goto out;
> +	}
> +
> +	if (!xe_gsc_proxy_init_done(&gt->uc.gsc))
> +		ret = false;
> +
> +	xe_force_wake_put(gt_to_fw(gt), XE_FW_GSC);
> +out:
> +	xe_pm_runtime_put(xe);
> +	return ret;
>   }
>   
>   int intel_hdcp_gsc_init(struct xe_device *xe)
> diff --git a/drivers/gpu/drm/xe/xe_gsc_proxy.c b/drivers/gpu/drm/xe/xe_gsc_proxy.c
> index 309ef80e3b95..1ced6b4d4946 100644
> --- a/drivers/gpu/drm/xe/xe_gsc_proxy.c
> +++ b/drivers/gpu/drm/xe/xe_gsc_proxy.c
> @@ -66,7 +66,7 @@ static inline struct xe_device *kdev_to_xe(struct device *kdev)
>   	return dev_get_drvdata(kdev);
>   }
>   
> -static bool gsc_proxy_init_done(struct xe_gsc *gsc)
> +bool xe_gsc_proxy_init_done(struct xe_gsc *gsc)
>   {
>   	struct xe_gt *gt = gsc_to_gt(gsc);
>   	u32 fwsts1 = xe_mmio_read32(gt, HECI_FWSTS1(MTL_GSC_HECI1_BASE));
> @@ -528,7 +528,7 @@ int xe_gsc_proxy_start(struct xe_gsc *gsc)
>   	if (err)
>   		return err;
>   
> -	if (!gsc_proxy_init_done(gsc)) {
> +	if (!xe_gsc_proxy_init_done(gsc)) {
>   		xe_gt_err(gsc_to_gt(gsc), "GSC FW reports proxy init not completed\n");
>   		return -EIO;
>   	}
> diff --git a/drivers/gpu/drm/xe/xe_gsc_proxy.h b/drivers/gpu/drm/xe/xe_gsc_proxy.h
> index 908f9441f093..c511ade6b863 100644
> --- a/drivers/gpu/drm/xe/xe_gsc_proxy.h
> +++ b/drivers/gpu/drm/xe/xe_gsc_proxy.h
> @@ -11,6 +11,7 @@
>   struct xe_gsc;
>   
>   int xe_gsc_proxy_init(struct xe_gsc *gsc);
> +bool xe_gsc_proxy_init_done(struct xe_gsc *gsc);
>   void xe_gsc_proxy_remove(struct xe_gsc *gsc);
>   int xe_gsc_proxy_start(struct xe_gsc *gsc);
>   


  reply	other threads:[~2024-02-13 23:22 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 10:14 [PATCH 0/5] XE HDCP Enablement Suraj Kandpal
2024-02-09 10:14 ` [PATCH 1/5] drm/i915/hdcp: Move intel_hdcp_gsc_message def away from header file Suraj Kandpal
2024-02-26  8:18   ` Murthy, Arun R
2024-02-09 10:14 ` [PATCH 2/5] drm/xe/hdcp: Use xe_device struct Suraj Kandpal
2024-02-13 23:16   ` Daniele Ceraolo Spurio
2024-02-14  5:30     ` Kandpal, Suraj
2024-02-26  8:45       ` Murthy, Arun R
2024-02-09 10:14 ` [PATCH 3/5] drm/xe: Use gsc_proxy_init_done to check proxy status Suraj Kandpal
2024-02-13 23:22   ` Daniele Ceraolo Spurio [this message]
2024-02-26 10:21     ` Murthy, Arun R
2024-02-09 10:14 ` [PATCH 4/5] drm/xe/hdcp: Enable HDCP for XE Suraj Kandpal
2024-02-09 17:50   ` kernel test robot
2024-02-13 23:30   ` Daniele Ceraolo Spurio
2024-02-14  5:33     ` Kandpal, Suraj
2024-02-14 17:05       ` Daniele Ceraolo Spurio
2024-02-15  6:12   ` Suraj Kandpal
2024-02-26 11:01     ` Murthy, Arun R
2024-02-09 10:14 ` [PATCH 5/5] drm/xe/hdcp: Add intel_hdcp_gsc_message to Makefile Suraj Kandpal
2024-02-16 13:52   ` Maarten Lankhorst
2024-02-19  5:09     ` Kandpal, Suraj
2024-02-09 10:56 ` ✓ CI.Patch_applied: success for XE HDCP Enablement (rev4) Patchwork
2024-02-09 10:57 ` ✓ CI.checkpatch: " Patchwork
2024-02-09 10:58 ` ✓ CI.KUnit: " Patchwork
2024-02-09 11:08 ` ✓ CI.Build: " Patchwork
2024-02-09 11:09 ` ✗ CI.Hooks: failure " Patchwork
2024-02-09 11:10 ` ✗ CI.checksparse: warning " Patchwork
2024-02-09 11:54 ` ✗ CI.BAT: failure " Patchwork
2024-02-15  6:17 ` ✓ CI.Patch_applied: success for XE HDCP Enablement (rev5) Patchwork
2024-02-15  6:18 ` ✓ CI.checkpatch: " Patchwork
2024-02-15  6:19 ` ✓ CI.KUnit: " Patchwork
2024-02-15  6:29 ` ✓ CI.Build: " Patchwork
2024-02-15  6:29 ` ✗ CI.Hooks: failure " Patchwork
2024-02-15  6:31 ` ✗ CI.checksparse: warning " Patchwork
2024-02-15  7:02 ` ✓ CI.BAT: success " 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=863431e0-1897-4d58-8bca-866b8c90cc54@intel.com \
    --to=daniele.ceraolospurio@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=suraj.kandpal@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