Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Suraj Kandpal <suraj.kandpal@intel.com>
To: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: ankit.k.nautiyal@intel.com, chaitanya.kumar.borah@intel.com,
	dnyaneshwar.bhadane@intel.com,
	Suraj Kandpal <suraj.kandpal@intel.com>
Subject: [PATCH 0/2] Clean and Optimise mtl_ddi_prepare_link_retrain
Date: Fri,  3 Jan 2025 10:47:03 +0530	[thread overview]
Message-ID: <20250103051705.145161-1-suraj.kandpal@intel.com> (raw)

While going through code of mtl_ddi_prepare_link_retrain which calls
mtl_port_buf_ctl_program I saw some potential cleanup and optimization
that could take place i.e the i915 to intel_display usage and using
intel_de_rmw instead of the intel_de_read, add mask and then
intel_de_write sequence. This patch series implements them.

Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>

Suraj Kandpal (2):
  drm/i915/dp: Use intel_display instead of drm_i915_private
  drm/i915/ddi: Optimize mtl_port_buf_ctl_program

 drivers/gpu/drm/i915/display/intel_ddi.c | 25 ++++++++++++------------
 1 file changed, 12 insertions(+), 13 deletions(-)

-- 
2.34.1


             reply	other threads:[~2025-01-03  5:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-03  5:17 Suraj Kandpal [this message]
2025-01-03  5:17 ` [PATCH 1/2] drm/i915/dp: Use intel_display instead of drm_i915_private Suraj Kandpal
2025-01-03 10:08   ` Jani Nikula
2025-01-03  5:17 ` [PATCH 2/2] drm/i915/ddi: Optimize mtl_port_buf_ctl_program Suraj Kandpal
2025-01-03 10:08   ` Jani Nikula
2025-01-03  6:21 ` ✓ CI.Patch_applied: success for Clean and Optimise mtl_ddi_prepare_link_retrain Patchwork
2025-01-03  6:21 ` ✓ CI.checkpatch: " Patchwork
2025-01-03  6:23 ` ✓ CI.KUnit: " Patchwork
2025-01-03  6:41 ` ✓ CI.Build: " Patchwork
2025-01-03  6:43 ` ✓ CI.Hooks: " Patchwork
2025-01-03  6:45 ` ✓ CI.checksparse: " Patchwork
2025-01-03  7:17 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-01-03  8:50 ` ✗ Xe.CI.Full: " 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=20250103051705.145161-1-suraj.kandpal@intel.com \
    --to=suraj.kandpal@intel.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=chaitanya.kumar.borah@intel.com \
    --cc=dnyaneshwar.bhadane@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