From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Chaitanya Kumar Borah" <chaitanya.kumar.borah@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ CI.checkpatch: success for drm/i915: Preserve value of fec_enable calculated before DSC compute config
Date: Mon, 12 Aug 2024 08:34:46 -0000 [thread overview]
Message-ID: <172345168686.594024.16632858729837055712@2413ebb6fbb6> (raw)
In-Reply-To: <20240812082446.3459081-1-chaitanya.kumar.borah@intel.com>
== Series Details ==
Series: drm/i915: Preserve value of fec_enable calculated before DSC compute config
URL : https://patchwork.freedesktop.org/series/137152/
State : success
== Summary ==
+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
9fe5037901cabbcdf27a6fe0dfb047ca1474d363
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 58ee393001b69c552c867750a320c5f19dd817d5
Author: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
Date: Mon Aug 12 13:54:46 2024 +0530
drm/i915: Preserve value of fec_enable calculated before DSC compute config
Before DSC compute config, fec_enable value is set in other functions
(e.g. intel_dp_mst_find_vcpi_slots_for_bpp). We are ignoring the value by
OR'ing its value in DSC compute config. One unintended effect of this is
setting fec_enable in UHBR use-cases which is not needed for Intel
hardware. Therefore, change operator to AND.
While at it, add a comment explaining why we don't enable FEC in eDP v1.5.
Signed-off-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
+ /mt/dim checkpatch e2742fa214d806ebd04fc067da4235d82d269033 drm-intel
58ee393001b6 drm/i915: Preserve value of fec_enable calculated before DSC compute config
next prev parent reply other threads:[~2024-08-12 8:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 8:24 [PATCH] drm/i915: Preserve value of fec_enable calculated before DSC compute config Chaitanya Kumar Borah
2024-08-12 8:34 ` ✓ CI.Patch_applied: success for " Patchwork
2024-08-12 8:34 ` Patchwork [this message]
2024-08-12 8:36 ` ✓ CI.KUnit: " Patchwork
2024-08-12 8:55 ` ✓ CI.Build: " Patchwork
2024-08-12 8:57 ` ✓ CI.Hooks: " Patchwork
2024-08-12 8:59 ` ✗ CI.checksparse: warning " Patchwork
2024-08-12 9:33 ` ✓ CI.BAT: success " Patchwork
2024-08-12 11:40 ` ✗ CI.FULL: failure " Patchwork
2024-08-12 11:53 ` [PATCH] " Jani Nikula
2024-08-12 13:03 ` Borah, Chaitanya Kumar
2024-08-14 8:45 ` Jani Nikula
2024-08-22 6:20 ` Borah, Chaitanya Kumar
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=172345168686.594024.16632858729837055712@2413ebb6fbb6 \
--to=patchwork@emeril.freedesktop.org \
--cc=chaitanya.kumar.borah@intel.com \
--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