From: Jani Nikula <jani.nikula@intel.com>
To: Luca Coelho <luciano.coelho@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [RFC v2 1/4] drm/i915/display: add support for DMC wakelocks
Date: Tue, 16 Jan 2024 14:28:22 +0200 [thread overview]
Message-ID: <875xztsbrt.fsf@intel.com> (raw)
In-Reply-To: <20240111091622.1110799-2-luciano.coelho@intel.com>
On Thu, 11 Jan 2024, Luca Coelho <luciano.coelho@intel.com> wrote:
> diff --git a/drivers/gpu/drm/i915/display/intel_wakelock.h b/drivers/gpu/drm/i915/display/intel_wakelock.h
> new file mode 100644
> index 000000000000..a47205e1ea32
> --- /dev/null
> +++ b/drivers/gpu/drm/i915/display/intel_wakelock.h
> @@ -0,0 +1,34 @@
> +/* SPDX-License-Identifier: MIT */
> +/*
> + * Copyright (C) 2023 Intel Corporation
> + */
> +
> +#ifndef __INTEL_WAKELOCK_H__
> +#define __INTEL_WAKELOCK_H__
> +
> +#include <linux/types.h>
> +#include <linux/workqueue.h>
> +#include <linux/refcount.h>
> +
> +#include "i915_reg_defs.h"
> +
> +struct drm_i915_private;
> +
> +struct intel_display_wl {
> + spinlock_t lock;
> + bool enabled;
> + refcount_t refcount;
> + struct delayed_work work;
> +};
> +
> +struct intel_display_wl_range {
> + u32 start;
> + u32 end;
> +};
> +
> +void intel_display_wl_init(struct drm_i915_private *i915);
> +void intel_display_wl_enable(struct drm_i915_private *i915);
> +void intel_display_wl_get(struct drm_i915_private *i915, i915_reg_t reg);
> +void intel_display_wl_put(struct drm_i915_private *i915, i915_reg_t reg);
Nitpick, I'll want the name prefix to match the filename,
i.e. intel_foo.[ch] have functions named intel_foo_*.
BR,
Jani.
> +
> +#endif /* __INTEL_WAKELOCK_H__ */
> diff --git a/drivers/gpu/drm/xe/Makefile b/drivers/gpu/drm/xe/Makefile
> index 0292b79852a0..387eccab28ae 100644
> --- a/drivers/gpu/drm/xe/Makefile
> +++ b/drivers/gpu/drm/xe/Makefile
> @@ -279,6 +279,7 @@ xe-$(CONFIG_DRM_XE_DISPLAY) += \
> i915-display/intel_vdsc.o \
> i915-display/intel_vga.o \
> i915-display/intel_vrr.o \
> + i915-display/intel_wakelock.o \
> i915-display/intel_wm.o \
> i915-display/skl_scaler.o \
> i915-display/skl_universal_plane.o \
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-01-16 12:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 9:16 [RFC v2 0/5] drm/i915/display: DMC wakelock implementation Luca Coelho
2024-01-11 9:16 ` [RFC v2 1/4] drm/i915/display: add support for DMC wakelocks Luca Coelho
2024-01-11 14:15 ` Gustavo Sousa
2024-01-12 9:58 ` Coelho, Luciano
2024-01-16 12:28 ` Jani Nikula [this message]
2024-01-16 12:32 ` Coelho, Luciano
2024-01-16 12:45 ` Jani Nikula
2024-01-16 13:10 ` Gustavo Sousa
2024-01-11 9:16 ` [RFC v2 2/4] drm/i915/display: use wakelock in the remaining read operations Luca Coelho
2024-01-11 9:16 ` [RFC v2 3/4] drm/i915/display: use wakelock in register waiting functions Luca Coelho
2024-01-11 9:16 ` [RFC v2 4/4] drm/i915/display: use wakelock in the last write function Luca Coelho
2024-01-11 9:55 ` ✓ CI.Patch_applied: success for drm/i915/display: DMC wakelock implementation Patchwork
2024-01-11 9:56 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-11 9:57 ` ✓ CI.KUnit: success " Patchwork
2024-01-11 10:04 ` ✓ CI.Build: " Patchwork
2024-01-11 10:05 ` ✓ CI.Hooks: " Patchwork
2024-01-11 10:06 ` ✗ CI.checksparse: warning " Patchwork
2024-01-11 10:43 ` ✗ CI.BAT: failure " 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=875xztsbrt.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=luciano.coelho@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