From: Jani Nikula <jani.nikula@linux.intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>, intel-gfx@lists.freedesktop.org
Cc: arun.r.murthy@intel.com, Suraj Kandpal <suraj.kandpal@intel.com>,
Nemesa Garg <nemesa.garg@intel.com>
Subject: Re: [RFC 1/3] drm/i915: Add Dark screen detection registers
Date: Wed, 24 Apr 2024 12:05:26 +0300 [thread overview]
Message-ID: <87frvbqgfd.fsf@intel.com> (raw)
In-Reply-To: <20240424073829.824312-3-suraj.kandpal@intel.com>
On Wed, 24 Apr 2024, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> Add Dark screen detection related register and field definitions.
It's time we stopped adding *any* new display registers to i915_reg.h.
BR,
Jani.
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> Signed-off-by: Nemesa Garg <nemesa.garg@intel.com>
> ---
> drivers/gpu/drm/i915/i915_reg.h | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> index 8eb6c2bf4557..474b1c263517 100644
> --- a/drivers/gpu/drm/i915/i915_reg.h
> +++ b/drivers/gpu/drm/i915/i915_reg.h
> @@ -1838,6 +1838,14 @@
> #define VRR_VSYNC_START_MASK REG_GENMASK(12, 0)
> #define VRR_VSYNC_START(vsync_start) REG_FIELD_PREP(VRR_VSYNC_START_MASK, (vsync_start))
>
> +#define _DARK_SCREEN_PIPE_A 0x60120
> +#define DARK_SCREEN(trans) _MMIO_TRANS2(trans, _DARK_SCREEN_PIPE_A)
> +#define DARK_SCREEN_ENABLE REG_BIT(31)
> +#define DARK_SCREEN_DETECT REG_BIT(29)
> +#define DARK_SCREEN_DONE REG_BIT(28)
> +#define DARK_SCREEN_COMPARE_MASK REG_GENMASK(9, 0)
> +#define DARK_SCREEN_COMPARE_VAL(x) REG_FIELD_PREP(DARK_SCREEN_COMPARE_MASK, (x))
> +
> /* VGA port control */
> #define ADPA _MMIO(0x61100)
> #define PCH_ADPA _MMIO(0xe1100)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-04-24 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 7:38 [RFC 0/3] Enable darkscreen detection Suraj Kandpal
2024-04-24 7:38 ` [RFC 1/3] drm/i915: Add Dark screen detection registers Suraj Kandpal
2024-04-24 9:05 ` Jani Nikula [this message]
2024-04-24 7:38 ` [RFC 2/3] drm/i915/darkscreen: Enable darkscreen detection Suraj Kandpal
2024-04-24 9:41 ` Jani Nikula
2024-04-24 7:38 ` [RFC 3/3] drm/i915: Schedule darkscreen detection work Suraj Kandpal
2024-04-24 8:19 ` ✗ Fi.CI.CHECKPATCH: warning for Enable darkscreen detection Patchwork
2024-04-24 8:20 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-04-24 9:48 ` [RFC 0/3] " Jani Nikula
2024-04-24 10:01 ` Kandpal, Suraj
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=87frvbqgfd.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nemesa.garg@intel.com \
--cc=suraj.kandpal@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.