All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Giedrius Statkevičius" <giedriuswork@gmail.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>,
	Ankit Nautiyal <ankit.k.nautiyal@intel.com>,
	<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
	<intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH v2] drm/i915/lspcon: do not hardcode settle timeout
Date: Mon, 4 Nov 2024 16:28:20 -0500	[thread overview]
Message-ID: <Zyk8dFthM0EA2A_K@intel.com> (raw)
In-Reply-To: <CALt+6nqxMZjuZuOKaj8Cx4dcNZx0n-0F9aa97d-vZoMWeN=bOw@mail.gmail.com>

On Mon, Nov 04, 2024 at 02:09:46PM +0200, Giedrius Statkevičius wrote:
> Hello,
> 
> Kind ping.

There was a pipe underun in CI... I honestly don't believe this patch is
causing it, but anyway I decided to trigger a retest there before I push this.

Thanks for the patch and review.

> 
> 
> On Thu, 17 Oct 2024 at 10:57, Giedrius Statkevičius
> <giedriuswork@gmail.com> wrote:
> >
> > Avoid hardcoding the LSPCON settle timeout because it takes a longer
> > time on certain chips made by certain vendors. Use the function that
> > already exists to determine the timeout.
> >
> > Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> > Signed-off-by: Giedrius Statkevičius <giedriuswork@gmail.com>

  reply	other threads:[~2024-11-04 21:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17  7:57 [PATCH v2] drm/i915/lspcon: do not hardcode settle timeout Giedrius Statkevičius
2024-10-17 13:57 ` ✓ CI.Patch_applied: success for drm/i915/lspcon: do not hardcode settle timeout (rev3) Patchwork
2024-10-17 13:57 ` ✓ CI.checkpatch: " Patchwork
2024-10-17 13:58 ` ✓ CI.KUnit: " Patchwork
2024-10-17 14:10 ` ✓ CI.Build: " Patchwork
2024-10-17 14:12 ` ✓ CI.Hooks: " Patchwork
2024-10-17 14:14 ` ✗ CI.checksparse: warning " Patchwork
2024-10-17 14:39 ` ✓ CI.BAT: success " Patchwork
2024-10-17 16:26 ` ✓ Fi.CI.BAT: success for drm/i915/lspcon: do not hardcode settle timeout (rev2) Patchwork
2024-10-17 18:18 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-10-18  2:54 ` ✗ CI.FULL: failure for drm/i915/lspcon: do not hardcode settle timeout (rev3) Patchwork
2024-11-04 12:09 ` [PATCH v2] drm/i915/lspcon: do not hardcode settle timeout Giedrius Statkevičius
2024-11-04 21:28   ` Rodrigo Vivi [this message]
2024-11-07  8:21     ` Giedrius Statkevičius
2025-01-22 11:15     ` Giedrius Statkevičius
2025-01-24  3:16       ` Rodrigo Vivi
2025-01-27 20:06         ` Rodrigo Vivi
2024-11-04 23:46 ` ✓ Fi.CI.BAT: success for drm/i915/lspcon: do not hardcode settle timeout (rev3) Patchwork
2024-11-05 17:06 ` ✗ Fi.CI.IGT: failure " Patchwork
2025-01-22 16:28 ` ✓ i915.CI.BAT: success for drm/i915/lspcon: do not hardcode settle timeout (rev4) Patchwork
2025-01-23 18:57 ` ✗ i915.CI.Full: failure " 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=Zyk8dFthM0EA2A_K@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=airlied@gmail.com \
    --cc=ankit.k.nautiyal@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=giedriuswork@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tursulin@ursulin.net \
    --cc=tzimmermann@suse.de \
    /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.