From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 13/22] drm/i915/guc: New GuC interrupt register for Gen11
Date: Fri, 12 Apr 2019 18:28:29 -0700 [thread overview]
Message-ID: <85185bcf-9d60-337e-4685-a546def6f34c@intel.com> (raw)
In-Reply-To: <20190411084436.24384-14-michal.wajdeczko@intel.com>
On 4/11/19 1:44 AM, Michal Wajdeczko wrote:
> Gen11 defines new more flexible Host-to-GuC interrupt register.
> Now the host can write any 32-bit payload to trigger an interrupt
> and GuC can additionally read this payload from the register.
> Current GuC firmware ignores the payload so we just write 0.
>
> Bspec: 21043
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
matches the specs.
Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
As a possible simplification, instead of using a function pointer we
could also just save the interrupt register in guc->send_regs and always
use GUC_SEND_TRIGGER (the gen11 payload is ignored anyway), or save the
trigger/payload value as well.
Daniele
> ---
> drivers/gpu/drm/i915/intel_guc.c | 14 +++++++++++++-
> drivers/gpu/drm/i915/intel_guc_reg.h | 1 +
> 2 files changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_guc.c b/drivers/gpu/drm/i915/intel_guc.c
> index 483c7019f817..5bc9bc7c956a 100644
> --- a/drivers/gpu/drm/i915/intel_guc.c
> +++ b/drivers/gpu/drm/i915/intel_guc.c
> @@ -34,6 +34,13 @@ static void gen8_guc_raise_irq(struct intel_guc *guc)
> I915_WRITE(GUC_SEND_INTERRUPT, GUC_SEND_TRIGGER);
> }
>
> +static void gen11_guc_raise_irq(struct intel_guc *guc)
> +{
> + struct drm_i915_private *dev_priv = guc_to_i915(guc);
> +
> + I915_WRITE(GEN11_GUC_HOST_INTERRUPT, 0);
> +}
> +
> static inline i915_reg_t guc_send_reg(struct intel_guc *guc, u32 i)
> {
> GEM_BUG_ON(!guc->send_regs.base);
> @@ -63,6 +70,8 @@ void intel_guc_init_send_regs(struct intel_guc *guc)
>
> void intel_guc_init_early(struct intel_guc *guc)
> {
> + struct drm_i915_private *i915 = guc_to_i915(guc);
> +
> intel_guc_fw_init_early(guc);
> intel_guc_ct_init_early(&guc->ct);
> intel_guc_log_init_early(&guc->log);
> @@ -71,7 +80,10 @@ void intel_guc_init_early(struct intel_guc *guc)
> spin_lock_init(&guc->irq_lock);
> guc->send = intel_guc_send_nop;
> guc->handler = intel_guc_to_host_event_handler_nop;
> - guc->notify = gen8_guc_raise_irq;
> + if (INTEL_GEN(i915) >= 11)
> + guc->notify = gen11_guc_raise_irq;
> + else
> + guc->notify = gen8_guc_raise_irq;
> }
>
> static int guc_init_wq(struct intel_guc *guc)
> diff --git a/drivers/gpu/drm/i915/intel_guc_reg.h b/drivers/gpu/drm/i915/intel_guc_reg.h
> index 57e7ad522c2f..aec02eddbaed 100644
> --- a/drivers/gpu/drm/i915/intel_guc_reg.h
> +++ b/drivers/gpu/drm/i915/intel_guc_reg.h
> @@ -103,6 +103,7 @@
>
> #define GUC_SEND_INTERRUPT _MMIO(0xc4c8)
> #define GUC_SEND_TRIGGER (1<<0)
> +#define GEN11_GUC_HOST_INTERRUPT _MMIO(0x1901f0)
>
> #define GUC_NUM_DOORBELLS 256
>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-04-13 1:28 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 8:44 [PATCH v2 00/22] GuC 32.0.3 Michal Wajdeczko
2019-04-11 8:44 ` [PATCH v2 01/22] drm/i915/guc: Change platform default GuC mode Michal Wajdeczko
2019-04-12 22:52 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 02/22] drm/i915/guc: Don't allow GuC submission Michal Wajdeczko
2019-04-15 7:37 ` Martin Peres
2019-04-11 8:44 ` [PATCH v2 03/22] drm/i915/guc: Simplify preparation of GuC parameter block Michal Wajdeczko
2019-04-15 18:27 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 04/22] drm/i915/guc: Update GuC firmware versions and names Michal Wajdeczko
2019-04-12 22:42 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 05/22] drm/i915/guc: Update GuC firmware CSS header Michal Wajdeczko
2019-04-15 20:25 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 06/22] drm/i915/guc: Update GuC boot parameters Michal Wajdeczko
2019-04-12 23:46 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 07/22] drm/i915/guc: Update GuC sleep status values Michal Wajdeczko
2019-04-13 0:06 ` Daniele Ceraolo Spurio
2019-04-13 0:24 ` Daniele Ceraolo Spurio
2019-04-15 20:21 ` John Spotswood
2019-04-13 0:20 ` [PATCH v2] drm/i915/guc: updated suspend/resume protocol Daniele Ceraolo Spurio
2019-04-16 23:16 ` John Spotswood
2019-04-11 8:44 ` [PATCH v2 08/22] drm/i915/guc: Update GuC sample-forcewake command Michal Wajdeczko
2019-04-13 0:10 ` Daniele Ceraolo Spurio
2019-04-16 23:45 ` John Spotswood
2019-04-11 8:44 ` [PATCH v2 09/22] drm/i915/guc: Update GuC ADS object definition Michal Wajdeczko
2019-04-13 1:16 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 10/22] drm/i915/guc: Always ask GuC to update power domain states Michal Wajdeczko
2019-04-15 20:46 ` Daniele Ceraolo Spurio
2019-04-16 23:26 ` John Spotswood
2019-04-11 8:44 ` [PATCH v2 11/22] drm/i915/guc: Reset GuC ADS during sanitize Michal Wajdeczko
2019-04-16 11:44 ` Lis, Tomasz
2019-04-11 8:44 ` [PATCH v2 12/22] drm/i915/guc: Treat GuC initialization failure as -EIO Michal Wajdeczko
2019-04-13 1:20 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 13/22] drm/i915/guc: New GuC interrupt register for Gen11 Michal Wajdeczko
2019-04-13 1:28 ` Daniele Ceraolo Spurio [this message]
2019-04-11 8:44 ` [PATCH v2 14/22] drm/i915/guc: New GuC scratch registers " Michal Wajdeczko
2019-04-13 1:30 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 15/22] drm/i915/huc: New HuC status register " Michal Wajdeczko
2019-04-15 21:19 ` Daniele Ceraolo Spurio
2019-04-15 21:44 ` Michal Wajdeczko
2019-04-15 22:10 ` Daniele Ceraolo Spurio
2019-04-15 22:23 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 16/22] drm/i915/guc: Create vfuncs for the GuC interrupts control functions Michal Wajdeczko
2019-04-15 17:51 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 17/22] drm/i915/guc: Correctly handle GuC interrupts on Gen11 Michal Wajdeczko
2019-04-11 8:44 ` [PATCH v2 18/22] drm/i915/guc: Update GuC CTB response definition Michal Wajdeczko
2019-04-15 17:57 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 19/22] drm/i915/guc: Enable GuC CTB communication on Gen11 Michal Wajdeczko
2019-04-11 23:58 ` Daniele Ceraolo Spurio
2019-04-11 8:44 ` [PATCH v2 20/22] drm/i915/guc: Define GuC firmware version for Icelake Michal Wajdeczko
2019-04-15 22:22 ` Srivatsa, Anusha
2019-04-11 8:44 ` [PATCH v2 21/22] drm/i915/huc: Define HuC " Michal Wajdeczko
2019-04-18 12:27 ` Ye, Tony
2019-04-11 8:44 ` [PATCH v2 22/22] HAX: prevent CI failures on configs with forced GuC submission Michal Wajdeczko
2019-04-12 11:30 ` Martin Peres
2019-04-12 11:54 ` Michal Wajdeczko
2019-04-11 19:17 ` ✗ Fi.CI.SPARSE: warning for GuC 32.0.3 (rev2) Patchwork
2019-04-11 19:37 ` ✓ Fi.CI.BAT: success " Patchwork
2019-04-11 20:24 ` [PATCH v2 00/22] GuC 32.0.3 Chris Wilson
2019-04-12 2:26 ` ✓ Fi.CI.IGT: success for GuC 32.0.3 (rev2) Patchwork
2019-04-13 0:46 ` ✗ Fi.CI.SPARSE: warning for GuC 32.0.3 (rev3) Patchwork
2019-04-13 1:09 ` ✓ Fi.CI.BAT: success " Patchwork
2019-04-13 4:33 ` ✓ Fi.CI.IGT: " 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=85185bcf-9d60-337e-4685-a546def6f34c@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.wajdeczko@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