From: Jani Nikula <jani.nikula@linux.intel.com>
To: Mika Kahola <mika.kahola@intel.com>, intel-gfx@lists.freedesktop.org
Cc: gustavo.sousa@intel.com, raag.jadav@intel.com,
Mika Kahola <mika.kahola@intel.com>
Subject: Re: [PATCH v4 2/2] drm/i915/display: Use struct intel_display instead of struct drm_i915_private
Date: Mon, 04 Nov 2024 12:32:36 +0200 [thread overview]
Message-ID: <87msifi917.fsf@intel.com> (raw)
In-Reply-To: <20241101133924.245817-3-mika.kahola@intel.com>
On Fri, 01 Nov 2024, Mika Kahola <mika.kahola@intel.com> wrote:
> Let's start using struct intel_display instead of struct drm_i915_private
> when introducing new code. No functional changes.
>
> Signed-off-by: Mika Kahola <mika.kahola@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_tc.c | 17 +++++++++++------
> 1 file changed, 11 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_tc.c b/drivers/gpu/drm/i915/display/intel_tc.c
> index e40d55f4c0c4..385c838ee996 100644
> --- a/drivers/gpu/drm/i915/display/intel_tc.c
> +++ b/drivers/gpu/drm/i915/display/intel_tc.c
> @@ -97,6 +97,11 @@ static struct drm_i915_private *tc_to_i915(struct intel_tc_port *tc)
> return to_i915(tc->dig_port->base.base.dev);
> }
>
> +static struct intel_display *tc_to_intel_display(struct intel_tc_port *tc)
> +{
> + return to_intel_display(tc->dig_port->base.base.dev);
> +}
> +
to_intel_display(tc->dig_port) is sufficient here.
And that begs the question, do we need the helper? Maybe just use that
directly inline?
BR,
Jani.
> static bool intel_tc_port_in_mode(struct intel_digital_port *dig_port,
> enum tc_port_mode mode)
> {
> @@ -1039,9 +1044,9 @@ static void wa_14020908590(struct intel_display *display, bool enable)
>
> static void __xelpdp_tc_phy_enable_tcss_power(struct intel_tc_port *tc, bool enable)
> {
> - struct drm_i915_private *i915 = tc_to_i915(tc);
> + struct intel_display *display = tc_to_intel_display(tc);
> enum port port = tc->dig_port->base.port;
> - i915_reg_t reg = XELPDP_PORT_BUF_CTL1(i915, port);
> + i915_reg_t reg = XELPDP_PORT_BUF_CTL1(display, port);
> u32 val;
>
> assert_tc_cold_blocked(tc);
> @@ -1050,15 +1055,15 @@ static void __xelpdp_tc_phy_enable_tcss_power(struct intel_tc_port *tc, bool ena
> * Gfx driver WA 14020908590 for PTL tcss_rxdetect_clkswb_req/ack
> * handshake violation when pwwreq= 0->1 during TC7/10 entry
> */
> - if (DISPLAY_VER(i915) == 30)
> - wa_14020908590(&i915->display, enable);
> + if (DISPLAY_VER(display) == 30)
> + wa_14020908590(display, enable);
>
> - val = intel_de_read(i915, reg);
> + val = intel_de_read(display, reg);
> if (enable)
> val |= XELPDP_TCSS_POWER_REQUEST;
> else
> val &= ~XELPDP_TCSS_POWER_REQUEST;
> - intel_de_write(i915, reg, val);
> + intel_de_write(display, reg, val);
> }
>
> static bool xelpdp_tc_phy_enable_tcss_power(struct intel_tc_port *tc, bool enable)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-11-04 10:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 13:39 [PATCH v4 0/2] drm/i915/display: Power request asserting/deasserting Mika Kahola
2024-11-01 13:39 ` [PATCH v4 1/2] drm/i915/xe3lpd: " Mika Kahola
2024-11-01 13:39 ` [PATCH v4 2/2] drm/i915/display: Use struct intel_display instead of struct drm_i915_private Mika Kahola
2024-11-04 10:32 ` Jani Nikula [this message]
2024-11-04 12:44 ` Kahola, Mika
2024-11-04 12:09 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display: Power request asserting/deasserting (rev2) Patchwork
2024-11-04 12:09 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-11-04 13:07 ` ✓ Fi.CI.BAT: success " Patchwork
2024-11-04 22:44 ` ✓ 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=87msifi917.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=gustavo.sousa@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kahola@intel.com \
--cc=raag.jadav@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.