Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: Ankit Nautiyal <ankit.k.nautiyal@intel.com>,
	<intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/gmbus: Add Wa_16025573575 for PTL for bit-bashing
Date: Thu, 12 Jun 2025 09:00:20 -0300	[thread overview]
Message-ID: <174972962084.14553.9763596946172547950@intel.com> (raw)
In-Reply-To: <20250612075330.837179-1-ankit.k.nautiyal@intel.com>

Quoting Ankit Nautiyal (2025-06-12 04:53:30-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.
>
>Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
>---
> drivers/gpu/drm/i915/display/intel_gmbus.c | 38 +++++++++++++++++++---
> 1 file changed, 34 insertions(+), 4 deletions(-)
>
>diff --git a/drivers/gpu/drm/i915/display/intel_gmbus.c b/drivers/gpu/drm/i915/display/intel_gmbus.c
>index 0d73f32fe7f1..c96167c70228 100644
>--- a/drivers/gpu/drm/i915/display/intel_gmbus.c
>+++ b/drivers/gpu/drm/i915/display/intel_gmbus.c
>@@ -242,10 +242,17 @@ static u32 get_reserved(struct intel_gmbus *bus)
>         struct intel_display *display = bus->display;
>         u32 reserved = 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);
>+        if (!display->platform.i830 && !display->platform.i845g) {

I believe the stuff specific to Wa_16025573575 could be done in a
separate "if" statement. The conditions for Wa_16025573575 already imply
(!display->platform.i830 && !display->platform.i845g), and using in a
separate "if" statement reduces one indentation level :-)

That would mean moving preserve_bits one level up, making it available
in the function's scope and doing the registers read conditioned on
preserve_bits being non-zero.

>+                /* On most chips, these bits must be preserved in software. */
>+                u32 preserve_bits = GPIO_DATA_PULLUP_DISABLE | GPIO_CLOCK_PULLUP_DISABLE;
>+
>+                /* PTL: Wa_16025573575: the masks bits need to be preserved through out */
>+                if (DISPLAY_VER(display) == 30)

Instead of open-coding the conditions for the workaround in three
different places in the file, I think we should have a function
needs_wa_16025573575() and use it.

Also, note that the workaround is also required for WCL (display version
30.02), and we would then include that in needs_wa_16025573575().

--
Gustavo Sousa

>+                        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 +315,23 @@ static void set_data(void *data, int state_high)
>         intel_de_posting_read(display, bus->gpio_reg);
> }
> 
>+/* PTL: Wa_16025573575 */
>+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 (DISPLAY_VER(display) == 30)
>+                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 (DISPLAY_VER(display) == 30)
>+                ptl_handle_mask_bits(bus, false);
> }
> 
> static void
>-- 
>2.45.2
>

  parent reply	other threads:[~2025-06-12 12:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12  7:53 [PATCH] drm/i915/gmbus: Add Wa_16025573575 for PTL for bit-bashing Ankit Nautiyal
2025-06-12  9:05 ` ✓ CI.checkpatch: success for " Patchwork
2025-06-12  9:06 ` ✓ CI.KUnit: " Patchwork
2025-06-12  9:17 ` ✓ CI.Build: " Patchwork
2025-06-12  9:58 ` ✓ Xe.CI.BAT: " Patchwork
2025-06-12 12:00 ` Gustavo Sousa [this message]
2025-06-13  6:15   ` [PATCH] " Nautiyal, Ankit K
2025-06-13  9:13     ` Jani Nikula
2025-06-13 10:23       ` Gustavo Sousa
2025-06-13 10:38         ` Jani Nikula
2025-06-15 15:17       ` Nautiyal, Ankit K
2025-06-12 21:08 ` ✗ Xe.CI.Full: failure for " 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=174972962084.14553.9763596946172547950@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 \
    /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