From: Gustavo Sousa <gustavo.sousa@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [PATCH 0/1] Remove redundant call to intel_init_display_hooks()
Date: Fri, 8 Sep 2023 15:49:27 -0300 [thread overview]
Message-ID: <20230908184928.65815-1-gustavo.sousa@intel.com> (raw)
In Xe initialization path, the function intel_init_display_hooks() is
being called twice, which is redundant. To remove redundancy, let's
remove one of the calls.
That function sets up hooks that are called from: (i) later in the
initialization path (i.e. intel_display_driver_probe_nogem()), (ii)
resume, or (iii) mode set commits.
In both call sites, none of the scenarios above are reached yet, so it
would be safe to remove the redundant call from either of the two.
However, since intel_display_driver_early_probe() is shared by both i915
and Xe, prefer to remove the call done from xe_display_init_nommio().
Gustavo Sousa (1):
fixup! drm/xe/display: Implement display support
drivers/gpu/drm/xe/xe_display.c | 2 --
1 file changed, 2 deletions(-)
--
2.41.0
next reply other threads:[~2023-09-08 18:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 18:49 Gustavo Sousa [this message]
2023-09-08 18:49 ` [Intel-xe] [PATCH 1/1] fixup! drm/xe/display: Implement display support Gustavo Sousa
2023-09-21 6:50 ` Balasubramani Vivekanandan
2023-09-08 19:10 ` [Intel-xe] ✓ CI.Patch_applied: success for Remove redundant call to intel_init_display_hooks() Patchwork
2023-09-08 19:11 ` [Intel-xe] ✓ CI.checkpatch: " Patchwork
2023-09-08 19:12 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-09-08 19:19 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-08 19:19 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-08 19:20 ` [Intel-xe] ✓ CI.checksparse: " Patchwork
2023-09-08 19:52 ` [Intel-xe] ✓ CI.BAT: " Patchwork
2023-09-21 12:34 ` Gustavo Sousa
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=20230908184928.65815-1-gustavo.sousa@intel.com \
--to=gustavo.sousa@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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