From: Jani Nikula <jani.nikula@linux.intel.com>
To: Dibin Moolakadan Subrahmanian
<dibin.moolakadan.subrahmanian@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: imre.deak@intel.com, uma.shankar@intel.com
Subject: Re: [PATCH v2] drm/i915/display: Mask RO bits in gen9_write_dc_state()
Date: Mon, 01 Jun 2026 12:38:31 +0300 [thread overview]
Message-ID: <4e28616f97067f232226a0fab8c2039cb124b2b8@intel.com> (raw)
In-Reply-To: <20260601090131.1840805-1-dibin.moolakadan.subrahmanian@intel.com>
On Mon, 01 Jun 2026, Dibin Moolakadan Subrahmanian <dibin.moolakadan.subrahmanian@intel.com> wrote:
> The DC_STATE_EN register has read-only status bits that are set by
> hardware on some platforms. These bits may cause the read-back
> verification loop in gen9_write_dc_state() to spuriously retry.
>
> Mask the RO bits from both the write value and the read-back comparison
> to prevent unnecessary retries.
>
> Changes in v2:
> - Rename patch from
> "drm/i915/display: Use rmw in gen9_write_dc_state() to preserve non-DC
> bits"
> to
> "drm/i915/display: Mask RO bits in gen9_write_dc_state()"
> - Mask only RO bits rather than masking all non DC state bits
> in DC_STATE_EN. As the register has also some clear-on-write flags,
> like 'Display DC*CO State Status DSI'(Imre Deak)
>
> BSpec: 49437,69115
> Signed-off-by: Dibin Moolakadan Subrahmanian <dibin.moolakadan.subrahmanian@intel.com>
> ---
> .../i915/display/intel_display_power_well.c | 29 +++++++++++++++----
> 1 file changed, 24 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_power_well.c b/drivers/gpu/drm/i915/display/intel_display_power_well.c
> index 04bd0dde5bed..4bc9e3ef738e 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_power_well.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_power_well.c
> @@ -726,14 +726,33 @@ static void assert_can_disable_dc9(struct intel_display *display)
> */
> }
>
> +static u32 dc_state_ro_mask(struct intel_display *display)
> +{
> + if (DISPLAY_VER(display) >= 20)
> + return BIT(10) | BIT(11);
> + else if (DISPLAY_VER(display) >= 13 && !display->platform.dg2)
> + return BIT(10);
> +
> + return 0;
> +}
> +
> static void gen9_write_dc_state(struct intel_display *display,
> u32 state)
The caller already has the platform specific mask, please just pass that
in and use it.
BR,
Jani.
> {
> int rewrites = 0;
> int rereads = 0;
> u32 v;
> + u32 ro_mask = dc_state_ro_mask(display);
> + u32 val = state;
> +
> + /*
> + * Mask out RO status bits from both the write value and the read-back
> + * comparison. HW may set these bits independently, so exclude them
> + * to prevent the verify loop from retrying due to RO bits mismatch.
> + */
> + val &= ~ro_mask;
>
> - intel_de_write(display, DC_STATE_EN, state);
> + intel_de_write(display, DC_STATE_EN, val);
>
> /* It has been observed that disabling the dc6 state sometimes
> * doesn't stick and dmc keeps returning old value. Make sure
> @@ -741,10 +760,10 @@ static void gen9_write_dc_state(struct intel_display *display,
> * we are confident that state is exactly what we want.
> */
> do {
> - v = intel_de_read(display, DC_STATE_EN);
> + v = intel_de_read(display, DC_STATE_EN) & ~ro_mask;
>
> - if (v != state) {
> - intel_de_write(display, DC_STATE_EN, state);
> + if (v != val) {
> + intel_de_write(display, DC_STATE_EN, val);
> rewrites++;
> rereads = 0;
> } else if (rereads++ > 5) {
> @@ -753,7 +772,7 @@ static void gen9_write_dc_state(struct intel_display *display,
>
> } while (rewrites < 100);
>
> - if (v != state)
> + if (v != val)
> drm_err(display->drm,
> "Writing dc state to 0x%x failed, now 0x%x\n",
> state, v);
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-06-01 9:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<20260506130321.487414-1-dibin.moolakadan.subrahmanian@intel.com>
2026-06-01 9:01 ` [PATCH v2] drm/i915/display: Mask RO bits in gen9_write_dc_state() Dibin Moolakadan Subrahmanian
2026-06-01 9:38 ` Jani Nikula [this message]
2026-06-01 11:47 ` Imre Deak
2026-06-02 4:51 ` Dibin Moolakadan Subrahmanian
2026-06-02 11:31 ` [PATCH v3] " Dibin Moolakadan Subrahmanian
2026-06-03 8:30 ` Jani Nikula
2026-06-03 11:45 ` Imre Deak
2026-06-03 15:16 ` Jani Nikula
2026-06-05 7:52 ` Dibin Moolakadan Subrahmanian
2026-06-01 11:38 ` ✓ CI.KUnit: success for " Patchwork
2026-06-01 12:18 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-01 14:51 ` ✓ Xe.CI.FULL: " Patchwork
2026-06-02 12:15 ` ✓ CI.KUnit: success for drm/i915/display: Mask RO bits in gen9_write_dc_state() (rev2) Patchwork
2026-06-02 12:53 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-02 21:31 ` ✓ Xe.CI.FULL: " Patchwork
2026-05-06 13:03 [PATCH] drm/i915/display: Use rmw in gen9_write_dc_state() to preserve non-DC bits Dibin Moolakadan Subrahmanian
2026-05-06 13:10 ` ✓ CI.KUnit: success for " Patchwork
2026-05-06 13:35 ` [PATCH] " Imre Deak
2026-05-07 5:47 ` Dibin Moolakadan Subrahmanian
2026-05-07 6:36 ` Imre Deak
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=4e28616f97067f232226a0fab8c2039cb124b2b8@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dibin.moolakadan.subrahmanian@intel.com \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=uma.shankar@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