From: Gustavo Sousa <gustavo.sousa@intel.com>
To: Jani Nikula <jani.nikula@intel.com>,
<intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>
Cc: <jani.nikula@intel.com>
Subject: Re: [PATCH v2 6/7] drm/i915/pch: use intel_de_wait_custom() instead of wait_for_us()
Date: Thu, 31 Jul 2025 10:27:27 -0300 [thread overview]
Message-ID: <175396844704.2011.2171397066782049225@intel.com> (raw)
In-Reply-To: <67e0afa2c0c5ad39b9108af15d0496394e674518.1753956266.git.jani.nikula@intel.com>
Quoting Jani Nikula (2025-07-31 07:05:13-03:00)
>Prefer the register read specific wait function over i915 wait_for_us().
>
>Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Gustavo Sousa <gustavo.sousa@intel.com>
>---
> drivers/gpu/drm/i915/display/intel_pch_refclk.c | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
>
>diff --git a/drivers/gpu/drm/i915/display/intel_pch_refclk.c b/drivers/gpu/drm/i915/display/intel_pch_refclk.c
>index d3c5255bf1a8..9ae53679a041 100644
>--- a/drivers/gpu/drm/i915/display/intel_pch_refclk.c
>+++ b/drivers/gpu/drm/i915/display/intel_pch_refclk.c
>@@ -17,16 +17,22 @@
>
> static void lpt_fdi_reset_mphy(struct intel_display *display)
> {
>+ int ret;
>+
> intel_de_rmw(display, SOUTH_CHICKEN2, 0, FDI_MPHY_IOSFSB_RESET_CTL);
>
>- if (wait_for_us(intel_de_read(display, SOUTH_CHICKEN2) &
>- FDI_MPHY_IOSFSB_RESET_STATUS, 100))
>+ ret = intel_de_wait_custom(display, SOUTH_CHICKEN2,
>+ FDI_MPHY_IOSFSB_RESET_STATUS, FDI_MPHY_IOSFSB_RESET_STATUS,
>+ 100, 0, NULL);
>+ if (ret)
> drm_err(display->drm, "FDI mPHY reset assert timeout\n");
>
> intel_de_rmw(display, SOUTH_CHICKEN2, FDI_MPHY_IOSFSB_RESET_CTL, 0);
>
>- if (wait_for_us((intel_de_read(display, SOUTH_CHICKEN2) &
>- FDI_MPHY_IOSFSB_RESET_STATUS) == 0, 100))
>+ ret = intel_de_wait_custom(display, SOUTH_CHICKEN2,
>+ FDI_MPHY_IOSFSB_RESET_STATUS, 0,
>+ 100, 0, NULL);
>+ if (ret)
> drm_err(display->drm, "FDI mPHY reset de-assert timeout\n");
> }
>
>--
>2.39.5
>
next prev parent reply other threads:[~2025-07-31 13:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 10:05 [PATCH v2 0/7] drm/i915/display: use intel_de_wait_*() functions Jani Nikula
2025-07-31 10:05 ` [PATCH v2 1/7] drm/i915/hdmi: use intel_de_wait_for_set() instead of wait_for() Jani Nikula
2025-07-31 12:54 ` Gustavo Sousa
2025-07-31 10:05 ` [PATCH v2 2/7] drm/i915/ddi: use intel_de_wait_custom() instead of wait_for_us() Jani Nikula
2025-07-31 13:00 ` Gustavo Sousa
2025-08-01 9:10 ` Jani Nikula
2025-07-31 10:05 ` [PATCH v2 3/7] drm/i915/dpll: " Jani Nikula
2025-07-31 13:09 ` Gustavo Sousa
2025-07-31 10:05 ` [PATCH v2 4/7] drm/i915/cdclk: " Jani Nikula
2025-07-31 13:22 ` Gustavo Sousa
2025-07-31 10:05 ` [PATCH v2 5/7] drm/i915/power: " Jani Nikula
2025-07-31 13:25 ` Gustavo Sousa
2025-07-31 10:05 ` [PATCH v2 6/7] drm/i915/pch: " Jani Nikula
2025-07-31 13:27 ` Gustavo Sousa [this message]
2025-07-31 10:05 ` [PATCH v2 7/7] drm/i915/dsi: " Jani Nikula
2025-07-31 13:32 ` Gustavo Sousa
2025-07-31 12:43 ` ✓ CI.KUnit: success for drm/i915/display: use intel_de_wait_*() functions (rev3) Patchwork
2025-07-31 12:58 ` ✗ CI.checksparse: warning " Patchwork
2025-07-31 13:54 ` ✓ Xe.CI.BAT: success " Patchwork
2025-07-31 15:25 ` ✗ Xe.CI.Full: 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=175396844704.2011.2171397066782049225@intel.com \
--to=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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