From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Alexander Usyskin <alexander.usyskin@intel.com>
Cc: David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>,
Tomas Winkler <tomas.winkler@intel.com>,
Vitaly Lubart <vitaly.lubart@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gsc: Only initialize GSC in tile 0
Date: Mon, 31 Oct 2022 05:35:34 -0400 [thread overview]
Message-ID: <Y1+W5ipudusyL0NB@intel.com> (raw)
In-Reply-To: <20221031055117.1043830-1-alexander.usyskin@intel.com>
On Mon, Oct 31, 2022 at 07:51:17AM +0200, Alexander Usyskin wrote:
> From: José Roberto de Souza <jose.souza@intel.com>
>
> For multi-tile setups the GSC operational only on the tile 0.
> Skip GSC auxiliary device creation for all other tiles.
>
> Cc: Tomas Winkler <tomas.winkler@intel.com>
> Cc: Vitaly Lubart <vitaly.lubart@intel.com>
> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_gt.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_gt.c b/drivers/gpu/drm/i915/gt/intel_gt.c
> index 2e796ffad911..92ad8cd45ddb 100644
> --- a/drivers/gpu/drm/i915/gt/intel_gt.c
> +++ b/drivers/gpu/drm/i915/gt/intel_gt.c
> @@ -456,7 +456,10 @@ void intel_gt_chipset_flush(struct intel_gt *gt)
>
> void intel_gt_driver_register(struct intel_gt *gt)
> {
> - intel_gsc_init(>->gsc, gt->i915);
> + if (gt->info.id == 0)
> + intel_gsc_init(>->gsc, gt->i915);
> + else
> + drm_dbg(>->i915->drm, "Not initializing gsc for remote tiles\n");
It looks to me that we need to move the gsc out of the intel_gt
instead of workaround the initialization.
>
> intel_rps_driver_register(>->rps);
>
> @@ -787,7 +790,8 @@ void intel_gt_driver_unregister(struct intel_gt *gt)
>
> intel_gt_sysfs_unregister(gt);
> intel_rps_driver_unregister(>->rps);
> - intel_gsc_fini(>->gsc);
> + if (gt->info.id == 0)
> + intel_gsc_fini(>->gsc);
>
> intel_pxp_fini(>->pxp);
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-10-31 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 5:51 [Intel-gfx] [PATCH] drm/i915/gsc: Only initialize GSC in tile 0 Alexander Usyskin
2022-10-31 6:55 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2022-10-31 9:35 ` Rodrigo Vivi [this message]
2022-10-31 9:48 ` [Intel-gfx] [PATCH] " Winkler, Tomas
2022-10-31 10:15 ` Rodrigo Vivi
2022-11-09 14:56 ` Usyskin, Alexander
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=Y1+W5ipudusyL0NB@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@linux.ie \
--cc=alexander.usyskin@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tomas.winkler@intel.com \
--cc=vitaly.lubart@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.