From: samasth.norway.ananda@oracle.com
To: Jani Nikula <jani.nikula@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: rodrigo.vivi@intel.com, ville.syrjala@linux.intel.com
Subject: Re: [External] : Re: [PATCH] drm/i915/gmbus: fix spurious timeout on 512-byte burst reads
Date: Thu, 19 Feb 2026 15:25:07 -0800 [thread overview]
Message-ID: <71d5ab59-c625-47b3-8a18-29548b1d65af@oracle.com> (raw)
In-Reply-To: <83ad67d411502b2e2ece666745b5209dae83e4f7@intel.com>
On 2/10/26 1:23 AM, Jani Nikula wrote:
> On Fri, 06 Feb 2026, Samasth Norway Ananda <samasth.norway.ananda@oracle.com> wrote:
>> When reading exactly 512 bytes with burst read enabled, the
>> extra_byte_added path breaks out of the inner do-while without
>> decrementing len. The outer while(len) then re-enters and gmbus_wait()
>> times out since all data has been delivered. Decrement len before the
>> break so the outer loop terminates correctly.
>
> Nice find, and the fix looks correct. How did you figure this out? Did
> you hit the issue?
I came across it while working on a different issue and was reading the
code.
>
> I wonder if the whole extra byte thing is a workaround for some old
> hardware that shouldn't be needed on modern hardware... Ville, thoughts?
>
>> Also fix a typo in a nearby comment ("generata" -> "generate").
>
> "Also" is a good hint that it should be a separate patch. ;)
Thanks. I will send out a v2 with separate patches :)
Samasth.
>
> BR,
> Jani
>
>> Fixes: d5dc0f43f268 ("drm/i915/gmbus: Enable burst read")
>> Signed-off-by: Samasth Norway Ananda <samasth.norway.ananda@oracle.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_gmbus.c | 6 ++++--
>> 1 file changed, 4 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_gmbus.c b/drivers/gpu/drm/i915/display/intel_gmbus.c
>> index 2caff677600c..5fb3fee34af4 100644
>> --- a/drivers/gpu/drm/i915/display/intel_gmbus.c
>> +++ b/drivers/gpu/drm/i915/display/intel_gmbus.c
>> @@ -496,8 +496,10 @@ gmbus_xfer_read_chunk(struct intel_display *display,
>>
>> val = intel_de_read_fw(display, GMBUS3(display));
>> do {
>> - if (extra_byte_added && len == 1)
>> + if (extra_byte_added && len == 1) {
>> + len--;
>> break;
>> + }
>>
>> *buf++ = val & 0xff;
>> val >>= 8;
>> @@ -693,7 +695,7 @@ do_gmbus_xfer(struct i2c_adapter *adapter, struct i2c_msg *msgs, int num,
>> goto clear_err;
>> }
>>
>> - /* Generate a STOP condition on the bus. Note that gmbus can't generata
>> + /* Generate a STOP condition on the bus. Note that gmbus can't generate
>> * a STOP on the very first cycle. To simplify the code we
>> * unconditionally generate the STOP condition with an additional gmbus
>> * cycle. */
>
prev parent reply other threads:[~2026-02-19 23:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 20:30 [PATCH] drm/i915/gmbus: fix spurious timeout on 512-byte burst reads Samasth Norway Ananda
2026-02-09 18:26 ` ✓ i915.CI.BAT: success for " Patchwork
2026-02-10 1:26 ` ✗ i915.CI.Full: failure " Patchwork
2026-02-10 9:23 ` [PATCH] " Jani Nikula
2026-02-10 16:39 ` Ville Syrjälä
2026-02-19 23:25 ` samasth.norway.ananda [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=71d5ab59-c625-47b3-8a18-29548b1d65af@oracle.com \
--to=samasth.norway.ananda@oracle.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=ville.syrjala@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