From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 05/10] drm/i915/crt: Clean up ADPA_HOTPLUG_BITS definitions
Date: Fri, 08 Nov 2024 15:12:20 +0200 [thread overview]
Message-ID: <87jzddeuob.fsf@intel.com> (raw)
In-Reply-To: <20241107161123.16269-6-ville.syrjala@linux.intel.com>
On Thu, 07 Nov 2024, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> ADPA_HOTPLUG_BITS is defined in terms of the individual
> register bits and is defined in intel_crt.c, whereas the
> counterpart mask (ADPA_CRT_HOTPLUG_MASK) is just defined
> as a raw hex constant and lives in i915_reg.h. Just define
> both the same way (with unified name to boot) and move both
> to intel_crt.c since they are more an implementation detail
> rather than anything to do with the actual regiter definitions.
*register
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_crt.c | 16 ++++++++++++----
> drivers/gpu/drm/i915/i915_reg.h | 1 -
> 2 files changed, 12 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_crt.c b/drivers/gpu/drm/i915/display/intel_crt.c
> index 73d5332cf103..e21e402f85c8 100644
> --- a/drivers/gpu/drm/i915/display/intel_crt.c
> +++ b/drivers/gpu/drm/i915/display/intel_crt.c
> @@ -55,12 +55,20 @@
> #include "intel_pch_refclk.h"
>
> /* Here's the desired hotplug mode */
> -#define ADPA_HOTPLUG_BITS (ADPA_CRT_HOTPLUG_PERIOD_128 | \
> +#define ADPA_HOTPLUG_BITS (ADPA_CRT_HOTPLUG_ENABLE | \
> + ADPA_CRT_HOTPLUG_PERIOD_128 | \
> ADPA_CRT_HOTPLUG_WARMUP_10MS | \
> ADPA_CRT_HOTPLUG_SAMPLE_4S | \
> ADPA_CRT_HOTPLUG_VOLTAGE_50 | \
> - ADPA_CRT_HOTPLUG_VOLREF_325MV | \
> - ADPA_CRT_HOTPLUG_ENABLE)
> + ADPA_CRT_HOTPLUG_VOLREF_325MV)
> +#define ADPA_HOTPLUG_MASK (ADPA_CRT_HOTPLUG_MONITOR_MASK | \
> + ADPA_CRT_HOTPLUG_ENABLE | \
> + ADPA_CRT_HOTPLUG_PERIOD_MASK | \
> + ADPA_CRT_HOTPLUG_WARMUP_MASK | \
> + ADPA_CRT_HOTPLUG_SAMPLE_MASK | \
> + ADPA_CRT_HOTPLUG_VOLTAGE_MASK | \
> + ADPA_CRT_HOTPLUG_VOLREF_MASK | \
> + ADPA_CRT_HOTPLUG_FORCE_TRIGGER)
>
> struct intel_crt {
> struct intel_encoder base;
> @@ -984,7 +992,7 @@ void intel_crt_reset(struct drm_encoder *encoder)
> u32 adpa;
>
> adpa = intel_de_read(display, crt->adpa_reg);
> - adpa &= ~ADPA_CRT_HOTPLUG_MASK;
> + adpa &= ~ADPA_HOTPLUG_MASK;
> adpa |= ADPA_HOTPLUG_BITS;
> intel_de_write(display, crt->adpa_reg, adpa);
> intel_de_posting_read(display, crt->adpa_reg);
> diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> index f233fc32e45c..6391f2e9d530 100644
> --- a/drivers/gpu/drm/i915/i915_reg.h
> +++ b/drivers/gpu/drm/i915/i915_reg.h
> @@ -1156,7 +1156,6 @@
> #define ADPA_PIPE_SEL(pipe) REG_FIELD_PREP(ADPA_PIPE_SEL_MASK, (pipe))
> #define ADPA_PIPE_SEL_MASK_CPT REG_GENMASK(30, 29)
> #define ADPA_PIPE_SEL_CPT(pipe) REG_FIELD_PREP(ADPA_PIPE_SEL_MASK_CPT, (pipe))
> -#define ADPA_CRT_HOTPLUG_MASK 0x03ff0000 /* bit 25-16 */
> #define ADPA_CRT_HOTPLUG_MONITOR_MASK REG_GENMASK(25, 24)
> #define ADPA_CRT_HOTPLUG_MONITOR_NONE REG_FIELD_PREP(ADPA_CRT_HOTPLUG_MONITOR_MASK, 0)
> #define ADPA_CRT_HOTPLUG_MONITOR_COLOR REG_FIELD_PREP(ADPA_CRT_HOTPLUG_MONITOR_MASK, 3)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-11-08 13:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 16:11 [PATCH 00/10] drm/i915: Potential boot oops fix and some cleanups Ville Syrjala
2024-11-07 16:11 ` [PATCH 01/10] drm/i915: Grab intel_display from the encoder to avoid potential oopsies Ville Syrjala
2024-11-08 13:00 ` Jani Nikula
2024-11-11 22:03 ` Ville Syrjälä
2024-11-07 16:11 ` [PATCH 02/10] drm/i915/crt: Split long line Ville Syrjala
2024-11-08 13:01 ` Jani Nikula
2024-11-07 16:11 ` [PATCH 03/10] drm/i915/crt: Drop the unused ADPA_DPMS bit definitions Ville Syrjala
2024-11-08 13:02 ` Jani Nikula
2024-11-07 16:11 ` [PATCH 04/10] drm/i915/crt: Use REG_BIT() & co Ville Syrjala
2024-11-08 13:08 ` Jani Nikula
2024-11-07 16:11 ` [PATCH 05/10] drm/i915/crt: Clean up ADPA_HOTPLUG_BITS definitions Ville Syrjala
2024-11-08 13:12 ` Jani Nikula [this message]
2024-11-07 16:11 ` [PATCH 06/10] drm/i915/crt: Extract intel_crt_regs.h Ville Syrjala
2024-11-08 13:13 ` Jani Nikula
2024-11-07 16:11 ` [PATCH 07/10] drm/i915/crt: s/pipe_config/crtc_state/ Ville Syrjala
2024-11-08 13:14 ` Jani Nikula
2024-11-07 16:11 ` [PATCH 08/10] drm/i915/crt: Drop pointless drm_device variables Ville Syrjala
2024-11-08 13:15 ` Jani Nikula
2024-11-07 16:11 ` [PATCH 09/10] drm/i915/crt: Rename some variables Ville Syrjala
2024-11-08 13:16 ` Jani Nikula
2024-11-07 16:11 ` [PATCH 10/10] drm/i915/crt: Nuke unused crt->connector Ville Syrjala
2024-11-08 13:16 ` Jani Nikula
2024-11-08 4:56 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Potential boot oops fix and some cleanups (rev2) Patchwork
2024-11-08 4:56 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-11-08 5:10 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-11-08 17:08 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Potential boot oops fix and some cleanups (rev3) Patchwork
2024-11-08 17:08 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-11-08 17:24 ` ✓ Fi.CI.BAT: success " Patchwork
2024-11-08 18:22 ` ✓ Fi.CI.IGT: " 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=87jzddeuob.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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