From: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>
To: Nemesa Garg <nemesa.garg@intel.com>,
<intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 00/10] Introduce drm sharpness property
Date: Thu, 9 Oct 2025 16:32:08 +0530 [thread overview]
Message-ID: <ca305187-6683-4ed5-8be8-a15df9f9a49c@intel.com> (raw)
In-Reply-To: <20251001063500.1259687-1-nemesa.garg@intel.com>
On 10/1/2025 12:04 PM, Nemesa Garg wrote:
> Many a times images are blurred or upscaled content is also not as
> crisp as original rendered image. Traditional sharpening techniques often
> apply a uniform level of enhancement across entire image, which sometimes
> result in over-sharpening of some areas and potential loss of natural details.
>
> Intel has come up with Display Engine based adaptive sharpening filter
> with minimal power and performance impact. From LNL onwards, the Display
> hardware can use one of the pipe scaler for adaptive sharpness filter.
> This can be used for both gaming and non-gaming use cases like photos,
> image viewing. It works on a region of pixels depending on the tap size.
>
> This is an attempt to introduce an adaptive sharpness solution which
> helps in improving the image quality. For this new CRTC property is added.
> The user can set this property with desired sharpness strength value with
> 0-255. A value of 1 representing minimum sharpening strength and 255
> representing maximum sharpness strength. A strength value of 0 means no
> sharpening or sharpening feature disabled.
> It works on a region of pixels depending on the tap size. The coefficients
> are used to generate an alpha value which is used to blend the sharpened
> image to original image.
>
> Middleware MR link: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3665
> IGT patchwork link: https://patchwork.freedesktop.org/series/130218/
>
> Continuing discussions from: https://patchwork.freedesktop.org/series/129888/
>
> https://invent.kde.org/plasma/kwin/-/merge_requests/7689
> Got ack from kwin maintainer on the UAPI patch.
>
> Minor changes in patch 3, 4 and 5 hence require rb.
>
> Nemesa Garg (10):
> drm/drm_crtc: Introduce sharpness strength property
> drm/i915/display: Introduce HAS_CASF for sharpness support
> drm/i915/display: Add CASF strength and winsize
> drm/i915/display: Add filter lut values
> drm/i915/display: Compute the scaler coefficients
> drm/i915/display: Add and compute scaler parameter
> drm/i915/display: Configure the second scaler
> drm/i915/display: Set and get the casf config
> drm/i915/display: Enable/disable casf
> drm/i915/display: Expose sharpness strength property
Overall series LGTM.
Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>
> drivers/gpu/drm/drm_atomic_uapi.c | 4 +
> drivers/gpu/drm/drm_crtc.c | 35 +++
> drivers/gpu/drm/i915/Makefile | 1 +
> drivers/gpu/drm/i915/display/intel_casf.c | 293 ++++++++++++++++++
> drivers/gpu/drm/i915/display/intel_casf.h | 22 ++
> .../gpu/drm/i915/display/intel_casf_regs.h | 33 ++
> drivers/gpu/drm/i915/display/intel_crtc.c | 3 +
> .../drm/i915/display/intel_crtc_state_dump.c | 5 +
> drivers/gpu/drm/i915/display/intel_display.c | 37 ++-
> .../drm/i915/display/intel_display_device.h | 1 +
> .../drm/i915/display/intel_display_types.h | 15 +
> drivers/gpu/drm/i915/display/skl_scaler.c | 91 +++++-
> drivers/gpu/drm/i915/display/skl_scaler.h | 2 +
> drivers/gpu/drm/xe/Makefile | 1 +
> include/drm/drm_crtc.h | 18 ++
> 15 files changed, 548 insertions(+), 13 deletions(-)
> create mode 100644 drivers/gpu/drm/i915/display/intel_casf.c
> create mode 100644 drivers/gpu/drm/i915/display/intel_casf.h
> create mode 100644 drivers/gpu/drm/i915/display/intel_casf_regs.h
>
next prev parent reply other threads:[~2025-10-09 11:02 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 6:34 [PATCH 00/10] Introduce drm sharpness property Nemesa Garg
2025-10-01 6:34 ` [PATCH 01/10] drm/drm_crtc: Introduce sharpness strength property Nemesa Garg
2025-10-04 10:08 ` Dmitry Baryshkov
2025-10-08 7:22 ` Garg, Nemesa
2025-10-08 20:05 ` Dmitry Baryshkov
2025-10-09 11:00 ` Nautiyal, Ankit K
2025-10-01 6:34 ` [PATCH 02/10] drm/i915/display: Introduce HAS_CASF for sharpness support Nemesa Garg
2025-10-01 6:34 ` [PATCH 03/10] drm/i915/display: Add CASF strength and winsize Nemesa Garg
2025-10-09 10:51 ` Nautiyal, Ankit K
2025-10-01 6:34 ` [PATCH 04/10] drm/i915/display: Add filter lut values Nemesa Garg
2025-10-09 10:51 ` Nautiyal, Ankit K
2025-10-01 6:34 ` [PATCH 05/10] drm/i915/display: Compute the scaler coefficients Nemesa Garg
2025-10-09 10:52 ` Nautiyal, Ankit K
2025-10-01 6:34 ` [PATCH 06/10] drm/i915/display: Add and compute scaler parameter Nemesa Garg
2025-10-01 6:34 ` [PATCH 07/10] drm/i915/display: Configure the second scaler Nemesa Garg
2025-10-01 6:34 ` [PATCH 08/10] drm/i915/display: Set and get the casf config Nemesa Garg
2025-10-01 6:34 ` [PATCH 09/10] drm/i915/display: Enable/disable casf Nemesa Garg
2025-10-01 6:35 ` [PATCH 10/10] drm/i915/display: Expose sharpness strength property Nemesa Garg
2025-10-01 9:30 ` ✓ i915.CI.BAT: success for Introduce drm sharpness property (rev19) Patchwork
2025-10-09 11:02 ` Nautiyal, Ankit K [this message]
2025-10-10 9:47 ` ✓ i915.CI.BAT: success for Introduce drm sharpness property (rev20) Patchwork
2025-10-12 16:06 ` ✗ i915.CI.Full: failure " Patchwork
2025-10-13 12:08 ` ✓ i915.CI.Full: success " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-10-26 17:26 [PATCH 00/10] Introduce drm sharpness property Nemesa Garg
2025-09-26 11:37 Nemesa Garg
2025-09-19 14:34 Nemesa Garg
2025-08-07 9:28 Nemesa Garg
2025-09-09 8:10 ` Jani Nikula
2025-09-09 8:39 ` Jani Nikula
2025-09-09 8:44 ` Garg, Nemesa
2025-09-19 11:55 ` Jani Nikula
2025-09-19 13:01 ` Garg, Nemesa
2025-07-24 13:45 Nemesa Garg
2025-07-28 11:42 ` Garg, Nemesa
2025-05-19 12:26 Nemesa Garg
2025-07-23 15:25 ` Xaver Hugl
2025-07-24 13:59 ` Garg, Nemesa
2025-08-11 10:23 ` Shankar, Uma
2025-04-08 10:24 Nemesa Garg
2025-04-02 12:56 Nemesa Garg
2025-03-04 10:28 Nemesa Garg
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=ca305187-6683-4ed5-8be8-a15df9f9a49c@intel.com \
--to=ankit.k.nautiyal@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=nemesa.garg@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