From: Jani Nikula <jani.nikula@intel.com>
To: "Kahola, Mika" <mika.kahola@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: RE: [PATCH] drm/i915/cx0: split out mtl_get_cx0_buf_trans() to c10 and c20 variants
Date: Wed, 04 Dec 2024 11:21:28 +0200 [thread overview]
Message-ID: <87plm73isn.fsf@intel.com> (raw)
In-Reply-To: <MW4PR11MB7054E2FC4DA3275E9FF14F42EF372@MW4PR11MB7054.namprd11.prod.outlook.com>
On Wed, 04 Dec 2024, "Kahola, Mika" <mika.kahola@intel.com> wrote:
>> -----Original Message-----
>> From: Nikula, Jani <jani.nikula@intel.com>
>> Sent: Friday, 29 November 2024 13.42
>> To: intel-gfx@lists.freedesktop.org; intel-xe@lists.freedesktop.org
>> Cc: Nikula, Jani <jani.nikula@intel.com>; Kahola, Mika <mika.kahola@intel.com>
>> Subject: [PATCH] drm/i915/cx0: split out mtl_get_cx0_buf_trans() to c10 and c20
>> variants
>>
>> The PHY is either c10 or c20, there's no need to check at runtime and complicate
>> the conditions in mtl_get_cx0_buf_trans().
>>
>> While at it, replace the direct port clock check with intel_dp_is_uhbr().
>>
>> Cc: Mika Kahola <mika.kahola@intel.com>
>
> The change is reasonable and solid.
>
> Reviewed-by: Mika Kahola <mika.kahola@intel.com>
Thanks, pushed to drm-intel-next.
BR,
Jani.
>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> .../drm/i915/display/intel_ddi_buf_trans.c | 23 +++++++++++++------
>> 1 file changed, 16 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_ddi_buf_trans.c
>> b/drivers/gpu/drm/i915/display/intel_ddi_buf_trans.c
>> index 4d21ce734343..9389b295036e 100644
>> --- a/drivers/gpu/drm/i915/display/intel_ddi_buf_trans.c
>> +++ b/drivers/gpu/drm/i915/display/intel_ddi_buf_trans.c
>> @@ -1687,18 +1687,24 @@ dg2_get_snps_buf_trans(struct intel_encoder
>> *encoder, }
>>
>> static const struct intel_ddi_buf_trans * -mtl_get_cx0_buf_trans(struct
>> intel_encoder *encoder,
>> +mtl_get_c10_buf_trans(struct intel_encoder *encoder,
>> const struct intel_crtc_state *crtc_state,
>> int *n_entries)
>> {
>> - if (intel_crtc_has_dp_encoder(crtc_state) && crtc_state->port_clock >=
>> 1000000)
>> + return intel_get_buf_trans(&mtl_c10_trans_dp14, n_entries); }
>> +
>> +static const struct intel_ddi_buf_trans * mtl_get_c20_buf_trans(struct
>> +intel_encoder *encoder,
>> + const struct intel_crtc_state *crtc_state,
>> + int *n_entries)
>> +{
>> + if (intel_crtc_has_dp_encoder(crtc_state) &&
>> +intel_dp_is_uhbr(crtc_state))
>> return intel_get_buf_trans(&mtl_c20_trans_uhbr, n_entries);
>> - else if (intel_crtc_has_type(crtc_state, INTEL_OUTPUT_HDMI) &&
>> !(intel_encoder_is_c10phy(encoder)))
>> + else if (intel_crtc_has_type(crtc_state, INTEL_OUTPUT_HDMI))
>> return intel_get_buf_trans(&mtl_c20_trans_hdmi, n_entries);
>> - else if (!intel_encoder_is_c10phy(encoder))
>> - return intel_get_buf_trans(&mtl_c20_trans_dp14, n_entries);
>> else
>> - return intel_get_buf_trans(&mtl_c10_trans_dp14, n_entries);
>> + return intel_get_buf_trans(&mtl_c20_trans_dp14, n_entries);
>> }
>>
>> void intel_ddi_buf_trans_init(struct intel_encoder *encoder) @@ -1706,7
>> +1712,10 @@ void intel_ddi_buf_trans_init(struct intel_encoder *encoder)
>> struct drm_i915_private *i915 = to_i915(encoder->base.dev);
>>
>> if (DISPLAY_VER(i915) >= 14) {
>> - encoder->get_buf_trans = mtl_get_cx0_buf_trans;
>> + if (intel_encoder_is_c10phy(encoder))
>> + encoder->get_buf_trans = mtl_get_c10_buf_trans;
>> + else
>> + encoder->get_buf_trans = mtl_get_c20_buf_trans;
>> } else if (IS_DG2(i915)) {
>> encoder->get_buf_trans = dg2_get_snps_buf_trans;
>> } else if (IS_ALDERLAKE_P(i915)) {
>> --
>> 2.39.5
>
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-12-04 9:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 11:41 [PATCH] drm/i915/cx0: split out mtl_get_cx0_buf_trans() to c10 and c20 variants Jani Nikula
2024-11-29 12:16 ` ✓ CI.Patch_applied: success for " Patchwork
2024-11-29 12:16 ` ✓ CI.checkpatch: " Patchwork
2024-11-29 12:17 ` ✓ CI.KUnit: " Patchwork
2024-11-29 12:23 ` ✓ i915.CI.BAT: " Patchwork
2024-11-29 12:35 ` ✓ CI.Build: " Patchwork
2024-11-29 12:37 ` ✓ CI.Hooks: " Patchwork
2024-11-29 12:39 ` ✗ CI.checksparse: warning " Patchwork
2024-11-29 13:00 ` ✓ Xe.CI.BAT: success " Patchwork
2024-11-29 16:39 ` ✓ i915.CI.Full: " Patchwork
2024-11-30 0:20 ` ✗ Xe.CI.Full: failure " Patchwork
2024-12-04 8:54 ` [PATCH] " Kahola, Mika
2024-12-04 9:21 ` Jani Nikula [this message]
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=87plm73isn.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=mika.kahola@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.