[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zyk8dFthM0EA2A_K@intel.com>
Date: Mon, 4 Nov 2024 16:28:20 -0500
From: Rodrigo Vivi <rodrigo.vivi@...el.com>
To: Giedrius Statkevičius <giedriuswork@...il.com>
CC: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>, Maxime Ripard
<mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>, David Airlie
<airlied@...il.com>, Simona Vetter <simona@...ll.ch>, Jani Nikula
<jani.nikula@...ux.intel.com>, Joonas Lahtinen
<joonas.lahtinen@...ux.intel.com>, Tvrtko Ursulin <tursulin@...ulin.net>,
Ankit Nautiyal <ankit.k.nautiyal@...el.com>,
<dri-devel@...ts.freedesktop.org>, <linux-kernel@...r.kernel.org>,
<intel-gfx@...ts.freedesktop.org>, <intel-xe@...ts.freedesktop.org>
Subject: Re: [PATCH v2] drm/i915/lspcon: do not hardcode settle timeout
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@...il.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@...el.com>
> > Signed-off-by: Giedrius Statkevičius <giedriuswork@...il.com>
Powered by blists - more mailing lists