From: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Cc: mitulkumar.ajitkumar.golani@intel.com,
ankit.k.nautiyal@intel.com, suraj.kandpal@intel.com,
jani.nikula@linux.intel.com, rodrigo.vivi@intel.com,
sfr@canb.auug.org.au
Subject: [PATCH 0/3] CMRR patch fixes
Date: Wed, 12 Jun 2024 15:24:30 +0530 [thread overview]
Message-ID: <20240612095433.323342-1-mitulkumar.ajitkumar.golani@intel.com> (raw)
Address following issues regarding CMRR
1. Describe target_rr_divider in struct drm_dp_as_sdp.
2. Compute vrr_vsync params when vrr.enable is set.
3. Use required macro to avoid overflow.
Mitul Golani (3):
drm/dp: Describe target_rr_divider in struct drm_dp_as_sdp
drm/i915/display: Send vrr vsync params whne vrr is enabled
drm/i915/display: Update calculation to avoid any overflow
drivers/gpu/drm/i915/display/intel_vrr.c | 12 +++++++-----
include/drm/display/drm_dp_helper.h | 1 +
2 files changed, 8 insertions(+), 5 deletions(-)
--
2.45.2
next reply other threads:[~2024-06-12 9:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 9:54 Mitul Golani [this message]
2024-06-12 9:54 ` [PATCH 1/3] drm/dp: Describe target_rr_divider in struct drm_dp_as_sdp Mitul Golani
2024-06-12 10:51 ` Golani, Mitulkumar Ajitkumar
2024-06-12 12:21 ` Nautiyal, Ankit K
2024-06-12 9:54 ` [PATCH 2/3] drm/i915/display: Send vrr vsync params whne vrr is enabled Mitul Golani
2024-06-12 9:54 ` [PATCH 3/3] drm/i915/display: Update calculation to avoid overflow Mitul Golani
2024-06-12 12:22 ` Nautiyal, Ankit K
2024-06-12 9:59 ` ✓ CI.Patch_applied: success for CMRR patch fixes Patchwork
2024-06-12 9:59 ` ✓ CI.checkpatch: " Patchwork
2024-06-12 10:00 ` ✓ CI.KUnit: " Patchwork
2024-06-12 10:12 ` ✓ CI.Build: " Patchwork
2024-06-12 10:14 ` ✓ CI.Hooks: " Patchwork
2024-06-12 10:16 ` ✗ CI.checksparse: warning " Patchwork
2024-06-12 10:38 ` ✓ CI.BAT: success " Patchwork
2024-06-12 12:21 ` ✗ 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=20240612095433.323342-1-mitulkumar.ajitkumar.golani@intel.com \
--to=mitulkumar.ajitkumar.golani@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=sfr@canb.auug.org.au \
--cc=suraj.kandpal@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