From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH 0/4] drm/i915: struct intel_display conversions
Date: Wed, 31 Jul 2024 19:44:32 +0300 [thread overview]
Message-ID: <cover.1722444150.git.jani.nikula@intel.com> (raw)
Convert some display files to struct intel_display. Some parts are
scripted, but my cocci is not quite there yet to change interfaces, so a
lot of this is still manual.q
Some stragglers are left behind, but struct intel_display is preferred
and i915 pointers are derived locally as needed.
BR,
Jani.
Jani Nikula (4):
drm/i915/acpi: convert to struct intel_display
drm/i915/opregion: unify intel_encoder/intel_connector naming
drm/i915/opregion: convert to struct intel_display
drm/i915/bios: convert to struct intel_display
drivers/gpu/drm/i915/display/g4x_dp.c | 3 +-
drivers/gpu/drm/i915/display/g4x_hdmi.c | 3 +-
drivers/gpu/drm/i915/display/icl_dsi.c | 3 +-
drivers/gpu/drm/i915/display/intel_acpi.c | 17 +-
drivers/gpu/drm/i915/display/intel_acpi.h | 18 +-
drivers/gpu/drm/i915/display/intel_bios.c | 846 +++++++++---------
drivers/gpu/drm/i915/display/intel_bios.h | 28 +-
.../gpu/drm/i915/display/intel_combo_phy.c | 8 +-
drivers/gpu/drm/i915/display/intel_ddi.c | 3 +-
drivers/gpu/drm/i915/display/intel_ddi.h | 3 +-
drivers/gpu/drm/i915/display/intel_display.c | 9 +-
.../drm/i915/display/intel_display_debugfs.c | 7 +-
.../drm/i915/display/intel_display_device.c | 8 +-
.../drm/i915/display/intel_display_driver.c | 22 +-
.../gpu/drm/i915/display/intel_display_irq.c | 27 +-
drivers/gpu/drm/i915/display/intel_dp.c | 8 +-
drivers/gpu/drm/i915/display/intel_lvds.c | 5 +-
drivers/gpu/drm/i915/display/intel_opregion.c | 320 +++----
drivers/gpu/drm/i915/display/intel_opregion.h | 58 +-
drivers/gpu/drm/i915/display/intel_sdvo.c | 3 +-
drivers/gpu/drm/i915/display/intel_tv.c | 3 +-
drivers/gpu/drm/i915/display/vlv_dsi.c | 5 +-
drivers/gpu/drm/i915/i915_driver.c | 22 +-
drivers/gpu/drm/xe/display/xe_display.c | 19 +-
24 files changed, 763 insertions(+), 685 deletions(-)
--
2.39.2
next reply other threads:[~2024-07-31 16:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 16:44 Jani Nikula [this message]
2024-07-31 16:44 ` [PATCH 1/4] drm/i915/acpi: convert to struct intel_display Jani Nikula
2024-08-06 13:51 ` Imre Deak
2024-07-31 16:44 ` [PATCH 2/4] drm/i915/opregion: unify intel_encoder/intel_connector naming Jani Nikula
2024-08-06 13:53 ` Imre Deak
2024-07-31 16:44 ` [PATCH 3/4] drm/i915/opregion: convert to struct intel_display Jani Nikula
2024-08-02 10:07 ` kernel test robot
2024-08-06 14:37 ` Imre Deak
2024-07-31 16:44 ` [PATCH 4/4] drm/i915/bios: " Jani Nikula
2024-08-06 15:23 ` Imre Deak
2024-07-31 17:38 ` ✓ CI.Patch_applied: success for drm/i915: struct intel_display conversions Patchwork
2024-07-31 17:38 ` ✓ CI.checkpatch: " Patchwork
2024-07-31 17:40 ` ✓ CI.KUnit: " Patchwork
2024-07-31 17:51 ` ✓ CI.Build: " Patchwork
2024-07-31 17:54 ` ✓ CI.Hooks: " Patchwork
2024-07-31 17:55 ` ✗ CI.checksparse: warning " Patchwork
2024-07-31 18:14 ` ✓ CI.BAT: success " Patchwork
2024-07-31 21:43 ` ✗ CI.FULL: failure " 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=cover.1722444150.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--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;
as well as URLs for NNTP newsgroup(s).