From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH v2 rebased 4/6] drm/xe/display: Enable modular fia in TGL
Date: Mon, 10 Apr 2023 11:38:34 -0400 [thread overview]
Message-ID: <ZDQteoVKCktzyNus@intel.com> (raw)
In-Reply-To: <20230406143133.29474-4-jose.souza@intel.com>
On Thu, Apr 06, 2023 at 07:31:31AM -0700, José Roberto de Souza wrote:
> TGL is the first platform tha has it.
> Enabling it for DG1 don't cause any issues as DG1 don't have any real
> TC ports, so intel_tc_port_init() will not be called for DG1.
so, why do we need to enable then?
>
> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> ---
> drivers/gpu/drm/xe/xe_display.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_display.c b/drivers/gpu/drm/xe/xe_display.c
> index 5fab5b9fbde0c..0001a9d02495d 100644
> --- a/drivers/gpu/drm/xe/xe_display.c
> +++ b/drivers/gpu/drm/xe/xe_display.c
> @@ -486,7 +486,10 @@ void xe_display_info_init(struct xe_device *xe)
> switch (xe->info.platform) {
> case XE_TIGERLAKE:
> case XE_DG1:
> - xe->info.display = (struct xe_device_display_info) { GEN12_DISPLAY };
> + xe->info.display = (struct xe_device_display_info) {
> + GEN12_DISPLAY,
> + .has_modular_fia = 1,
> + };
> break;
> case XE_ALDERLAKE_S:
> xe->info.display = (struct xe_device_display_info) {
> --
> 2.40.0
>
next prev parent reply other threads:[~2023-04-10 15:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 14:31 [Intel-xe] [PATCH v2 rebased 1/6] drm/i915: Nuke unused dsparb_lock José Roberto de Souza
2023-04-06 14:31 ` [Intel-xe] [PATCH v2 rebased 2/6] drm/i915: Initialize dkl_phy spin lock from display code path José Roberto de Souza
2023-04-10 15:33 ` [Intel-xe] [Intel-gfx] " Rodrigo Vivi
2023-04-10 17:07 ` Souza, Jose
2023-04-10 17:20 ` Rodrigo Vivi
2023-04-06 14:31 ` [Intel-xe] [PATCH v2 rebased 3/6] drm/i915: Only initialize dlk phy lock in display 12 and newer José Roberto de Souza
2023-04-10 15:37 ` Rodrigo Vivi
2023-04-10 17:10 ` Souza, Jose
2023-04-10 17:19 ` Rodrigo Vivi
2023-04-06 14:31 ` [Intel-xe] [PATCH v2 rebased 4/6] drm/xe/display: Enable modular fia in TGL José Roberto de Souza
2023-04-10 15:38 ` Rodrigo Vivi [this message]
2023-04-10 16:24 ` Souza, Jose
2023-04-10 16:50 ` Rodrigo Vivi
2023-04-10 17:15 ` Souza, Jose
2023-04-10 17:20 ` Rodrigo Vivi
2023-04-10 17:29 ` Souza, Jose
2023-04-10 17:30 ` Vivi, Rodrigo
2023-04-06 14:31 ` [Intel-xe] [PATCH v2 rebased 5/6] drm/xe/display: Disable PSR HW tracking for DG2 and MTL José Roberto de Souza
2023-04-10 15:43 ` Rodrigo Vivi
2023-04-06 14:31 ` [Intel-xe] [PATCH v2 rebased 6/6] drm/xe: Enable Raptorlake-P José Roberto de Souza
2023-04-10 15:44 ` Rodrigo Vivi
2023-04-06 14:36 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [v2,rebased,1/6] drm/i915: Nuke unused dsparb_lock Patchwork
2023-04-06 14:37 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-04-06 14:41 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-04-06 20:38 ` [Intel-xe] [PATCH v2 rebased 1/6] " Rodrigo Vivi
2023-04-10 14:43 ` Souza, Jose
2023-04-10 15:26 ` Rodrigo Vivi
2023-04-10 15:45 ` Rodrigo Vivi
2023-04-10 15:46 ` [Intel-xe] ✗ CI.Patch_applied: failure for series starting with [v2,rebased,1/6] drm/i915: Nuke unused dsparb_lock (rev2) 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=ZDQteoVKCktzyNus@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jose.souza@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