From: Shashank Sharma <shashank.sharma@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [RFC 0/2] Enable Nearest-neighbor for Integer mode scaling
Date: Tue, 3 Sep 2019 22:22:25 +0530 [thread overview]
Message-ID: <20190903165227.6056-1-shashank.sharma@intel.com> (raw)
Blurry outputs during upscaling the buffer, is a generic problem of gfx
industry. One of the major reason behind this blurriness is the
interpolation of pixel values used by most of the upscaling hardwares.
Nearest-neighbor is a scaling mode, which works by filling in the missing
color values in the upscaled image with that of the coordinate-mapped
nearest source pixel value.
Nearest-neighbor can produce (almost) non-blurry scaling outputs when
the scaling ratio is complete integer. For example:
- input buffer resolution: 1280x720(HD)
- output buffer resolution: 3840x2160(UHD/4K)
- scaling ratio (h) = 3840/1280 = 3
scaling ratio (v) = 2160/720 = 3
In such scenarios, we should try to pick Nearest-neighbor as scaling
method when possible.
Many gaming communities have been asking for integer-mode scaling
support, some links and background:
https://software.intel.com/en-us/articles/integer-scaling-support-on-intel-graphics
http://tanalin.com/en/articles/lossless-scaling/
https://community.amd.com/thread/209107
https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/1002/feature-request-nonblurry-upscaling-at-integer-rat/
This patch series enables NN scaling on Intel display (ICL), when the upscaling
ratio is integer.
Shashank Sharma (2):
drm/i915: Indicate integer up-scaling ratios
drm/i915: Pick nearest-neighbor mode for integer scaling ratios
drivers/gpu/drm/i915/display/intel_display.c | 97 ++++++++++++++++++-
.../drm/i915/display/intel_display_types.h | 7 ++
drivers/gpu/drm/i915/i915_reg.h | 31 ++++++
3 files changed, 134 insertions(+), 1 deletion(-)
--
2.17.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-09-03 16:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 16:52 Shashank Sharma [this message]
2019-09-03 16:52 ` [RFC 1/2] drm/i915: Indicate integer up-scaling ratios Shashank Sharma
2019-09-04 7:28 ` Jani Nikula
2019-09-04 10:37 ` Sharma, Shashank
2019-09-04 7:38 ` Ramalingam C
2019-09-04 10:38 ` Sharma, Shashank
2019-09-03 16:52 ` [RFC 2/2] drm/i915: Pick nearest-neighbor mode for integer scaling ratios Shashank Sharma
2019-09-04 7:54 ` Ramalingam C
2019-09-03 17:05 ` ✗ Fi.CI.CHECKPATCH: warning for Enable Nearest-neighbor for Integer mode scaling Patchwork
2019-09-03 17:20 ` [RFC 0/2] " Ville Syrjälä
2019-09-04 3:02 ` Sharma, Shashank
2019-09-04 12:26 ` Ville Syrjälä
2019-09-04 15:17 ` Sharma, Shashank
2019-09-03 17:21 ` ✗ Fi.CI.BAT: failure for " 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=20190903165227.6056-1-shashank.sharma@intel.com \
--to=shashank.sharma@intel.com \
--cc=intel-gfx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.