From: Gustavo Sousa <gustavo.sousa@intel.com>
To: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>,
<intel-gfx@lists.freedesktop.org>
Cc: <intel-xe@lists.freedesktop.org>, <jani.nikula@linux.intel.com>
Subject: Re: [PATCH 2/2] drm/i915/gmbus: Add Wa_16025573575 for PTL for bit-bashing
Date: Thu, 3 Jul 2025 09:16:28 -0300 [thread overview]
Message-ID: <175154498806.3748.7979864637600744446@intel.com> (raw)
In-Reply-To: <a1e8b331-eddd-4386-8647-f6364f7744b3@intel.com>
Quoting Nautiyal, Ankit K (2025-07-03 03:05:54-03:00)
>
>On 7/2/2025 6:41 PM, Gustavo Sousa wrote:
>> Quoting Ankit Nautiyal (2025-07-02 05:46:19-03:00)
>>> As per Wa_16025573575 for PTL, set the GPIO masks bit before starting
>>> bit-bashing and maintain value through the bit-bashing sequence.
>>> After bit-bashing sequence is done, clear the GPIO masks bits.
>>>
>>> v2:
>>> -Use new helper for display workarounds. (Jani)
>>> -Use a separate if-block for the workaround. (Gustavo)
>>>
>>> Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>>> ---
>>> .../gpu/drm/i915/display/intel_display_wa.c | 7 ++++
>>> .../gpu/drm/i915/display/intel_display_wa.h | 1 +
>>> drivers/gpu/drm/i915/display/intel_gmbus.c | 34 +++++++++++++++++--
>>> 3 files changed, 40 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/display/intel_display_wa.c b/drivers/gpu/drm/i915/display/intel_display_wa.c
>>> index f5e8d58d9a68..12d1df5981f7 100644
>>> --- a/drivers/gpu/drm/i915/display/intel_display_wa.c
>>> +++ b/drivers/gpu/drm/i915/display/intel_display_wa.c
>>> @@ -42,11 +42,18 @@ void intel_display_wa_apply(struct intel_display *display)
>>> gen11_display_wa_apply(display);
>>> }
>>>
>>> +static bool intel_display_needs_wa_16025573575(struct intel_display *display)
>>> +{
>>> + return DISPLAY_VER(display) == 30;
>> We should also check for 30.02.
>
>I was thinking to add a separate patch for this, but yeah can include in
>this patch as well.
>
>
>>
>>> +}
>>> +
>>> bool __intel_display_wa(struct intel_display *display, enum intel_display_wa wa)
>>> {
>>> switch (wa) {
>>> case INTEL_DISPLAY_WA_16023588340:
>>> return intel_display_needs_wa_16023588340(display);
>>> + case INTEL_DISPLAY_WA_16025573575:
>>> + return intel_display_needs_wa_16025573575(display);
>> While it makes sense to have function
>> intel_display_needs_wa_16023588340() (at least for now), I wonder if the
>> same could be said about intel_display_needs_wa_16025573575()...
>>
>> Maybe it would be simpler to just inline the conditions with a single
>> line here instead of adding 5 extra lines to the file.
>
>
>IMHO, it's better to keep __intel_display_wa() simple and uniform. In
>the future,
>
>some workarounds might involve complex conditions (such as checks for
>steppings,
>applicability to multiple platforms or variants)
>which could make the switch-case harder to read if inlined.
>
>Having dedicated functions like intel_display_needs_wa_xxxx() helps
>encapsulate that logic cleanly.
>
>Mixing inlined conditions with function calls would reduce consistency
>and readability.
Fair enough.
If you prefer to have a separate patch for WCL, then:
Reviewed-by: Gustavo Sousa <gustavo.sousa@intel.com>
>
>
>Thanks & Regards,
>
>Ankit
>
>
>>
>> --
>> Gustavo Sousa
>>
>>> default:
>>> drm_WARN(display->drm, 1, "Missing Wa number: %d\n", wa);
>>> break;
>>> diff --git a/drivers/gpu/drm/i915/display/intel_display_wa.h b/drivers/gpu/drm/i915/display/intel_display_wa.h
>>> index 146ee70d66f7..d3d241992e55 100644
>>> --- a/drivers/gpu/drm/i915/display/intel_display_wa.h
>>> +++ b/drivers/gpu/drm/i915/display/intel_display_wa.h
>>> @@ -23,6 +23,7 @@ bool intel_display_needs_wa_16023588340(struct intel_display *display);
>>>
>>> enum intel_display_wa {
>>> INTEL_DISPLAY_WA_16023588340,
>>> + INTEL_DISPLAY_WA_16025573575,
>>> };
>>>
>>> bool __intel_display_wa(struct intel_display *display, enum intel_display_wa wa);
>>> diff --git a/drivers/gpu/drm/i915/display/intel_gmbus.c b/drivers/gpu/drm/i915/display/intel_gmbus.c
>>> index 0d73f32fe7f1..95cab11c9cde 100644
>>> --- a/drivers/gpu/drm/i915/display/intel_gmbus.c
>>> +++ b/drivers/gpu/drm/i915/display/intel_gmbus.c
>>> @@ -39,6 +39,7 @@
>>> #include "intel_de.h"
>>> #include "intel_display_regs.h"
>>> #include "intel_display_types.h"
>>> +#include "intel_display_wa.h"
>>> #include "intel_gmbus.h"
>>> #include "intel_gmbus_regs.h"
>>>
>>> @@ -241,11 +242,18 @@ static u32 get_reserved(struct intel_gmbus *bus)
>>> {
>>> struct intel_display *display = bus->display;
>>> u32 reserved = 0;
>>> + u32 preserve_bits = 0;
>>>
>>> /* On most chips, these bits must be preserved in software. */
>>> if (!display->platform.i830 && !display->platform.i845g)
>>> - reserved = intel_de_read_notrace(display, bus->gpio_reg) &
>>> - (GPIO_DATA_PULLUP_DISABLE | GPIO_CLOCK_PULLUP_DISABLE);
>>> + preserve_bits |= GPIO_DATA_PULLUP_DISABLE | GPIO_CLOCK_PULLUP_DISABLE;
>>> +
>>> + /* PTL: Wa_16025573575: the masks bits need to be preserved through out */
>>> + if (intel_display_wa(display, 16025573575))
>>> + preserve_bits |= GPIO_CLOCK_DIR_MASK | GPIO_CLOCK_VAL_MASK |
>>> + GPIO_DATA_DIR_MASK | GPIO_DATA_VAL_MASK;
>>> +
>>> + reserved = intel_de_read_notrace(display, bus->gpio_reg) & preserve_bits;
>>>
>>> return reserved;
>>> }
>>> @@ -308,6 +316,22 @@ static void set_data(void *data, int state_high)
>>> intel_de_posting_read(display, bus->gpio_reg);
>>> }
>>>
>>> +static void
>>> +ptl_handle_mask_bits(struct intel_gmbus *bus, bool set)
>>> +{
>>> + struct intel_display *display = bus->display;
>>> + u32 reg_val = intel_de_read_notrace(display, bus->gpio_reg);
>>> + u32 mask_bits = GPIO_CLOCK_DIR_MASK | GPIO_CLOCK_VAL_MASK |
>>> + GPIO_DATA_DIR_MASK | GPIO_DATA_VAL_MASK;
>>> + if (set)
>>> + reg_val |= mask_bits;
>>> + else
>>> + reg_val &= ~mask_bits;
>>> +
>>> + intel_de_write_notrace(display, bus->gpio_reg, reg_val);
>>> + intel_de_posting_read(display, bus->gpio_reg);
>>> +}
>>> +
>>> static int
>>> intel_gpio_pre_xfer(struct i2c_adapter *adapter)
>>> {
>>> @@ -319,6 +343,9 @@ intel_gpio_pre_xfer(struct i2c_adapter *adapter)
>>> if (display->platform.pineview)
>>> pnv_gmbus_clock_gating(display, false);
>>>
>>> + if (intel_display_wa(display, 16025573575))
>>> + ptl_handle_mask_bits(bus, true);
>>> +
>>> set_data(bus, 1);
>>> set_clock(bus, 1);
>>> udelay(I2C_RISEFALL_TIME);
>>> @@ -336,6 +363,9 @@ intel_gpio_post_xfer(struct i2c_adapter *adapter)
>>>
>>> if (display->platform.pineview)
>>> pnv_gmbus_clock_gating(display, true);
>>> +
>>> + if (intel_display_wa(display, 16025573575))
>>> + ptl_handle_mask_bits(bus, false);
>>> }
>>>
>>> static void
>>> --
>>> 2.45.2
>>>
next prev parent reply other threads:[~2025-07-03 12:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 8:46 [PATCH 0/2] Introduce helper for display workarounds and add Wa_16025573575 Ankit Nautiyal
2025-07-02 8:46 ` [PATCH 1/2] drm/i915/display_wa: Add helpers to check wa Ankit Nautiyal
2025-07-02 9:29 ` Jani Nikula
2025-07-02 13:30 ` Gustavo Sousa
2025-07-02 14:12 ` Jani Nikula
2025-07-03 6:19 ` Nautiyal, Ankit K
2025-07-02 19:40 ` Ville Syrjälä
2025-07-02 20:25 ` Lucas De Marchi
2025-07-02 21:29 ` Ville Syrjälä
2025-07-02 21:49 ` Ville Syrjälä
2025-07-03 9:30 ` Nautiyal, Ankit K
2025-07-03 12:14 ` Gustavo Sousa
2025-07-03 13:51 ` Lucas De Marchi
2025-07-03 12:08 ` Gustavo Sousa
2025-07-03 13:55 ` Lucas De Marchi
2025-07-03 14:44 ` Gustavo Sousa
2025-07-02 8:46 ` [PATCH 2/2] drm/i915/gmbus: Add Wa_16025573575 for PTL for bit-bashing Ankit Nautiyal
2025-07-02 13:11 ` Gustavo Sousa
2025-07-03 6:05 ` Nautiyal, Ankit K
2025-07-03 12:16 ` Gustavo Sousa [this message]
2025-07-02 10:01 ` ✓ i915.CI.BAT: success for Introduce helper for display workarounds and add Wa_16025573575 (rev2) Patchwork
2025-07-03 2:39 ` ✓ i915.CI.Full: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-06-30 5:49 [PATCH 0/2] Introduce helper for display workarounds and add Wa_16025573575 Ankit Nautiyal
2025-06-30 5:49 ` [PATCH 2/2] drm/i915/gmbus: Add Wa_16025573575 for PTL for bit-bashing Ankit Nautiyal
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=175154498806.3748.7979864637600744446@intel.com \
--to=gustavo.sousa@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.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