From: Jani Nikula <jani.nikula@linux.intel.com>
To: Nemesa Garg <nemesa.garg@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Cc: Nemesa Garg <nemesa.garg@intel.com>, uma.shankar@intel.com
Subject: Re: [PATCH 00/10] Introduce drm sharpness property
Date: Fri, 19 Sep 2025 14:55:59 +0300 [thread overview]
Message-ID: <0f35ace53cf269b68fb3adc425680aac8cf10fb6@intel.com> (raw)
In-Reply-To: <20250807092841.3169436-1-nemesa.garg@intel.com>
On Thu, 07 Aug 2025, Nemesa Garg <nemesa.garg@intel.com> 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.
I was planning on merging this, but AFAICT this is the newest
submission. Basically the CI results are 1½ months old, and I'd prefer
newer.
Also need to figure out which route to merge, drm-misc or drm-intel.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-09-19 11:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 9:28 [PATCH 00/10] Introduce drm sharpness property Nemesa Garg
2025-08-07 9:28 ` [PATCH 01/10] drm/drm_crtc: Introduce sharpness strength property Nemesa Garg
2025-08-18 6:06 ` G M, Adarsh
2025-08-07 9:28 ` [PATCH 02/10] drm/i915/display: Introduce HAS_CASF for sharpness support Nemesa Garg
2025-08-07 9:28 ` [PATCH 03/10] drm/i915/display: Add strength and winsize register Nemesa Garg
2025-08-07 9:28 ` [PATCH 04/10] drm/i915/display: Add filter lut values Nemesa Garg
2025-08-07 9:28 ` [PATCH 05/10] drm/i915/display: Compute the scaler coefficients Nemesa Garg
2025-08-07 9:28 ` [PATCH 06/10] drm/i915/display: Add and compute scaler parameter Nemesa Garg
2025-08-07 9:28 ` [PATCH 07/10] drm/i915/display: Configure the second scaler Nemesa Garg
2025-08-07 9:28 ` [PATCH 08/10] drm/i915/display: Set and get the casf config Nemesa Garg
2025-08-07 9:28 ` [PATCH 09/10] drm/i915/display: Enable/disable casf Nemesa Garg
2025-08-07 9:28 ` [PATCH 10/10] drm/i915/display: Expose sharpness strength property Nemesa Garg
2025-08-07 11:11 ` ✓ i915.CI.BAT: success for Introduce drm sharpness property (rev16) Patchwork
2025-08-07 15:11 ` ✓ i915.CI.Full: " Patchwork
2025-09-09 8:10 ` [PATCH 00/10] Introduce drm sharpness property Jani Nikula
2025-09-09 8:39 ` Jani Nikula
2025-09-09 8:44 ` Garg, Nemesa
2025-09-19 11:55 ` Jani Nikula [this message]
2025-09-19 13:01 ` Garg, Nemesa
-- strict thread matches above, loose matches on Subject: below --
2025-10-26 17:26 Nemesa Garg
2025-10-01 6:34 Nemesa Garg
2025-10-09 11:02 ` Nautiyal, Ankit K
2025-09-26 11:37 Nemesa Garg
2025-09-19 14:34 Nemesa Garg
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=0f35ace53cf269b68fb3adc425680aac8cf10fb6@intel.com \
--to=jani.nikula@linux.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 \
--cc=uma.shankar@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