From: Nirmoy Das <nirmoy.das@linux.intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
intel-xe@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v3 4/5] drm/xe: Combine common force-wake code into helpers
Date: Wed, 12 Jun 2024 12:14:54 +0200 [thread overview]
Message-ID: <cf7a8224-b83c-43fb-b59b-3c74a22b98bf@linux.intel.com> (raw)
In-Reply-To: <20240611163537.1944-5-michal.wajdeczko@intel.com>
On 6/11/2024 6:35 PM, Michal Wajdeczko wrote:
> The code of 'control' and 'wait' force-wake operations are very
> similar for both 'wake' and 'sleep' cases. Add helpers to maximize
> code reuse.
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
> ---
> v2: rename str_wake_sleep helper param (Rodrigo)
> drop inline from str_wake_sleep helper (Michal)
> ---
> drivers/gpu/drm/xe/xe_force_wake.c | 54 +++++++++++++++++-------------
> 1 file changed, 30 insertions(+), 24 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_force_wake.c b/drivers/gpu/drm/xe/xe_force_wake.c
> index afbca81c12dd..468aabd72d6b 100644
> --- a/drivers/gpu/drm/xe/xe_force_wake.c
> +++ b/drivers/gpu/drm/xe/xe_force_wake.c
> @@ -15,6 +15,11 @@
>
> #define XE_FORCE_WAKE_ACK_TIMEOUT_MS 50
>
> +static const char *str_wake_sleep(bool wake)
> +{
> + return wake ? "wake" : "sleep";
> +}
> +
> static void domain_init(struct xe_force_wake_domain *domain,
> enum xe_force_wake_domain_id id,
> struct xe_reg reg, struct xe_reg ack)
> @@ -89,46 +94,47 @@ void xe_force_wake_init_engines(struct xe_gt *gt, struct xe_force_wake *fw)
> FORCEWAKE_ACK_GSC);
> }
>
> +static void __domain_ctl(struct xe_gt *gt, struct xe_force_wake_domain *domain, bool wake)
> +{
> + xe_mmio_write32(gt, domain->reg_ctl, domain->mask | (wake ? domain->val : 0));
> +}
> +
> +static int __domain_wait(struct xe_gt *gt, struct xe_force_wake_domain *domain, bool wake)
> +{
> + u32 value;
> + int ret;
> +
> + ret = xe_mmio_wait32(gt, domain->reg_ack, domain->val, wake ? domain->val : 0,
> + XE_FORCE_WAKE_ACK_TIMEOUT_MS * USEC_PER_MSEC,
> + &value, true);
> + if (ret)
> + xe_gt_notice(gt, "Force wake domain %d failed to ack %s (%pe) reg[%#x] = %#x\n",
> + domain->id, str_wake_sleep(wake), ERR_PTR(ret),
> + domain->reg_ack.addr, value);
> +
> + return ret;
> +}
> +
> static void domain_wake(struct xe_gt *gt, struct xe_force_wake_domain *domain)
> {
> - xe_mmio_write32(gt, domain->reg_ctl, domain->mask | domain->val);
> + __domain_ctl(gt, domain, true);
> }
>
> static int domain_wake_wait(struct xe_gt *gt,
> struct xe_force_wake_domain *domain)
> {
> - u32 value;
> - int ret;
> -
> - ret = xe_mmio_wait32(gt, domain->reg_ack, domain->val, domain->val,
> - XE_FORCE_WAKE_ACK_TIMEOUT_MS * USEC_PER_MSEC,
> - &value, true);
> - if (ret)
> - xe_gt_notice(gt, "Force wake domain %d failed to ack wake (%pe) reg[%#x] = %#x\n",
> - domain->id, ERR_PTR(ret), domain->reg_ack.addr, value);
> -
> - return ret;
> + return __domain_wait(gt, domain, true);
> }
>
> static void domain_sleep(struct xe_gt *gt, struct xe_force_wake_domain *domain)
> {
> - xe_mmio_write32(gt, domain->reg_ctl, domain->mask);
> + __domain_ctl(gt, domain, false);
> }
>
> static int domain_sleep_wait(struct xe_gt *gt,
> struct xe_force_wake_domain *domain)
> {
> - u32 value;
> - int ret;
> -
> - ret = xe_mmio_wait32(gt, domain->reg_ack, domain->val, 0,
> - XE_FORCE_WAKE_ACK_TIMEOUT_MS * USEC_PER_MSEC,
> - &value, true);
> - if (ret)
> - xe_gt_notice(gt, "Force wake domain %d failed to ack sleep (%pe) reg[%#x] = %#x\n",
> - domain->id, ERR_PTR(ret), domain->reg_ack.addr, value);
> -
> - return ret;
> + return __domain_wait(gt, domain, false);
> }
>
> #define for_each_fw_domain_masked(domain__, mask__, fw__, tmp__) \
next prev parent reply other threads:[~2024-06-12 10:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 16:35 [PATCH v3 0/5] Prepare Xe force-wake code for VFs Michal Wajdeczko
2024-06-11 16:35 ` [PATCH v3 1/5] drm/xe: Prefer GT oriented messages in xe_force_wake.c Michal Wajdeczko
2024-06-12 10:11 ` Nirmoy Das
2024-06-11 16:35 ` [PATCH v3 2/5] drm/xe: Kill fw_to_gt() helper Michal Wajdeczko
2024-06-11 16:41 ` Francois Dugast
2024-06-12 10:12 ` Nirmoy Das
2024-06-11 16:35 ` [PATCH v3 3/5] drm/xe: Include additional info on failed force-wake operation Michal Wajdeczko
2024-06-11 17:04 ` Rodrigo Vivi
2024-06-12 10:13 ` Nirmoy Das
2024-06-11 16:35 ` [PATCH v3 4/5] drm/xe: Combine common force-wake code into helpers Michal Wajdeczko
2024-06-12 10:14 ` Nirmoy Das [this message]
2024-06-11 16:35 ` [PATCH v3 5/5] drm/xe/vf: Ignore force-wake requests if VF Michal Wajdeczko
2024-06-12 10:15 ` Nirmoy Das
2024-06-11 17:36 ` ✓ CI.Patch_applied: success for Prepare Xe force-wake code for VFs (rev4) Patchwork
2024-06-11 17:36 ` ✓ CI.checkpatch: " Patchwork
2024-06-11 17:37 ` ✓ CI.KUnit: " Patchwork
2024-06-11 17:49 ` ✓ CI.Build: " Patchwork
2024-06-11 17:51 ` ✗ CI.Hooks: failure " Patchwork
2024-06-11 17:53 ` ✓ CI.checksparse: success " Patchwork
2024-06-11 18:34 ` ✓ CI.BAT: " Patchwork
2024-06-11 22:27 ` ✗ CI.FULL: failure " Patchwork
2024-06-12 9:54 ` Michal Wajdeczko
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=cf7a8224-b83c-43fb-b59b-3c74a22b98bf@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.wajdeczko@intel.com \
--cc=rodrigo.vivi@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