From: Jani Nikula <jani.nikula@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: vinod.govindapillai@intel.com, Suraj Kandpal <suraj.kandpal@intel.com>
Subject: Re: [PATCH 1/6] drm/i915/wm: Initialize max_latency variable to appropriate value
Date: Mon, 02 Dec 2024 11:42:26 +0200 [thread overview]
Message-ID: <871pyq775p.fsf@intel.com> (raw)
In-Reply-To: <20241115160116.1436521-1-suraj.kandpal@intel.com>
On Fri, 15 Nov 2024, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> Initialize max_latency variable to LNL_PKG_C_LATENCY_MASK which helps
> to eliminate the else block and make the whole code a lot cleaner.
> While we are at it group the initialized variable together.
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
> drivers/gpu/drm/i915/display/skl_watermark.c | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/skl_watermark.c b/drivers/gpu/drm/i915/display/skl_watermark.c
> index 1a4c1fa24820..a49e8915346e 100644
> --- a/drivers/gpu/drm/i915/display/skl_watermark.c
> +++ b/drivers/gpu/drm/i915/display/skl_watermark.c
> @@ -2857,9 +2857,8 @@ static int skl_wm_add_affected_planes(struct intel_atomic_state *state,
> static void
> skl_program_dpkgc_latency(struct drm_i915_private *i915, bool enable_dpkgc)
> {
> - u32 max_latency = 0;
> + u32 max_latency = LNL_PKG_C_LATENCY_MASK, added_wake_time = 0;
Whoops. Please read your own commits through before sending.
BR,
Jani.
> u32 clear = 0, val = 0;
> - u32 added_wake_time = 0;
>
> if (DISPLAY_VER(i915) < 20)
> return;
> @@ -2870,9 +2869,6 @@ skl_program_dpkgc_latency(struct drm_i915_private *i915, bool enable_dpkgc)
> max_latency = LNL_PKG_C_LATENCY_MASK;
> added_wake_time = DSB_EXE_TIME +
> i915->display.sagv.block_time_us;
> - } else {
> - max_latency = LNL_PKG_C_LATENCY_MASK;
> - added_wake_time = 0;
> }
>
> clear |= LNL_ADDED_WAKE_TIME_MASK | LNL_PKG_C_LATENCY_MASK;
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-12-02 9:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 16:01 [PATCH 1/6] drm/i915/wm: Initialize max_latency variable to appropriate value Suraj Kandpal
2024-11-15 16:01 ` [PATCH 2/6] drm/i915/wm: Refactor dpkgc value prepration Suraj Kandpal
2024-11-15 16:01 ` [PATCH 3/6] drm/i915/wm: Rename enable_dpkgc variable Suraj Kandpal
2024-12-02 9:34 ` Golani, Mitulkumar Ajitkumar
2024-12-02 9:40 ` Kandpal, Suraj
2024-12-02 9:59 ` Kandpal, Suraj
2024-11-15 16:01 ` [PATCH 4/6] drm/i915/wm: Use intel_display structure in DPKGC code Suraj Kandpal
2024-12-02 9:38 ` Golani, Mitulkumar Ajitkumar
2024-12-02 9:50 ` Kandpal, Suraj
2024-11-15 16:01 ` [PATCH 5/6] drm/i915/display: Refactor DPKGC code to call it from atomic_commit_tail Suraj Kandpal
2024-12-02 12:38 ` Golani, Mitulkumar Ajitkumar
2024-11-15 16:01 ` [PATCH 6/6] drm/i915/wm: Modify latency programmed into PKG_C_LATENCY Suraj Kandpal
2024-12-03 8:04 ` Golani, Mitulkumar Ajitkumar
2024-12-03 8:38 ` Kandpal, Suraj
2024-11-15 16:07 ` ✓ CI.Patch_applied: success for series starting with [1/6] drm/i915/wm: Initialize max_latency variable to appropriate value Patchwork
2024-11-15 16:07 ` ✓ CI.checkpatch: " Patchwork
2024-11-15 16:09 ` ✓ CI.KUnit: " Patchwork
2024-11-15 16:18 ` ✗ CI.Build: failure " Patchwork
2024-11-15 16:26 ` ✗ Fi.CI.BAT: " Patchwork
2024-11-15 16:26 ` ✗ Fi.CI.SPARSE: warning " Patchwork
2024-11-18 4:00 ` ✓ CI.Patch_applied: success for series starting with [1/6] drm/i915/wm: Initialize max_latency variable to appropriate value (rev2) Patchwork
2024-11-18 4:00 ` ✓ CI.checkpatch: " Patchwork
2024-11-18 4:02 ` ✓ CI.KUnit: " Patchwork
2024-11-18 4:27 ` ✓ CI.Build: " Patchwork
2024-11-18 4:27 ` ✗ CI.Hooks: failure " Patchwork
2024-11-18 4:29 ` ✗ CI.checksparse: warning " Patchwork
2024-11-18 4:48 ` ✓ CI.BAT: success " Patchwork
2024-11-18 5:52 ` ✗ CI.FULL: failure " Patchwork
2024-12-02 9:15 ` [PATCH 1/6] drm/i915/wm: Initialize max_latency variable to appropriate value Golani, Mitulkumar Ajitkumar
2024-12-02 9:17 ` Kandpal, Suraj
2024-12-02 9:42 ` Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-03 8:47 Suraj Kandpal
2024-12-05 1:35 ` Golani, Mitulkumar Ajitkumar
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=871pyq775p.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=suraj.kandpal@intel.com \
--cc=vinod.govindapillai@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 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.