From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Golani,
Mitulkumar Ajitkumar" <mitulkumar.ajitkumar.golani@intel.com>,
"Garg, Nemesa" <nemesa.garg@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "Garg, Nemesa" <nemesa.garg@intel.com>,
"Kulkarni@freedesktop.org" <Kulkarni@freedesktop.org>,
"Kulkarni, Vandita" <vandita.kulkarni@intel.com>
Subject: RE: [PATCH] drm/i915/display: Add WA_14018221282
Date: Fri, 08 Nov 2024 11:32:37 +0200 [thread overview]
Message-ID: <878qtuf4ui.fsf@intel.com> (raw)
In-Reply-To: <CY5PR11MB6344E6FFAF5D2A2085CCFEC7B25D2@CY5PR11MB6344.namprd11.prod.outlook.com>
On Fri, 08 Nov 2024, "Golani, Mitulkumar Ajitkumar" <mitulkumar.ajitkumar.golani@intel.com> wrote:
>> -----Original Message-----
>> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of
>> Nemesa Garg
>> Sent: 08 November 2024 13:31
>> To: intel-gfx@lists.freedesktop.org
>> Cc: Garg, Nemesa <nemesa.garg@intel.com>; Kulkarni@freedesktop.org;
>> Kulkarni, Vandita <vandita.kulkarni@intel.com>
>> Subject: [PATCH] drm/i915/display: Add WA_14018221282
>>
>> It was observed that the first write to DKL DP Mode register was not taking
>> effect, hence rewrite this register.
>>
>> Signed-off-by: Nemesa Garg <nemesa.garg@intel.com>
>> Signed-off-by: Kulkarni, Vandita <vandita.kulkarni@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_ddi.c | 14 ++++++++++++++
>> 1 file changed, 14 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_ddi.c
>> b/drivers/gpu/drm/i915/display/intel_ddi.c
>> index 769bd1f26db2..16a1d18f3aa1 100644
>> --- a/drivers/gpu/drm/i915/display/intel_ddi.c
>> +++ b/drivers/gpu/drm/i915/display/intel_ddi.c
>> @@ -2104,6 +2104,16 @@ void
>> intel_ddi_sanitize_encoder_pll_mapping(struct intel_encoder *encoder)
>> encoder->disable_clock(encoder);
>> }
>>
>> +static void
>> +tgl_wa_14018221282(struct drm_i915_private *dev_priv, enum tc_port
>> tc_port,
>
> 1. I recommend, Need to think on naming here, as doesn't clarify on anything.
Yes please everyone stop with the madness of naming functions
bla_bla_wa_124235432().
BR,
Jani.
> 2. Also adding on thought to have pre-check of return if values are already updated.
>
>> + u32 ln0, u32 ln1)
>> +{
>> + if (ln0 != intel_dkl_phy_read(dev_priv, DKL_DP_MODE(tc_port, 0)))
>> + intel_dkl_phy_write(dev_priv, DKL_DP_MODE(tc_port, 0),
>> ln0);
>> + if (ln1 != intel_dkl_phy_read(dev_priv, DKL_DP_MODE(tc_port, 1)))
>> + intel_dkl_phy_write(dev_priv, DKL_DP_MODE(tc_port, 1),
>> ln1); }
>> +
>> static void
>> icl_program_mg_dp_mode(struct intel_digital_port *dig_port,
>> const struct intel_crtc_state *crtc_state) @@ -2185,6
>> +2195,10 @@ icl_program_mg_dp_mode(struct intel_digital_port *dig_port,
>> if (DISPLAY_VER(dev_priv) >= 12) {
>> intel_dkl_phy_write(dev_priv, DKL_DP_MODE(tc_port, 0),
>> ln0);
>> intel_dkl_phy_write(dev_priv, DKL_DP_MODE(tc_port, 1),
>> ln1);
>> + /* WA_14018221282 */
>> + if (DISPLAY_VER(dev_priv) == 12)
>> + tgl_wa_14018221282(dev_priv, tc_port, ln0, ln1);
>
> Always use the display local var when possible. DISPLAY_VER(display)
>
>> +
>> } else {
>> intel_de_write(dev_priv, MG_DP_MODE(0, tc_port), ln0);
>> intel_de_write(dev_priv, MG_DP_MODE(1, tc_port), ln1);
>> --
>> 2.25.1
>
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-11-08 9:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 8:01 [PATCH] drm/i915/display: Add WA_14018221282 Nemesa Garg
2024-11-08 8:16 ` Golani, Mitulkumar Ajitkumar
2024-11-08 9:02 ` Garg, Nemesa
2024-11-08 9:32 ` Jani Nikula [this message]
2024-11-08 9:08 ` ✗ Fi.CI.BAT: failure for " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-11-11 8:08 [PATCH] " Nemesa Garg
2024-11-11 8:32 ` Jani Nikula
2024-11-11 17:42 ` Garg, Nemesa
2024-12-12 9:40 Nemesa Garg
2024-12-13 18:49 ` Matt Roper
2024-12-26 6:06 Nemesa Garg
2025-01-08 12:58 ` Kahola, Mika
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=878qtuf4ui.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Kulkarni@freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mitulkumar.ajitkumar.golani@intel.com \
--cc=nemesa.garg@intel.com \
--cc=vandita.kulkarni@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